DOCSLIB.ORG

4PSA DNS Manager 4.0.0

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
4PSA DNS Manager 4.0.0 4PSA DNS Manager 4.0.0 Client's User Guide For more information about 4PSA DNS Manager, check: http://www.4psa.com Copyright © 2011 Rack-Soft. 4PSA is a registered trademark of Rack-Soft, Inc. Client's User Guide Manual Version 79252.10 at 2011/04/11 11:37:58 For suggestions regarding this manual contact: [email protected] All rights reserved. Distribution of this work or derivative of this work is prohibited unless prior written permission is obtained from the copyright holder. DNS Manager is a registered trademark of 4PSA (Rack-Soft, Inc.). Plesk is a registered trademark of Parallels, Inc. Linux is a registered trademark of Linus Torvalds. RedHat is a registered trademark of Red Hat Software, Inc. FreeBSD is a registered trademark of FreeBSD, Inc. All other trademarks and copyrights are property of their respective owners. Table of Contents Preface ................................................................................................. 5 Who Should Read This Guide ....................................................................... 5 Chapter 1. About 4PSA DNS Manager 4.0.0 ............................................... 6 Where to Use 4PSA DNS Manager ................................................................ 6 4PSA DNS Manager 4.0.0 Features ............................................................... 7 Chapter 2. Navigation ............................................................................ 9 The Navigation Panel ................................................................................. 9 The Top Frame Controls ........................................................................... 10 The Main Frame Controls .......................................................................... 10 Using the Search Functions ....................................................................... 11 The Table Controls .................................................................................. 12 How to Remove Table Records ................................................................... 12 Chapter 3. Logging In ........................................................................... 14 Chapter 4. General Account Management ............................................... 15 Chapter 5. Manage the Application ........................................................ 17 Manage Interface Preferences .................................................................... 17 My Interface Settings ........................................................................... 18 Manage the Custom Buttons ...................................................................... 18 Add a New Custom Button .................................................................... 19 Chapter 6. Manage the System Features ................................................. 23 Manage the System Settings ..................................................................... 24 XML Export ........................................................................................... 26 XML Import ........................................................................................... 26 Chapter 7. Manage the System Templates ............................................... 28 Manage the DNS Templates ....................................................................... 28 Add a New Client DNS Template ............................................................. 29 Client's DNS Template Management ......................................................... 30 Chapter 8. Manage the DNS Zones ......................................................... 34 Client Management Page .......................................................................... 34 Searching the DNS Zones List ................................................................ 35 SPF Rules .......................................................................................... 36 Glue Records ...................................................................................... 37 Global Operations on DNS Zones ............................................................. 38 Edit Client Information ............................................................................. 40 Add a New DNS Zone .............................................................................. 40 Add a Single DNS Zone Name ................................................................ 41 Adding Multiple DNS Zones with Complete DNS Records ................................ 44 Edit a DNS Zone .................................................................................... 45 Add a New DNS Records ....................................................................... 49 Transfer IP Addresses ........................................................................... 60 DNS Zone Backup ............................................................................... 61 Manage the Round Robin Polls ................................................................ 62 Set the SOA Parameters ....................................................................... 64 Checking the Nameservers .................................................................... 65 Managing DNS Zones Remote Update Locations .............................................. 66 Add a New Remote Update Location ......................................................... 68 Remote Logs ...................................................................................... 70 Removal Confirmation .......................................................................... 70 DNS Zone Backup ................................................................................... 71 Chapter 9. Remote Update Location Configuration ................................... 72 1. 4PSA DNS Manager as a Secondary Server ................................................ 72 2. 4PSA DNS Manager as a Primary Server ................................................... 74 Chapter 10. Contact and Support ........................................................... 76 Appendix A. Supported Dump File Examples .......................................... 77 Index ................................................................................................... 87 Preface Who Should Read This Guide This User Guide must be read by the 4PSA DNS Manager clients. 4.0.0 Client's User Guide 5 Chapter 1 About 4PSA DNS Manager 4.0.0 4PSA DNS Manager 4.0.0 is a server-level multitenant software automation solution that allows users with a minimum IT experience to manage DNS Zones. With 4PSA DNS Manager, you can create and administer DNS Zones and DNS Records, backup DNS Zones, manage DNS templates, gather DNS information from remote servers, etc. 4PSA DNS Manager can load DNS zone names from remote servers, regardless of the control panel or the operating system that runs on these servers. Thanks to its advanced features, 4PSA DNS Manager is the ideal tool for automatic DNS management. Where to Use 4PSA DNS Manager Unlike other DNS management applications, 4PSA DNS Manager offers superior automation features and a friendly client level interface. Clients who use hosting services will find 4PSA DNS Manager to be a very easy to use solution. Most DNS applications are frustrating; it is a known fact that even 4.0.0 Client's User Guide 6 some administrators do not fully understand all DNS functions. With 4PSA DNS Manager, these problems have become history. Here are several utilization scenarios: • Centralize DNS information from multiple servers. You will be able to offer two name servers no matter how many hosting servers you have and what platform or control panel they use. The centralization process is automatic and you do not have to add DNS Zone information to the 4PSA DNS Manager server. The interface scripts for most popular hosting panels like Plesk, Cpanel, Ensim, InterWorx Control Panel and Helm are included. • Offer DNS redundancy. 4PSA DNS Manager can act as a secondary DNS server, gathering zone names from all the participant servers and automatically updating DNS Zone information. • Offer DNS hosting. Hosting companies can use your services for DNS redundancy. Because no work is actually required to update the list of DNS Zones, DNS hosting becomes a very simple task. Clients will love the nice interface and the Zone validation. 4PSA DNS Manager 4.0.0 Features Some of the most important features offered by 4PSA DNS Manager 4.0.0 are: • Administrator and client management levels. • System designed for automatic DNS hosting. • Client permissions and limits. • Client actions auditing that logs information about DNS zone changes. • Command line creation utilities. • Supports both RFC1912 and timestamp SOA Serial number formats. • SystemAPI third party integration. • DNS Zone management: ◦ Advanced Reverse DNS Zones management. ◦ Create DNS Zones in interface (single Zones or from file). 4.0.0 Client's User Guide 7 ◦ Master/Slave Zones supported. ◦ A, AAAA, CNAME, NAPTR, NS, MX, PTR, SRV, TXT Records supported. ◦ Advanced Record management with owned and wide server level and client level DNS templates support. ◦ Update DNS Zone information from remote servers (can retrieve the list of DNS Zones added in any control panel interface). ◦ Per server or per client Start of Authority (SOA) Records: refresh time, retry time, expire time, minimum TTL, default TTL. ◦ Automatic query of reverse DNS. ◦ E 164 Zones support. ◦ IPV6 reverse Zones support. • Remote update locations management: ◦ Remote Zone types/Update interval. ◦ Remote update statistics
Load more

Recommended publications
  • Sistem Pendukung Keputusan Dalam Pemilihan Control Panel Virtual Private Server Menggunakan Metode AHP Dan SAW
    Citec Journal, Vol. 5, No. 1, November 2017 – Januari 2018 ISSN: 2460-4259 14 Sistem Pendukung Keputusan Dalam Pemilihan Control Panel Virtual Private Server Menggunakan Metode AHP dan SAW Decision Support System in Selection of a Control Panel Virtual Private Server Using AHP and SAW Method Arwendra Adi Putra*1, Kusrini 2, Eko Pramono3 1,2,3Magister Teknik Informatika, Universitas Amikom Yogyakarta E-mail: [email protected], [email protected], [email protected] Abstrak Hosting dapat dibedakan menjadi berbagai macam type, salah satunya adalah Virtual Private Server (VPS). VPS merupakan sebuah cara untuk membagi sumber daya sebuah physical server menjadi server virtual. Sebuah VPS memerlukan control panel karena untuk mempermudah pengaturan seperti mengelola email, disk, database, penambahan domain, memonitor bandwidth dan backup data. Terdapat berbagai macam control panel dengan spesifikasi yang berbeda-beda. Pemilihan control panel tersebut sangat penting karena control panel tersebut harus disesuaikan dengan spesifikasi VPS. Berdasarkan permasalahan tersebut, diperlukan sistem yang dapat membantu dalam pengambilan keputusan dalam pemilihan control panel. Metode yang digunakan dalam penelitian ini adalah dengan menggunakan metode Analitical Hierarcy Process (AHP) dan Simple Additive Weighting (SAW). Metode AHP digunakan untuk mencari bobot variabel kriteria, sedangkan metode SAW digunakan untuk menentukan nilai akhir dan perangkingan. Hasil perangkingan alternatif control panel pada sistem ini menunjukkan hasil yang sama dengan hasil perangkingan dari pakar control panel, sehingga sistem ini dapat digunakan oleh pengguna sebagai dasar pengambilan keputusan dalam menentukan pemilihan alternatif control panel. Kata Kunci — control panel, VPS, AHP, SAW, sistem pendukung keputusan Abstract Hosting can be divided into various types, one of them is Virtual Private Server (VPS).
    [Show full text]
  • DNS Zones Overview
    DNS Zones Overview A DNS zone is the contiguous portion of the DNS domain name space over which a DNS server has authority. A zone is a portion of a namespace. It is not a domain. A domain is a branch of the DNS namespace. A DNS zone can contain one or more contiguous domains. A DNS server can be authoritative for multiple DNS zones. A non-contiguous namespace cannot be a DNS zone. A zone contains the resource records for all of the names within the particular zone. Zone files are used if DNS data is not integrated with Active Directory. The zone files contain the DNS database resource records that define the zone. If DNS and Active Directory are integrated, then DNS data is stored in Active Directory. The different types of zones used in Windows Server 2003 DNS are listed below: Primary zone Secondary zone Active Directory-integrated zone Reverse lookup zone Stub zone A primary zone is the only zone type that can be edited or updated because the data in the zone is the original source of the data for all domains in the zone. Updates made to the primary zone are made by the DNS server that is authoritative for the specific primary zone. Users can also back up data from a primary zone to a secondary zone. A secondary zone is a read-only copy of the zone that was copied from the master server during zone transfer. In fact, a secondary zone can only be updated through zone transfer. An Active Directory-integrated zone is a zone that stores its data in Active Directory.
    [Show full text]
  • Domain Name System 1 Domain Name System
    Domain Name System 1 Domain Name System The Domain Name System (DNS) is a hierarchical distributed naming system for computers, services, or any resource connected to the Internet or a private network. It associates various information with domain names assigned to each of the participating entities. A Domain Name Service translates queries for domain names (which are easier to understand and utilize when accessing the internet) into IP addresses for the purpose of locating computer services and devices worldwide. An often-used analogy to explain the Domain Name System is that it serves as the phone book for the Internet by translating human-friendly computer hostnames into IP addresses. For example, the domain name www.example.com translates to the addresses 192.0.43.10 (IPv4) and 2620:0:2d0:200::10 (IPv6). The Domain Name System makes it possible to assign domain names to groups of Internet resources and users in a meaningful way, independent of each entity's physical location. Because of this, World Wide Web (WWW) hyperlinks and Internet contact information can remain consistent and constant even if the current Internet routing arrangements change or the participant uses a mobile device. Internet domain names are easier to remember than IP addresses such as 208.77.188.166 (IPv4) or 2001:db8:1f70::999:de8:7648:6e8 (IPv6). Users take advantage of this when they recite meaningful Uniform Resource Locators (URLs) and e-mail addresses without having to know how the computer actually locates them. The Domain Name System distributes the responsibility of assigning domain names and mapping those names to IP addresses by designating authoritative name servers for each domain.
    [Show full text]
  • DNS) Administration Guide
    Edgecast Route (DNS) Administration Guide Disclaimer Care was taken in the creation of this guide. However, Edgecast cannot accept any responsibility for errors or omissions. There are no warranties, expressed or implied, including the warranty of merchantability or fitness for a particular purpose, accompanying this product. Trademark Information EDGECAST is a registered trademark of Verizon Digital Media Services Inc. About This Guide Route (DNS) Administration Guide Version 2.40 8/28/2021 ©2021 Verizon Media. All rights reserved. Table of Contents Route ............................................................................................................................................................. 1 Introduction .............................................................................................................................................. 1 Scope ......................................................................................................................................................... 1 Module Comparison ................................................................................................................................. 2 Managed (Primary) or Secondary DNS Module .................................................................................... 2 DNS Health Checks Module .................................................................................................................. 3 Billing Activation ......................................................................................................................................
    [Show full text]
  • DNS) Deployment Guide
    Archived NIST Technical Series Publication The attached publication has been archived (withdrawn), and is provided solely for historical purposes. It may have been superseded by another publication (indicated below). Archived Publication Series/Number: NIST Special Publication 800-81 Revision 1 Title: Secure Domain Name System (DNS) Deployment Guide Publication Date(s): April 2010 Withdrawal Date: September 2013 Withdrawal Note: SP 800-81 Revision 1 is superseded in its entirety by the publication of SP 800-81-2 (September 2013). Superseding Publication(s) The attached publication has been superseded by the following publication(s): Series/Number: NIST Special Publication 800-81-2 Title: Secure Domain Name System (DNS) Deployment Guide Author(s): Ramaswamy Chandramouli, Scott Rose Publication Date(s): September 2013 URL/DOI: http://dx.doi.org/10.6028/NIST.SP.800-81-2 Additional Information (if applicable) Contact: Computer Security Division (Information Technology Lab) Latest revision of the SP 800-81-2 (as of August 7, 2015) attached publication: Related information: http://csrc.nist.gov/ Withdrawal N/A announcement (link): Date updated: ƵŐƵƐƚϳ, 2015 Special Publication 800-81r1 Sponsored by the Department of Homeland Security Secure Domain Name System (DNS) Deployment Guide Recommendations of the National Institute of Standards and Technology Ramaswamy Chandramouli Scott Rose i NIST Special Publication 800-81r1 Secure Domain Name System (DNS) Deployment Guide Sponsored by the Department of Homeland Security Recommendations of the National Institute of Standards and Technology Ramaswamy Chandramouli Scott Rose C O M P U T E R S E C U R I T Y Computer Security Division/Advanced Network Technologies Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899 April 2010 U.S.
    [Show full text]
  • CDP 3.12.2 Release Notes
    R1Soft Continuous Data Protection®, Documentation, Version 3.18.2 CDP 3.12.2 Release Notes CDP 3.12.2 (Stable) Release Notes This release includes 4 product editions: CDP Standard Edition, CDP Advanced Edition, CDP Enterprise Edition, and Data Center Console. IMPORTANT NOTE(S): Release 3.12.2 This update to 3.12.1 contains two improvements: MySQL backups on servers that have crashed tables will continue without failing. The crashed tables will be skipped and the backup process will continue. Additional data will be recorded in your disk safe which will aid in debugging if there is ever a problem with your disk safe. This update will also correct a potential issue if recovery points have been merged out of order. If you have already installed or upgraded to the 3.12.0 or 3.12.1 agent, there is no need to install the 3.12.2 agent as no changes have been made to this application. Release 3.12.1 Addresses Issues with 3.8.x Upgrade and MySQL Discovery Performance: There have been a small number of issues with customers upgrading from 3.8.x or who previously had one of these versions installed. This update will correct the problem for these customers experiencing issues upgrading or running CDP Server after upgrading to 3.12 and prevent this issue on future upgrades. This release also corrects a performance problem with discovery and backup of MySQL databases which was introduced in 3.12.0. This fix returns performance to speeds achieved in 3.10. Upgrading customers may experience a delay when starting the WebUI: Please be patient as important updates are in progress.
    [Show full text]
  • Measurements and Laboratory Simulations of the Upper DNS Hierarchy
    Measurements and Laboratory Simulations of the Upper DNS Hierarchy 1 2 2 2 Duane Wessels , Marina Fomenkov , Nevil Brownlee , and kc claffy 1 The Measurement Factory, Inc. [email protected] 2 CAIDA, San Diego Supercomputer Center, University of California, San Diego fmarina, nevil, [email protected] Abstract. Given that the global DNS system, especially at the higher root and top-levels, experiences significant query loads, we seek to answer the following questions: (1) How does the choice of DNS caching software for local resolvers affect query load at the higher levels? (2) How do DNS caching implementations spread the query load among a set of higher level DNS servers? To answer these questions we did case studies of workday DNS traffic at the University of California San Diego (USA), the University of Auckland (New Zealand), and the University of Colorado at Boulder (USA). We also tested var- ious DNS caching implementations in fully controlled laboratory experiments. This paper presents the results of our analysis of real and simulated DNS traffic. We make recommendations to network administrators and software developers aimed at improving the overall DNS system. 1 Background The Domain Name System (DNS) is a fundamental component of the modern Inter- net [1], providing a critical link between human users and Internet routing infrastructure by mapping host names to IP addresses. The DNS hierarchical name space is divided into zones and coded in the widespread “dots” structure. For example, com is the parent zone for microsoft.com, cnn.com, and approximately 20 million other zones. The DNS hierarchy’s root zone is served by 13 nameservers, known collectively as the DNS root servers.
    [Show full text]
  • Server Backup Manager Demo
    What’s new at R1Soft? Introductions Juan Rogers Sr. Joined the R1Soft team in 2017 as a Sr. Product Manager with 30 + years of experience in Information Technology, BDR and Cloud computing. Agenda • R1Soft Background • Technology Overview -R1Soft Server Backup Manager • SBM Feature Highlights • What’s New in Server Backup Manager • Come see us ! R1Soft Background Partners • Founded in 2007 • Based in Houston, TX • Deployed by 1,800 Service Providers • Protecting 250,000+ Servers Worldwide • Acquired by Continuum Managed Services in 2014 • Provides the Core Technology for Continuum’s Continuity 247™ R1Soft® Technology Overview Backup Manager Backup Manager (Site A) (Site B) • Block level backup • Only one full backup for life • CDP through changed block tracking (incremental forever) • Site-to-site replication between managers • Cross-platform support • Web based management Protected Machines SBM Feature Highlights • Continuous Data Protection™ • Protect Windows and Linux Servers • Block-Level Backups • Database Integration for MySQL • Flexible Backup Schedules and Microsoft SQL Server • Bare Metal and Granular File • Integration for Hosting Control Restore Panels Including cPanel, Plesk, Interworx and more… • Site-to-Site Replication • Integration for Microsoft Exchange • Multi-Tenancy • AES-256 Disk Safe Encryption New Features in SBM 6.6 Cost-Effective Off-site Backup and Archival Media assets, scientific data, and other intellectual property must be backed up and preserved for the long term. Helps you to comply with long-term regulatory compliance data retention mandates - (years, decades) Offsite backups allow recovery even if the primary site has been destroyed. 3-2-1 Backup strategy Contingencies for natural disaster, malware, and malicious attacks. For many organizations this is still an error prone and expensive manual effort.
    [Show full text]
  • Understanding Implications of DNS Zone Provisioning
    Understanding Implications of DNS Zone Provisioning Andrew J. Kalafut Craig A. Shue Minaxi Gupta [email protected] [email protected] [email protected] Computer Science Department Indiana University Bloomington, IN ABSTRACT a domain need to synchronize with each other in their view DNS is a critical component of the Internet. This paper of the zone. The DNS provides a special query for that, takes a comprehensive look at the provisioning of Internet called the zone transfer query. In this work, we leverage the domains and its impact on the availability of various services. zone transfer query to capture detailed information about To gather data, we sweep 60% of the Internet’s domains DNS zones in the Internet. During a three month period, for zone transfers. 6.6% of them allow us to transfer their we swept 60% of the Internet for zone transfers. In order to complete information. We find that carelessness in handling increase our data beyond those zones allowing zone trans- DNS records can lead to reduced availability of name servers, fer, we walked the zones of the second-level domains known email, and Web servers. It also undermines anti-spam efforts to deploy DNSSEC [2] (DNS Security Extensions). This is and the efforts to shut down phishing sites or to contain a slow process since it involves making a large number of malware infections. queries, but its net effect is the same as a zone transfer. Us- ing the two data sets, we examined the DNS zones in our two data sets. The key findings of our study are the following: Categories and Subject Descriptors C.2.2 [Network protocols]: Applications—DNS 1.
    [Show full text]
  • When Parents and Children Disagree: Diving Into DNS Delegation Inconsistency
    When parents and children disagree: Diving into DNS delegation inconsistency Raffaele Sommese1, Giovane C.M. Moura2, Mattijs Jonker1, Roland van Rijswijk-Deij1;3, Alberto Dainotti4, K.C. Claffy4, and Anna Sperotto1 1 University of Twente 2 SIDN Labs 3 NLnet Labs 4 CAIDA Abstract. The Domain Name System (DNS) is a hierarchical, decen- tralized, and distributed database. A key mechanism that enables the DNS to be hierarchical and distributed is delegation [7] of responsibil- ity from parent to child zones—typically managed by different entities. RFC1034 [12] states that authoritative nameserver (NS) records at both parent and child should be “consistent and remain so”, but we find in- consistencies for over 13M second-level domains. We classify the type of inconsistencies we observe, and the behavior of resolvers in the face of such inconsistencies, using RIPE Atlas to probe our experimental do- main configured for different scenarios. Our results underline the risk such inconsistencies pose to the availability of misconfigured domains. 1 Introduction The Domain Name System (DNS) [12] is one of the most critical components of the Internet, used by virtually every user and application. DNS is a distributed, hierarchical database that maps hosts, services and applications to IP addresses and various other types of records. A key mechanism that enables the DNS to be hierarchical and distributed is delegation [7]. In order for delegation to work, the DNS hierarchy is organized in parent and child zones—typically managed by different entities—that need to share common information (NS records) about which are the authoritative name servers for a given domain.
    [Show full text]
  • DNS and BIND Other Resources from O’Reilly
    DNS and BIND Other resources from O’Reilly Related titles DNS and BIND Cookbook™ DNS on Windows Server 2003 oreilly.com oreilly.com is more than a complete catalog of O’Reilly books. You’ll also find links to news, events, articles, weblogs, sample chapters, and code examples. oreillynet.com is the essential portal for developers interested in open and emerging technologies, including new platforms, pro- gramming languages, and operating systems. Conferences O’Reilly brings diverse innovators together to nurture the ideas that spark revolutionary industries. We specialize in document- ing the latest tools and systems, translating the innovator’s knowledge into useful skills for those in the trenches. Visit con- ferences.oreilly.com for our upcoming events. Safari Bookshelf (safari.oreilly.com) is the premier online refer- ence library for programmers and IT professionals. Conduct searches across more than 1,000 books. Subscribers can zero in on answers to time-critical questions in a matter of seconds. Read the books on your Bookshelf from cover to cover or sim- ply flip to the page you need. Try it today for free. FIFTH EDITION DNS and BIND Cricket Liu and Paul Albitz Beijing • Cambridge • Farnham • Köln • Sebastopol • Taipei • Tokyo DNS and BIND, Fifth Edition by Cricket Liu and Paul Albitz Copyright © 2006, 2001, 1998, 1997, 1992 O’Reilly Media, Inc. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (safari.oreilly.com).
    [Show full text]
  • A Longitudinal, End-To-End View of the DNSSEC Ecosystem
    A Longitudinal, End-to-End View of the DNSSEC Ecosystem Taejoong Chung Roland van Rijswijk-Deij Northeastern University University of Twente and SURFnet Balakrishnan Chandrasekaran David Choffnes Dave Levin TU Berlin Northeastern University University of Maryland Bruce M. Maggs Alan Mislove Duke University and Akamai Technologies Northeastern University Christo Wilson Northeastern University Abstract To address these problems, DNS Security Extensions (DNSSEC) [20] were introduced nearly two decades ago. The Domain Name System’s Security Extensions At its core, DNSSEC is a hierarchical public key infras- (DNSSEC) allow clients and resolvers to verify that tructure (PKI) that largely mirrors the DNS hierarchy and DNS responses have not been forged or modified in- is rooted at the root DNS zone. To enable DNSSEC, the flight. DNSSEC uses a public key infrastructure (PKI) owner of a domain signs its DNS records and publishes to achieve this integrity, without which users can be sub- the signatures along with its public key; this public key is ject to a wide range of attacks. However, DNSSEC can then signed by its parent domain, and so on up to the root operate only if each of the principals in its PKI prop- DNS zone. A resolver validates a signed DNS record erly performs its management tasks: authoritative name by recursively checking the associated signatures until it servers must generate and publish their keys and signa- reaches the well-known root zone trusted key. tures correctly, child zones that support DNSSEC must Largely in response to powerful attacks such as the be correctly signed with their parent’s keys, and resolvers Kaminsky Attack [28], DNSSEC adoption has increased must actually validate the chain of signatures.
    [Show full text]