# AUTHOR <EMAIL@ADDRESS>, YEAR.
# 
# neb <nick@bebout.net>, 2011.
msgid ""
msgstr ""
"Project-Id-Version: Fedora Deployment Guide\n"
"POT-Creation-Date: 2011-02-22T00:51:12\n"
"PO-Revision-Date: 2011-06-29 22:59+0000\n"
"Last-Translator: perplex <perplesso82@gmail.com>\n"
"Language-Team: Italian <trans-it@lists.fedoraproject.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: it\n"
"Plural-Forms: nplurals=2; plural=(n != 1)\n"

#. Tag: title
#, no-c-format
msgid "The BIND DNS Server"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>DNS</primary> <secondary>definition</secondary> "
"<seealso>BIND</seealso>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>nameserver</primary> <see>DNS</see>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"<systemitem class=\"protocol\">DNS</systemitem> (Domain Name System), also "
"known as a <firstterm>nameserver</firstterm>, is a network system that "
"associates hostnames with their respective IP addresses. For users, this has"
" the advantage that they can refer to machines on the network by names that "
"are usually easier to remember than the numerical network addresses. For "
"system administrators, using the nameserver allows them to change the IP "
"address for a host without ever affecting the name-based queries, or to "
"decide which machines handle these queries."
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>Berkeley Internet Name Domain</primary> <see>BIND</see>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"This chapter covers <systemitem class=\"service\">BIND</systemitem> "
"(Berkeley Internet Name Domain), the DNS server included in &MAJOROS;. It "
"focuses on the structure of its configuration files, and describes how to "
"administer it both locally and remotely."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Introduction to DNS"
msgstr "Introduzione a DNS"

#. Tag: indexterm
#, no-c-format
msgid "<primary>root nameserver</primary> <see>BIND</see>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"DNS is usually implemented using one or more centralized servers that are "
"authoritative for certain domains. When a client host requests information "
"from a nameserver, it usually connects to port 53. The nameserver then "
"attempts to resolve the name requested. If it does not have an authoritative"
" answer, or does not already have the answer cached from an earlier query, "
"it queries other nameservers, called <firstterm>root "
"nameservers</firstterm>, to determine which nameservers are authoritative "
"for the name in question, and then queries them to get the requested name."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Nameserver Zones"
msgstr "Zone del server dei nomi"

#. Tag: indexterm
#, no-c-format
msgid "<primary>BIND</primary> <secondary>resource record</secondary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>resource record</primary> <see>BIND</see>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary>fully qualified domain name</primary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary><acronym>FQDN</acronym></primary> <see>fully qualified domain "
"name</see>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"In a DNS server such as BIND, all information is stored in basic data "
"elements called <firstterm>resource records</firstterm> (RR). The resource "
"record is usually a <firstterm>fully qualified domain name</firstterm> "
"(FQDN) of a host, and is broken down into multiple sections organized into a"
" tree-like hierarchy. This hierarchy consists of a main trunk, primary "
"branches, secondary branches, and so on."
msgstr ""

#. Tag: title
#, no-c-format
msgid "A simple resource record"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "bob.sales.example.com"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>zones</secondary> "
"<tertiary>description</tertiary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Each level of the hierarchy is divided by a period (that is, "
"<literal>.</literal>). In <xref linkend=\"example-bind-introduction-zones-"
"rr\" />, <literal>com</literal> defines the <firstterm>top-level "
"domain</firstterm>, <literal>example</literal> its subdomain, and "
"<literal>sales</literal> the subdomain of <literal>example</literal>. In "
"this case, <literal>bob</literal> identifies a resource record that is part "
"of the <systemitem class=\"domainname\">sales.example.com</systemitem> "
"domain. With the exception of the part furthest to the left (that is, "
"<literal>bob</literal>), each of these sections is called a "
"<firstterm>zone</firstterm> and defines a specific "
"<firstterm>namespace</firstterm>."
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>types</secondary> <tertiary>primary "
"(master) nameserver</tertiary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>types</secondary> <tertiary>secondary "
"(slave) nameserver</tertiary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Zones are defined on authoritative nameservers through the use of "
"<firstterm>zone files</firstterm>, which contain definitions of the resource"
" records in each zone. Zone files are stored on <firstterm>primary "
"nameservers</firstterm> (also called <firstterm>master "
"nameservers</firstterm>), where changes are made to the files, and "
"<firstterm>secondary nameservers</firstterm> (also called <firstterm>slave "
"nameservers</firstterm>), which receive zone definitions from the primary "
"nameservers. Both primary and secondary nameservers are authoritative for "
"the zone and look the same to clients. Depending on the configuration, any "
"nameserver can also serve as a primary or secondary server for multiple "
"zones at the same time."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Nameserver Types"
msgstr "Tipi di server dei nomi"

#. Tag: para
#, no-c-format
msgid "There are two nameserver configuration types:"
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>types</secondary> "
"<tertiary>authoritative nameserver</tertiary> </indexterm> <indexterm> "
"<primary>authoritative nameserver</primary> <see>BIND</see> </indexterm> "
"<indexterm> <primary>BIND</primary> <secondary>types</secondary> "
"<tertiary>primary (master) nameserver</tertiary> </indexterm> <indexterm> "
"<primary>primary nameserver</primary> <see>BIND</see> </indexterm> "
"<indexterm> <primary>BIND</primary> <secondary>types</secondary> "
"<tertiary>secondary (slave) nameserver</tertiary> </indexterm> <indexterm> "
"<primary>secondary nameserver</primary> <see>BIND</see> </indexterm> "
"authoritative"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Authoritative nameservers answer to resource records that are part of their "
"zones only. This category includes both primary (master) and secondary "
"(slave) nameservers."
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>types</secondary> "
"<tertiary>recursive nameserver</tertiary> </indexterm> <indexterm> "
"<primary>recursive nameserver</primary> <see>BIND</see> </indexterm> "
"recursive"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Recursive nameservers offer resolution services, but they are not "
"authoritative for any zone. Answers for all resolutions are cached in a "
"memory for a fixed period of time, which is specified by the retrieved "
"resource record."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Although a nameserver can be both authoritative and recursive at the same "
"time, it is recommended not to combine the configuration types. To be able "
"to perform their work, authoritative servers should be available to all "
"clients all the time. On the other hand, since the recursive lookup takes "
"far more time than authoritative responses, recursive servers should be "
"available to a restricted number of clients only, otherwise they are prone "
"to distributed denial of service (DDoS) attacks."
msgstr ""

#. Tag: title
#, no-c-format
msgid "BIND as a Nameserver"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>utilities</secondary> "
"<tertiary><systemitem class=\"service\">named</systemitem></tertiary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>utilities</secondary> "
"<tertiary><command>rndc</command></tertiary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>utilities</secondary> "
"<tertiary><command>dig</command></tertiary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary><systemitem class=\"service\">named</systemitem></primary> "
"<see>BIND</see>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><command>rndc</command></primary> <see>BIND</see>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid "<primary><command>dig</command></primary> <see>BIND</see>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"BIND consists of a set of DNS-related programs. It contains a monolithic "
"nameserver called <systemitem class=\"service\">named</systemitem>, an "
"administration utility called <command>rndc</command>, and a debugging tool "
"called <command>dig</command>. Refer to <xref linkend=\"ch-"
"Controlling_Access_to_Services\" /> for more information on how to run a "
"service in &MAJOROS;."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Configuring the <command>named</command> Service"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"When the <systemitem class=\"service\">named</systemitem> service is "
"started, it reads the configuration from the files as described in <xref "
"linkend=\"table-bind-namedconf-files\" />."
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary><filename>/etc/named.conf</filename></primary> <see>BIND</see>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>files</secondary> "
"<tertiary><filename>/etc/named.conf</filename></tertiary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>directories</secondary> "
"<tertiary><filename class=\"directory\">/etc/named/</filename></tertiary>"
msgstr ""

#. Tag: title
#, no-c-format
msgid ""
"The <systemitem class=\"service\">named</systemitem> service configuration "
"files"
msgstr ""

#. Tag: entry
#, no-c-format
msgid "Path"
msgstr ""

#. Tag: entry
#, no-c-format
msgid "Description"
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<filename>/etc/named.conf</filename>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid "The main configuration file."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<filename class=\"directory\">/etc/named/</filename>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"An auxiliary directory for configuration files that are included in the main"
" configuration file."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The configuration file consists of a collection of statements with nested "
"options surrounded by opening and closing curly brackets (that is, "
"<literal>{</literal> and <literal>}</literal>). Note that when editing the "
"file, you have to be careful not to make any syntax error, otherwise the "
"<systemitem class=\"service\">named</systemitem> service will not start. A "
"typical <filename>/etc/named.conf</filename> file is organized as follows:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"<replaceable>statement-1</replaceable> [\"<replaceable>statement-1-name</replaceable>\"] [<replaceable>statement-1-class</replaceable>] {\n"
"  <replaceable>option-1</replaceable>;\n"
"  <replaceable>option-2</replaceable>;\n"
"  <replaceable>option-N</replaceable>;\n"
"};\n"
"<replaceable>statement-2</replaceable> [\"<replaceable>statement-2-name</replaceable>\"] [<replaceable>statement-2-class</replaceable>] {\n"
"  <replaceable>option-1</replaceable>;\n"
"  <replaceable>option-2</replaceable>;\n"
"  <replaceable>option-N</replaceable>;\n"
"};\n"
"<replaceable>statement-N</replaceable> [\"<replaceable>statement-N-name</replaceable>\"] [<replaceable>statement-N-class</replaceable>] {\n"
"  <replaceable>option-1</replaceable>;\n"
"  <replaceable>option-2</replaceable>;\n"
"  <replaceable>option-N</replaceable>;\n"
"};"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Note: Running BIND in a Chroot Environment"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"If you have installed the <package>bind-chroot</package> package, the BIND "
"service will run in the <filename "
"class=\"directory\">/var/named/chroot</filename> environment. In that case, "
"the initialization script will mount the above configuration files using the"
" <command>mount --bind</command> command, so that you can manage the "
"configuration outside this environment."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Common Statement Types"
msgstr "Tipo di istruzioni comuni"

#. Tag: para
#, no-c-format
msgid ""
"The following types of statements are commonly used in "
"<filename>/etc/named.conf</filename>:"
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>configuration</secondary> "
"<tertiary><option>acl</option> statement</tertiary> </indexterm> "
"<option>acl</option>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <option>acl</option> (Access Control List) statement allows you to "
"define groups of hosts, so that they can be permitted or denied access to "
"the nameserver. It takes the following form:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"acl <replaceable>acl-name</replaceable> {\n"
"  <replaceable>match-element</replaceable>;\n"
"  ...\n"
"};"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <replaceable>acl-name</replaceable> statement name is the name of the "
"access control list, and the <replaceable>match-element</replaceable> option"
" is usually an individual IP address (such as <literal>10.0.1.1</literal>) "
"or a CIDR network notation (for example, <literal>10.0.1.0/24</literal>). "
"For a list of already defined keywords, see <xref linkend=\"table-bind-"
"namedconf-common-acl\" />."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Predefined access control lists"
msgstr ""

#. Tag: entry
#, no-c-format
msgid "Keyword"
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>any</option>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid "Matches every IP address."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>localhost</option>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid "Matches any IP address that is in use by the local system."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>localnets</option>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"Matches any IP address on any network to which the local system is "
"connected."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>none</option>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid "Does not match any IP address."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <option>acl</option> statement can be especially useful with conjunction"
" with other statements such as <option>options</option>. <xref linkend"
"=\"example-bind-namedconf-common-acl\" /> defines two access control lists, "
"<literal>black-hats</literal> and <literal>red-hats</literal>, and adds "
"<literal>black-hats</literal> on the blacklist while granting <literal>red-"
"hats</literal> a normal access."
msgstr ""

#. Tag: title
#, no-c-format
msgid ""
"Using <option>acl</option> in conjunction with <option>options</option>"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"acl black-hats {\n"
"  10.0.2.0/24;\n"
"  192.168.0.0/24;\n"
"  1234:5678::9abc/24;\n"
"};\n"
"acl red-hats {\n"
"  10.0.1.0/24;\n"
"};\n"
"options {\n"
"  blackhole { black-hats; };\n"
"  allow-query { red-hats; };\n"
"  allow-query-cache { red-hats; };\n"
"};"
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>configuration</secondary> "
"<tertiary><option>include</option> statement</tertiary> </indexterm> "
"<option>include</option>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <option>include</option> statement allows you to include files in the "
"<filename>/etc/named.conf</filename>, so that potentially sensitive data can"
" be placed in a separate file with restricted permissions. It takes the "
"following form:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "include \"<replaceable>file-name</replaceable>\""
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <replaceable>file-name</replaceable> statement name is an absolute path "
"to a file."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Including a file to <filename>/etc/named.conf</filename>"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "include \"/etc/named.rfc1912.zones\";"
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>configuration</secondary> "
"<tertiary><option>options</option> statement</tertiary> </indexterm> "
"<option>options</option>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <option>options</option> statement allows you to define global server "
"configuration options as well as to set defaults for other statements. It "
"can be used to specify the location of the <systemitem "
"class=\"service\">named</systemitem> working directory, the types of queries"
" allowed, and much more. It takes the following form:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"options {\n"
"  <replaceable>option</replaceable>;\n"
"  ...\n"
"};"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"For a list of frequently used <replaceable>option</replaceable> directives, "
"see <xref linkend=\"table-bind-namedconf-common-options\" /> below."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Commonly used options"
msgstr ""

#. Tag: entry
#, no-c-format
msgid "Option"
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>allow-query</option>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"Specifies which hosts are allowed to query the nameserver for authoritative "
"resource records. It accepts an access control lists, a collection of IP "
"addresses, or networks in the CIDR notation. All hosts are allowed by "
"default."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>allow-query-cache</option>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"Specifies which hosts are allowed to query the nameserver for non-"
"authoritative data such as recursive queries. Only "
"<literal>localhost</literal> and <literal>localnets</literal> are allowed by"
" default."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>blackhole</option>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"Specifies which hosts are <emphasis>not</emphasis> allowed to query the "
"nameserver. This option should be used when particular host or network "
"floods the server with requests. The default option is "
"<literal>none</literal>."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>directory</option>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"Specifies a working directory for the <systemitem "
"class=\"service\">named</systemitem> service. The default option is "
"<literal>/var/named/</literal>."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>dnssec-enable</option>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"Specifies whether to return DNSSEC related resource records. The default "
"option is <literal>yes</literal>."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>dnssec-validation</option>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"Specifies whether to prove that resource records are authentic via DNSSEC. "
"The default option is <option>yes</option>."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>forwarders</option>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"Specifies a list of valid IP addresses for nameservers to which the requests"
" should be forwarded for resolution."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>forward</option>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Specifies the behavior of the <option>forwarders</option> directive. It "
"accepts the following options:"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"<literal>first</literal> — The server will query the nameservers listed in "
"the <option>forwarders</option> directive before attempting to resolve the "
"name on its own."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"<literal>only</literal> — When unable to query the nameservers listed in the"
" <option>forwarders</option> directive, the server will not attempt to "
"resolve the name on its own."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>listen-on</option>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"Specifies the IPv4 network interface on which to listen for queries. On a "
"DNS server that also acts as a gateway, you can use this option to answer "
"queries originating from a single network only. All IPv4 interfaces are used"
" by default."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>listen-on-v6</option>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"Specifies the IPv6 network interface on which to listen for queries. On a "
"DNS server that also acts as a gateway, you can use this option to answer "
"queries originating from a single network only. All IPv6 interfaces are used"
" by default."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>max-cache-size</option>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"Specifies the maximum amount of memory to be used for server caches. When "
"the limit is reached, the server causes records to expire prematurely so "
"that the limit is not exceeded. In a server with multiple views, the limit "
"applies separately to the cache of each view. The default option is "
"<literal>32M</literal>."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>notify</option>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Specifies whether to notify the secondary nameservers when a zone is "
"updated. It accepts the following options:"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"<option>yes</option> — The server will notify all secondary nameservers."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"<option>no</option> — The server will <emphasis>not</emphasis> notify any "
"secondary nameserver."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"<option>master-only</option> — The server will notify primary server for the"
" zone only."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"<option>explicit</option> — The server will notify only the secondary "
"servers that are specified in the <option>also-notify</option> list within a"
" zone statement."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>pid-file</option>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"Specifies the location of the process ID file created by the <systemitem "
"class=\"service\">named</systemitem> service."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>recursion</option>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"Specifies whether to act as a recursive server. The default option is "
"<literal>yes</literal>."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>statistics-file</option>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"Specifies an alternate location for statistics files. The "
"<filename>/var/named/named.stats</filename> file is used by default."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Important: Restrict Recursive Servers to Selected Clients Only"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"To prevent distributed denial of service (DDoS) attacks, it is recommended "
"that you use the <option>allow-query-cache</option> option to restrict "
"recursive DNS services for a particular subset of clients only."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Refer to the <citetitle>BIND 9 Administrator Reference Manual</citetitle> "
"referenced in <xref linkend=\"s2-bind-installed-docs\" />, and the "
"<filename>named.conf</filename> manual page for a complete list of available"
" options."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Using the <option>options</option> statement"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"options {\n"
"  allow-query       { localhost; };\n"
"  listen-on port    53 { 127.0.0.1; };\n"
"  listen-on-v6 port 53 { ::1; };\n"
"  max-cache-size    256M;\n"
"  directory         \"/var/named\";\n"
"  statistics-file   \"/var/named/data/named_stats.txt\";\n"
"\n"
"  recursion         yes;\n"
"  dnssec-enable     yes;\n"
"  dnssec-validation yes;\n"
"};"
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>configuration</secondary> "
"<tertiary><option>zone</option> statement</tertiary> </indexterm> "
"<option>zone</option>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <option>zone</option> statement allows you to define the characteristics"
" of a zone, such as the location of its configuration file and zone-specific"
" options, and can be used to override the global <option>options</option> "
"statements. It takes the following form:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"zone <replaceable>zone-name</replaceable> [<replaceable>zone-class</replaceable>] {\n"
"  <replaceable>option</replaceable>;\n"
"  ...\n"
"};"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <replaceable>zone-name</replaceable> attribute is the name of the zone, "
"<replaceable>zone-class</replaceable> is the optional class of the zone, and"
" <replaceable>option</replaceable> is a <option>zone</option> statement "
"option as described in <xref linkend=\"table-bind-namedconf-common-zone\" "
"/>."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <replaceable>zone-name</replaceable> attribute is particularly "
"important, as it is the default value assigned for the "
"<option>$ORIGIN</option> directive used within the corresponding zone file "
"located in the <filename>/var/named/</filename> directory. The <systemitem "
"class=\"service\">named</systemitem> daemon appends the name of the zone to "
"any non-fully qualified domain name listed in the zone file. For example, if"
" a <option>zone</option> statement defines the namespace for "
"<literal>example.com</literal>, use <literal>example.com</literal> as the "
"<replaceable>zone-name</replaceable> so that it is placed at the end of "
"hostnames within the <literal>example.com</literal> zone file."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"For more information about zone files, refer to <xref linkend=\"s1-bind-"
"zone\" />."
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"Specifies which clients are allowed to request information about this zone. "
"This option overrides global <option>allow-query</option> option. All query "
"requests are allowed by default."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>allow-transfer</option>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"Specifies which secondary servers are allowed to request a transfer of the "
"zone's information. All transfer requests are allowed by default."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>allow-update</option>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Specifies which hosts are allowed to dynamically update information in their"
" zone. The default option is to deny all dynamic update requests."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Note that you should be careful when allowing hosts to update information "
"about their zone. Do not set IP addresses in this option unless the server "
"is in the trusted network. Instead, use TSIG key as described in <xref "
"linkend=\"s2-bind-features-tsig\" />."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>file</option>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"Specifies the name of the file in the <systemitem "
"class=\"service\">named</systemitem> working directory that contains the "
"zone's configuration data."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>masters</option>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"Specifies from which IP addresses to request authoritative zone information."
" This option is used only if the zone is defined as <option>type</option> "
"<option>slave</option>."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<option>type</option>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Specifies the zone type. It accepts the following options:"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"<option>delegation-only</option> — Enforces the delegation status of "
"infrastructure zones such as COM, NET, or ORG. Any answer that is received "
"without an explicit or implicit delegation is treated as "
"<literal>NXDOMAIN</literal>. This option is only applicable in TLDs or root "
"zone files used in recursive or caching implementations."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"<option>forward</option> — Forwards all requests for information about this "
"zone to other nameservers."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"<option>hint</option> — A special type of zone used to point to the root "
"nameservers which resolve queries when a zone is not otherwise known. No "
"configuration beyond the default is necessary with a <option>hint</option> "
"zone."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"<option>master</option> — Designates the nameserver as authoritative for "
"this zone. A zone should be set as the <option>master</option> if the zone's"
" configuration files reside on the system."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"<option>slave</option> — Designates the nameserver as a slave server for "
"this zone. Master server is specified in <option>masters</option> directive."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Most changes to the <filename>/etc/named.conf</filename> file of a primary "
"or secondary nameserver involve adding, modifying, or deleting "
"<option>zone</option> statements, and only a small subset of "
"<option>zone</option> statement options is usually needed for a nameserver "
"to work efficiently."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"In <xref linkend=\"example-bind-namedconf-common-zone-primary\" />, the zone"
" is identified as <literal>example.com</literal>, the type is set to "
"<literal>master</literal>, and the <systemitem "
"class=\"service\">named</systemitem> service is instructed to read the "
"<filename>/var/named/example.com.zone</filename> file. It also allows only a"
" secondary nameserver (<literal>192.168.0.2</literal>) to transfer the zone."
msgstr ""

#. Tag: title
#, no-c-format
msgid "A <option>zone</option> statement for a primary nameserver"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"zone \"example.com\" IN {\n"
"  type master;\n"
"  file \"example.com.zone\";\n"
"  allow-transfer { 192.168.0.2; };\n"
"};"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"A secondary server's <option>zone</option> statement is slightly different. "
"The type is set to <literal>slave</literal>, and the "
"<literal>masters</literal> directive is telling <systemitem "
"class=\"service\">named</systemitem> the IP address of the master server."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"In <xref linkend=\"example-bind-namedconf-common-zone-secondary\" />, the "
"<systemitem class=\"service\">named</systemitem> service is configured to "
"query the primary server at the <literal>192.168.0.1</literal> IP address "
"for information about the <literal>example.com</literal> zone. The received "
"information is then saved to the "
"<filename>/var/named/slaves/example.com.zone</filename> file. Note that you "
"have to put all slave zones to <filename>/var/named/slaves</filename> "
"directory, otherwise the service will fail to transfer the zone."
msgstr ""

#. Tag: title
#, no-c-format
msgid "A <option>zone</option> statement for a secondary nameserver"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"zone \"example.com\" {\n"
"  type slave;\n"
"  file \"slaves/example.com.zone\";\n"
"  masters { 192.168.0.1; };\n"
"};"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Other Statement Types"
msgstr "Altri tipi di istruzione"

#. Tag: para
#, no-c-format
msgid ""
"The following types of statements are less commonly used in "
"<filename>/etc/named.conf</filename>:"
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>configuration</secondary> "
"<tertiary><option>controls</option> statement</tertiary> </indexterm> "
"<option>controls</option>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <option>controls</option> statement allows you to configure various "
"security requirements necessary to use the <command>rndc</command> command "
"to administer the <systemitem class=\"service\">named</systemitem> service."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Refer to <xref linkend=\"s1-bind-rndc\" /> for more information on the "
"<command>rndc</command> utility and its usage."
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>configuration</secondary> "
"<tertiary><option>key</option> statement</tertiary> </indexterm> "
"<option>key</option>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <option>key</option> statement allows you to define a particular key by "
"name. Keys are used to authenticate various actions, such as secure updates "
"or the use of the <command>rndc</command> command. Two options are used with"
" <option>key</option>:"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"<option>algorithm <replaceable>algorithm-name</replaceable></option> — The "
"type of algorithm to be used (for example, <literal>hmac-md5</literal>)."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"<option>secret \"<replaceable>key-value</replaceable>\"</option> — The "
"encrypted key."
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>configuration</secondary> "
"<tertiary><option>logging</option> statement</tertiary> </indexterm> "
"<option>logging</option>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <option>logging</option> statement allows you to use multiple types of "
"logs, so called <firstterm>channels</firstterm>. By using the "
"<option>channel</option> option within the statement, you can construct a "
"customized type of log with its own file name (<option>file</option>), size "
"limit (<option>size</option>), versioning (<option>version</option>), and "
"level of importance (<option>severity</option>). Once a customized channel "
"is defined, a <option>category</option> option is used to categorize the "
"channel and begin logging when the <systemitem "
"class=\"service\">named</systemitem> service is restarted."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"By default, <systemitem class=\"service\">named</systemitem> sends standard "
"messages to the <systemitem class=\"service\">rsyslog</systemitem> daemon, "
"which places them in <filename>/var/log/messages</filename>. Several "
"standard channels are built into BIND with various severity levels, such as "
"<literal>default_syslog</literal> (which handles informational logging "
"messages) and <literal>default_debug</literal> (which specifically handles "
"debugging messages). A default category, called <literal>default</literal>, "
"uses the built-in channels to do normal logging without any special "
"configuration."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Customizing the logging process can be a very detailed process and is beyond"
" the scope of this chapter. For information on creating custom BIND logs, "
"refer to the <citetitle>BIND 9 Administrator Reference Manual</citetitle> "
"referenced in <xref linkend=\"s2-bind-installed-docs\" />."
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>configuration</secondary> "
"<tertiary><option>server</option> statement</tertiary> </indexterm> "
"<option>server</option>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <option>server</option> statement allows you to specify options that "
"affect how the <systemitem class=\"service\">named</systemitem> service "
"should respond to remote nameservers, especially with regard to "
"notifications and zone transfers."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <option>transfer-format</option> option controls the number of resource "
"records that are sent with each message. It can be either <literal>one-"
"answer</literal> (only one resource record), or <literal>many-"
"answers</literal> (multiple resource records). Note that while the <literal"
">many-answers</literal> option is more efficient, it is not supported by "
"older versions of BIND."
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>configuration</secondary> "
"<tertiary><option>trusted-keys</option> statement</tertiary> </indexterm> "
"<option>trusted-keys</option>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <option>trusted-keys</option> statement allows you to specify assorted "
"public keys used for secure DNS (DNSSEC). Refer to <xref linkend=\"s2-bind-"
"features-dnssec\" /> for more information on this topic."
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>configuration</secondary> "
"<tertiary><option>view</option> statement</tertiary> </indexterm> "
"<option>view</option>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <option>view</option> statement allows you to create special views "
"depending upon which network the host querying the nameserver is on. This "
"allows some hosts to receive one answer regarding a zone while other hosts "
"receive totally different information. Alternatively, certain zones may only"
" be made available to particular trusted hosts while non-trusted hosts can "
"only make queries for other zones."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Multiple views can be used as long as their names are unique. The <option"
">match-clients</option> option allows you to specify the IP addresses that "
"apply to a particular view. If the <option>options</option> statement is "
"used within a view, it overrides the already configured global options. "
"Finally, most <option>view</option> statements contain multiple "
"<option>zone</option> statements that apply to the <option>match-"
"clients</option> list."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Note that the order in which the <option>view</option> statements are listed"
" is important, as the first statement that matches a particular client's IP "
"address is used. For more information on this topic, refer to <xref "
"linkend=\"s2-bind-features-views\" />."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Comment Tags"
msgstr "Tag di commento"

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>configuration</secondary> "
"<tertiary>comment tags</tertiary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Additionally to statements, the <filename>/etc/named.conf</filename> file "
"can also contain comments. Comments are ignored by the <systemitem "
"class=\"service\">named</systemitem> service, but can prove useful when "
"providing additional information to a user. The following are valid comment "
"tags:"
msgstr ""

#. Tag: term
#, no-c-format
msgid "<literal>//</literal>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Any text after the <literal>//</literal> characters to the end of the line "
"is considered a comment. For example:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "notify yes;  // notify all secondary nameservers"
msgstr ""

#. Tag: term
#, no-c-format
msgid "<literal>#</literal>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Any text after the <literal>#</literal> character to the end of the line is "
"considered a comment. For example:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "notify yes;  # notify all secondary nameservers"
msgstr ""

#. Tag: term
#, no-c-format
msgid "<literal>/*</literal> and <literal>*/</literal>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Any block of text enclosed in <literal>/*</literal> and "
"<literal>*/</literal> is considered a comment. For example:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "notify yes;  /* notify all secondary nameservers */"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Editing Zone Files"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>directories</secondary> "
"<tertiary><filename class=\"directory\">/var/named/</filename></tertiary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>directories</secondary> "
"<tertiary><filename "
"class=\"directory\">/var/named/slaves/</filename></tertiary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>directories</secondary> "
"<tertiary><filename "
"class=\"directory\">/var/named/dynamic/</filename></tertiary>"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>directories</secondary> "
"<tertiary><filename "
"class=\"directory\">/var/named/data/</filename></tertiary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"As outlined in <xref linkend=\"s2-bind-introduction-zones\" />, zone files "
"contain information about a namespace. They are stored in the <systemitem "
"class=\"service\">named</systemitem> working directory located in <filename "
"class=\"directory\">/var/named/</filename> by default, and each zone file is"
" named according to the <option>file</option> option in the "
"<option>zone</option> statement, usually in a way that relates to the domain"
" in question and identifies the file as containing zone data, such as "
"<filename>example.com.zone</filename>."
msgstr ""

#. Tag: title
#, no-c-format
msgid "The <systemitem class=\"service\">named</systemitem> service zone files"
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<filename class=\"directory\">/var/named/</filename>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"The working directory for the <systemitem "
"class=\"service\">named</systemitem> service. The nameserver is "
"<emphasis>not</emphasis> allowed to write to this directory."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<filename class=\"directory\">/var/named/slaves/</filename>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"The directory for secondary zones. This directory is writable by the "
"<systemitem class=\"service\">named</systemitem> service."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<filename class=\"directory\">/var/named/dynamic/</filename>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"The directory for other files, such as dynamic DNS (DDNS) zones or managed "
"DNSSEC keys. This directory is writable by the <systemitem "
"class=\"service\">named</systemitem> service."
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<filename class=\"directory\">/var/named/data/</filename>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"The directory for various statistics and debugging files. This directory is "
"writable by the <systemitem class=\"service\">named</systemitem> service."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"A zone file consists of directives and resource records. Directives tell the"
" nameserver to perform tasks or apply special settings to the zone, resource"
" records define the parameters of the zone and assign identities to "
"individual hosts. While the directives are optional, the resource records "
"are required in order to provide name service to a zone."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"All directives and resource records should be entered on individual lines."
msgstr ""
"Tutte le direttive ed i record dovrebbero essere inseriti su righe diverse."

#. Tag: title
#, no-c-format
msgid "Common Directives"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Directives begin with the dollar sign character (that is, "
"<literal>$</literal>) followed by the name of the directive, and usually "
"appear at the top of the file. The following directives are commonly used in"
" zone files:"
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>zones</secondary> "
"<tertiary><command>$INCLUDE</command> directive</tertiary> </indexterm> "
"<command>$INCLUDE</command>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <command>$INCLUDE</command> directive allows you to include another file"
" at the place where it appears, so that other zone settings can be stored in"
" a separate zone file."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Using the <command>$INCLUDE</command> directive"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "$INCLUDE /var/named/penguin.example.com"
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>zones</secondary> "
"<tertiary><command>$ORIGIN</command> directive</tertiary> </indexterm> "
"<command>$ORIGIN</command>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <command>$ORIGIN</command> directive allows you to append the domain "
"name to unqualified records, such as those with the hostname only. Note that"
" the use of this directive is not necessary if the zone is specified in "
"<filename>/etc/named.conf</filename>, since the zone name is used by "
"default."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"In <xref linkend=\"example-bind-zone-directive-origin\" />, any names used "
"in resource records that do not end in a trailing period (that is, the "
"<literal>.</literal> character) are appended with "
"<literal>example.com</literal>."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Using the <command>$ORIGIN</command> directive"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "$ORIGIN example.com."
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>zones</secondary> "
"<tertiary><command>$TTL</command> directive</tertiary> </indexterm> "
"<command>$TTL</command>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <command>$TTL</command> directive allows you to set the default "
"<firstterm>Time to Live</firstterm> (TTL) value for the zone, that is, how "
"long is a zone record valid. Each resource record can contain its own TTL "
"value, which overrides this directive."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Increasing this value allows remote nameservers to cache the zone "
"information for a longer period of time, reducing the number of queries for "
"the zone and lengthening the amount of time required to proliferate resource"
" record changes."
msgstr ""
"Impostando un valore pi&ugrave; alto si indica ai server dei nomi di "
"conservare in memoria queste informazioni di zona per un periodo di tempo "
"maggiore. Ci&ograve; riduce il numero di richieste relative a questa zona, "
"ma allunga anche il tempo necessario per modificare il record di risorse."

#. Tag: title
#, no-c-format
msgid "Using the <command>$TTL</command> directive"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "$TTL 1D"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Common Resource Records"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The following resource records are commonly used in zone files:"
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>zones</secondary> "
"<tertiary><command>A</command> (Address) resource record</tertiary> "
"</indexterm> <command>A</command>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <firstterm>Address</firstterm> record specifies an IP address to be "
"assigned to a name. It takes the following form:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"<replaceable>hostname</replaceable> IN A <replaceable>IP-"
"address</replaceable>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"If the <replaceable>hostname</replaceable> value is omitted, the record will"
" point to the last specified <replaceable>hostname</replaceable>."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"In <xref linkend=\"example-bind-zone-rr-a\" />, the requests for <systemitem"
" class=\"domainname\">server1.example.com</systemitem> are pointed to "
"<literal>10.0.1.3</literal> or <literal>10.0.1.5</literal>."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Using the <command>A</command> resource record"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"server1  IN  A  10.0.1.3\n"
"         IN  A  10.0.1.5"
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>zones</secondary> "
"<tertiary><command>CNAME</command> (Canonical Name) resource "
"record</tertiary> </indexterm> <command>CNAME</command>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <firstterm>Canonical Name</firstterm> record maps one name to another. "
"Because of this, this type of record is sometimes referred to as an "
"<firstterm>alias record</firstterm>. It takes the following form:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"<replaceable>alias-name</replaceable> IN CNAME <replaceable>real-"
"name</replaceable>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"<command>CNAME</command> records are most commonly used to point to services"
" that use a common naming scheme, such as <literal>www</literal> for Web "
"servers. However, there are multiple restrictions for their usage:"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"CNAME records should not point to other CNAME records. This is mainly to "
"avoid possible infinite loops."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"CNAME records should not contain other resource record types (such as A, NS,"
" MX, etc.). The only exception are DNSSEC related records (that is, RRSIG, "
"NSEC, etc.) when the zone is signed."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Other resource record that point to the fully qualified domain name (FQDN) "
"of a host (that is, NS, MX, PTR) should not point to a CNAME record."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"In <xref linkend=\"example-bind-zone-rr-cname\" />, the <command>A</command>"
" record binds a hostname to an IP address, while the "
"<command>CNAME</command> record points the commonly used "
"<literal>www</literal> hostname to it."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Using the <command>CNAME</command> resource record"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"server1  IN  A      10.0.1.5\n"
"www      IN  CNAME  server1"
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>zones</secondary> "
"<tertiary><command>MX</command> (Mail Exchange) resource record</tertiary> "
"</indexterm> <command>MX</command>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <firstterm>Mail Exchange</firstterm> record specifies where the mail "
"sent to a particular namespace controlled by this zone should go. It takes "
"the following form:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"IN MX <replaceable>preference-value</replaceable> <replaceable>email-server-"
"name</replaceable>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <replaceable>email-server-name</replaceable> is a fully qualified domain"
" name (FQDN). The <replaceable>preference-value</replaceable> allows "
"numerical ranking of the email servers for a namespace, giving preference to"
" some email systems over others. The <command>MX</command> resource record "
"with the lowest <replaceable>preference-value</replaceable> is preferred "
"over the others. However, multiple email servers can possess the same value "
"to distribute email traffic evenly among them."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"In <xref linkend=\"example-bind-zone-rr-mx\" />, the first <systemitem "
"class=\"domainname\">mail.example.com</systemitem> email server is preferred"
" to the <systemitem class=\"domainname\">mail2.example.com</systemitem> "
"email server when receiving email destined for the <systemitem "
"class=\"domainname\">example.com</systemitem> domain."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Using the <command>MX</command> resource record"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"example.com.  IN  MX  10  mail.example.com.\n"
"              IN  MX  20  mail2.example.com."
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>zones</secondary> "
"<tertiary><command>NS</command> (Nameserver) resource record</tertiary> "
"</indexterm> <command>NS</command>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <firstterm>Nameserver</firstterm> record announces authoritative "
"nameservers for a particular zone. It takes the following form:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "IN NS <replaceable>nameserver-name</replaceable>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <replaceable>nameserver-name</replaceable> should be a fully qualified "
"domain name (FQDN). Note that when two nameservers are listed as "
"authoritative for the domain, it is not important whether these nameservers "
"are secondary nameservers, or if one of them is a primary server. They are "
"both still considered authoritative."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Using the <command>NS</command> resource record"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"IN  NS  dns1.example.com.\n"
"IN  NS  dns2.example.com."
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>zones</secondary> "
"<tertiary><command>PTR</command> (Pointer) resource record</tertiary> "
"</indexterm> <command>PTR</command>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <firstterm>Pointer</firstterm> record points to another part of the "
"namespace. It takes the following form:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"<replaceable>last-IP-digit</replaceable> IN PTR <replaceable>FQDN-of-"
"system</replaceable>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <replaceable>last-IP-digit</replaceable> directive is the last number in"
" an IP address, and the <replaceable>FQDN-of-system</replaceable> is a fully"
" qualified domain name (FQDN)."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"<command>PTR</command> records are primarily used for reverse name "
"resolution, as they point IP addresses back to a particular name. Refer to "
"<xref linkend=\"s2-bind-configuration-zone-reverse\" /> for more examples of"
" <command>PTR</command> records in use."
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>zones</secondary> "
"<tertiary><command>SOA</command> (Start of Authority) resource "
"record</tertiary> </indexterm> <command>SOA</command>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <firstterm>Start of Authority</firstterm> record announces important "
"authoritative information about a namespace to the nameserver. Located after"
" the directives, it is the first resource record in a zone file. It takes "
"the following form:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"@  IN  SOA  <replaceable>primary-name-server</replaceable> <replaceable>hostmaster-email</replaceable> (\n"
"       <replaceable>serial-number</replaceable>\n"
"       <replaceable>time-to-refresh</replaceable>\n"
"       <replaceable>time-to-retry</replaceable>\n"
"       <replaceable>time-to-expire</replaceable>\n"
"       <replaceable>minimum-TTL</replaceable> )"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The directives are as follows:"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <literal>@</literal> symbol places the <command>$ORIGIN</command> "
"directive (or the zone's name if the <command>$ORIGIN</command> directive is"
" not set) as the namespace being defined by this <command>SOA</command> "
"resource record."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <replaceable>primary-name-server</replaceable> directive is the hostname"
" of the primary nameserver that is authoritative for this domain."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <replaceable>hostmaster-email</replaceable> directive is the email of "
"the person to contact about the namespace."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <replaceable>serial-number</replaceable> directive is a numerical value "
"incremented every time the zone file is altered to indicate it is time for "
"the <systemitem class=\"service\">named</systemitem> service to reload the "
"zone."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <replaceable>time-to-refresh</replaceable> directive is the numerical "
"value secondary nameservers use to determine how long to wait before asking "
"the primary nameserver if any changes have been made to the zone."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <replaceable>time-to-retry</replaceable> directive is a numerical value "
"used by secondary nameservers to determine the length of time to wait before"
" issuing a refresh request in the event that the primary nameserver is not "
"answering. If the primary server has not replied to a refresh request before"
" the amount of time specified in the <replaceable>time-to-"
"expire</replaceable> directive elapses, the secondary servers stop "
"responding as an authority for requests concerning that namespace."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"In BIND 4 and 8, the <replaceable>minimum-TTL</replaceable> directive is the"
" amount of time other nameservers cache the zone's information. In BIND 9, "
"it defines how long negative answers are cached for. Caching of negative "
"answers can be set to a maximum of 3 hours (that is, <option>3H</option>)."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"When configuring BIND, all times are specified in seconds. However, it is "
"possible to use abbreviations when specifying units of time other than "
"seconds, such as minutes (<literal>M</literal>), hours "
"(<literal>H</literal>), days (<literal>D</literal>), and weeks "
"(<literal>W</literal>). <xref linkend=\"tb-bind-seconds\" /> shows an amount"
" of time in seconds and the equivalent time in another format."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Seconds compared to other time units"
msgstr "Secondi paragonati ad altre unit&agrave; di tempo"

#. Tag: entry
#, no-c-format
msgid "Seconds"
msgstr "Secondi"

#. Tag: entry
#, no-c-format
msgid "Other Time Units"
msgstr "Altre unit&agrave; di tempo"

#. Tag: entry
#, no-c-format
msgid "60"
msgstr ""

#. Tag: entry
#, no-c-format
msgid "<literal>1M</literal>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid "1800"
msgstr "1800"

#. Tag: entry
#, no-c-format
msgid "<literal>30M</literal>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid "3600"
msgstr "3600"

#. Tag: entry
#, no-c-format
msgid "<literal>1H</literal>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid "10800"
msgstr "10800"

#. Tag: entry
#, no-c-format
msgid "<literal>3H</literal>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid "21600"
msgstr "21600"

#. Tag: entry
#, no-c-format
msgid "<literal>6H</literal>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid "43200"
msgstr "43200"

#. Tag: entry
#, no-c-format
msgid "<literal>12H</literal>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid "86400"
msgstr "86400"

#. Tag: entry
#, no-c-format
msgid "<literal>1D</literal>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid "259200"
msgstr "259200"

#. Tag: entry
#, no-c-format
msgid "<literal>3D</literal>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid "604800"
msgstr "604800"

#. Tag: entry
#, no-c-format
msgid "<literal>1W</literal>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid "31536000"
msgstr "31536000"

#. Tag: entry
#, no-c-format
msgid "<literal>365D</literal>"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Using the <command>SOA</command> resource record"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"@  IN  SOA  dns1.example.com.  hostmaster.example.com. (\n"
"       2001062501  ; serial\n"
"       21600       ; refresh after 6 hours\n"
"       3600        ; retry after 1 hour\n"
"       604800      ; expire after 1 week\n"
"       86400 )     ; minimum TTL of 1 day"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>zones</secondary> <tertiary>comment "
"tags</tertiary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Additionally to resource records and directives, a zone file can also "
"contain comments. Comments are ignored by the <systemitem "
"class=\"service\">named</systemitem> service, but can prove useful when "
"providing additional information to the user. Any text after the semicolon "
"character (that is, <literal>;</literal>) to the end of the line is "
"considered a comment. For example:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "   604800  ; expire after 1 week"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Example Usage"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The following examples show the basic usage of zone files."
msgstr ""

#. Tag: title
#, no-c-format
msgid "A Simple Zone File"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>zones</secondary> <tertiary>example "
"usage</tertiary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"<xref linkend=\"example-bind-zone-examples-basic\" /> demonstrates the use "
"of standard directives and <command>SOA</command> values."
msgstr ""

#. Tag: title
#, no-c-format
msgid "A simple zone file"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"$ORIGIN example.com.\n"
"$TTL 86400\n"
"@         IN  SOA  dns1.example.com.  hostmaster.example.com. (\n"
"              2001062501  ; serial\n"
"              21600       ; refresh after 6 hours\n"
"              3600        ; retry after 1 hour\n"
"              604800      ; expire after 1 week\n"
"              86400 )     ; minimum TTL of 1 day\n"
";\n"
";\n"
"          IN  NS     dns1.example.com.\n"
"          IN  NS     dns2.example.com.\n"
"dns1      IN  A      10.0.1.1\n"
"          IN  AAAA   aaaa:bbbb::1\n"
"dns2      IN  A      10.0.1.2\n"
"          IN  AAAA   aaaa:bbbb::2\n"
";\n"
";\n"
"@         IN  MX     10  mail.example.com.\n"
"          IN  MX     20  mail2.example.com.\n"
"mail      IN  A      10.0.1.5\n"
"          IN  AAAA   aaaa:bbbb::5\n"
"mail2     IN  A      10.0.1.6\n"
"          IN  AAAA   aaaa:bbbb::6\n"
";\n"
";\n"
"; This sample zone file illustrates sharing the same IP addresses\n"
"; for multiple services:\n"
";\n"
"services  IN  A      10.0.1.10\n"
"          IN  AAAA   aaaa:bbbb::10\n"
"          IN  A      10.0.1.11\n"
"          IN  AAAA   aaaa:bbbb::11\n"
"\n"
"ftp       IN  CNAME  services.example.com.\n"
"www       IN  CNAME  services.example.com.\n"
";\n"
";"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"In this example, the authoritative nameservers are set as <systemitem "
"class=\"domainname\">dns1.example.com</systemitem> and <systemitem "
"class=\"domainname\">dns2.example.com</systemitem>, and are tied to the "
"<systemitem class=\"ipaddress\">10.0.1.1</systemitem> and <systemitem "
"class=\"ipaddress\">10.0.1.2</systemitem> IP addresses respectively using "
"the <command>A</command> record."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The email servers configured with the <command>MX</command> records point to"
" <systemitem class=\"domainname\">mail</systemitem> and <systemitem "
"class=\"domainname\">mail2</systemitem> via <command>A</command> records. "
"Since these names do not end in a trailing period (that is, the "
"<literal>.</literal> character), the <command>$ORIGIN</command> domain is "
"placed after them, expanding them to <systemitem "
"class=\"domainname\">mail.example.com</systemitem> and <systemitem "
"class=\"domainname\">mail2.example.com</systemitem>."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Services available at the standard names, such as <systemitem "
"class=\"domainname\">www.example.com</systemitem> (<acronym>WWW</acronym>), "
"are pointed at the appropriate servers using the <command>CNAME</command> "
"record."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"This zone file would be called into service with a <command>zone</command> "
"statement in the <filename>/etc/named.conf</filename> similar to the "
"following:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"zone \"example.com\" IN {\n"
"  type master;\n"
"  file \"example.com.zone\";\n"
"  allow-update { none; };\n"
"};"
msgstr ""

#. Tag: title
#, no-c-format
msgid "A Reverse Name Resolution Zone File"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"A reverse name resolution zone file is used to translate an IP address in a "
"particular namespace into an fully qualified domain name (FQDN). It looks "
"very similar to a standard zone file, except that the <command>PTR</command>"
" resource records are used to link the IP addresses to a fully qualified "
"domain name as shown in <xref linkend=\"example-bind-zone-examples-reverse\""
" />."
msgstr ""

#. Tag: title
#, no-c-format
msgid "A reverse name resolution zone file"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"$ORIGIN 1.0.10.in-addr.arpa.\n"
"$TTL 86400\n"
"@  IN  SOA  dns1.example.com.  hostmaster.example.com. (\n"
"       2001062501  ; serial\n"
"       21600       ; refresh after 6 hours\n"
"       3600        ; retry after 1 hour\n"
"       604800      ; expire after 1 week\n"
"       86400 )     ; minimum TTL of 1 day\n"
";\n"
"@  IN  NS   dns1.example.com.\n"
";\n"
"1  IN  PTR  dns1.example.com.\n"
"2  IN  PTR  dns2.example.com.\n"
";\n"
"5  IN  PTR  server1.example.com.\n"
"6  IN  PTR  server2.example.com.\n"
";\n"
"3  IN  PTR  ftp.example.com.\n"
"4  IN  PTR  ftp.example.com."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"In this example, IP addresses <systemitem "
"class=\"ipaddress\">10.0.1.1</systemitem> through <systemitem "
"class=\"ipaddress\">10.0.1.6</systemitem> are pointed to the corresponding "
"fully qualified domain name."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"This zone file would be called into service with a <option>zone</option> "
"statement in the <filename>/etc/named.conf</filename> file similar to the "
"following:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"zone \"1.0.10.in-addr.arpa\" IN {\n"
"  type master;\n"
"  file \"example.com.rr.zone\";\n"
"  allow-update { none; };\n"
"};"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"There is very little difference between this example and a standard "
"<command>zone</command> statement, except for the zone name. Note that a "
"reverse name resolution zone requires the first three blocks of the IP "
"address reversed followed by <command>.in-addr.arpa</command>. This allows "
"the single block of IP numbers used in the reverse name resolution zone file"
" to be associated with the zone."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Using the <command>rndc</command> Utility"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <command>rndc</command> utility is a command line tool that allows you "
"to administer the <systemitem class=\"service\">named</systemitem> service, "
"both locally and from a remote machine. Its usage is as follows:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"<command>rndc</command> [<replaceable>option</replaceable>...] "
"<replaceable>command</replaceable> [<replaceable>command-"
"option</replaceable>]"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Configuring the Utility"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"To prevent unauthorized access to the service, <systemitem "
"class=\"service\">named</systemitem> must be configured to listen on the "
"selected port (that is, <literal>953</literal> by default), and an identical"
" key must be used by both the service and the <command>rndc</command> "
"utility."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Relevant files"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>files</secondary> "
"<tertiary><filename>/etc/named.conf</filename></tertiary> </indexterm> "
"<filename>/etc/named.conf</filename>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"The default configuration file for the <systemitem "
"class=\"service\">named</systemitem> service."
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>files</secondary> "
"<tertiary><filename>/etc/rndc.conf</filename></tertiary> </indexterm> "
"<filename>/etc/rndc.conf</filename>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"The default configuration file for the <command>rndc</command> utility."
msgstr ""

#. Tag: entry
#, no-c-format
msgid ""
"<indexterm> <primary>BIND</primary> <secondary>files</secondary> "
"<tertiary><filename>/etc/rndc.key</filename></tertiary> </indexterm> "
"<filename>/etc/rndc.key</filename>"
msgstr ""

#. Tag: entry
#, no-c-format
msgid "The default key location."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <command>rndc</command> configuration is located in "
"<filename>/etc/rndc.conf</filename>. If the file does not exist, the utility"
" will use the key located in <filename>/etc/rndc.key</filename>, which was "
"generated automatically during the installation process using the <command"
">rndc-confgen -a</command> command."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <systemitem class=\"service\">named</systemitem> service is configured "
"using the <option>controls</option> statement in the "
"<filename>/etc/named.conf</filename> configuration file as described in "
"<xref linkend=\"s2-bind-namedconf-state-other\" />. Unless this statement is"
" present, only the connections from the loopback address (that is, "
"<systemitem class=\"ipaddress\">127.0.0.1</systemitem>) will be allowed, and"
" the key located in <filename>/etc/rndc.key</filename> will be used."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"For more information on this topic, refer to manual pages and the "
"<citetitle>BIND 9 Administrator Reference Manual</citetitle> listed in <xref"
" linkend=\"s1-bind-additional-resources\" />."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Important: Set the Correct Permissions"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"To prevent unprivileged users from sending control commands to the service, "
"make sure only root is allowed to read the "
"<filename>/etc/rndc.key</filename> file:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "~]# <command>chmod o-rwx /etc/rndc.key</command>"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Checking the Service Status"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"To check the current status of the <systemitem "
"class=\"service\">named</systemitem> service, use the following command:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"~]# <command>rndc status</command>\n"
"version: 9.7.0-P2-RedHat-9.7.0-5.P2.el6\n"
"CPUs found: 1\n"
"worker threads: 1\n"
"number of zones: 16\n"
"debug level: 0\n"
"xfers running: 0\n"
"xfers deferred: 0\n"
"soa queries in progress: 0\n"
"query logging is OFF\n"
"recursive clients: 0/0/1000\n"
"tcp clients: 0/100\n"
"server is up and running"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Reloading the Configuration and Zones"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"To reload both the configuration file and zones, type the following at a "
"shell prompt:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"~]# <command>rndc reload</command>\n"
"server reload successful"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"This will reload the zones while keeping all previously cached responses, so"
" that you can make changes to the zone files without losing all stored name "
"resolutions."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"To reload a single zone, specify its name after the "
"<command>reload</command> command, for example:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"~]# <command>rndc reload localhost</command>\n"
"zone reload up-to-date"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Finally, to reload the configuration file and newly added zones only, type:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "~]# <command>rndc reconfig</command>"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Note: Modyfying Zones with Dynamic DNS"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"If you intend to manually modify a zone that uses Dynamic DNS (DDNS), make "
"sure you run the <command>freeze</command> command first:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "~]# <command>rndc freeze localhost</command>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Once you are finished, run the <command>thaw</command> command to allow the "
"DDNS again and reload the zone:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"~]# <command>rndc thaw localhost</command>\n"
"The zone reload and thaw was successful."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Updating Zone Keys"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"To update the DNSSEC keys and sign the zone, use the <command>sign</command>"
" command. For example:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "~]# <command>rndc sign localhost</command>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Note that to sign a zone with the above command, the <option>auto-"
"dnssec</option> option has to be set to <literal>maintain</literal> in the "
"zone statement. For instance:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"zone \"localhost\" IN {\n"
"  type master;\n"
"  file \"named.localhost\";\n"
"  allow-update { none; };\n"
"  auto-dnssec maintain;\n"
"};"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Enabling the DNSSEC Validation"
msgstr ""

#. Tag: para
#, no-c-format
msgid "To enable the DNSSEC validation, type the following at a shell prompt:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "~]# <command>rndc validation on</command>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Similarly, to disable this option, type:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "~]# <command>rndc validation off</command>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Refer to the <option>options</option> statement described in <xref "
"linkend=\"s2-bind-namedconf-state\" /> for information on how configure this"
" option in <filename>/etc/named.conf</filename>."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Enabling the Query Logging"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"To enable (or disable in case it is currently enabled) the query logging, "
"run the following command:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "~]# <command>rndc querylog</command>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"To check the current setting, use the <command>status</command> command as "
"described in <xref linkend=\"s2-bind-rndc-status\" />."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Using the <command>dig</command> Utility"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The <command>dig</command> utility is a command line tool that allows you to"
" perform DNS lookups and debug a nameserver configuration. Its typical usage"
" is as follows:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"<command>dig</command> [@<replaceable>server</replaceable>] "
"[<replaceable>option</replaceable>...] <replaceable>name</replaceable> "
"<replaceable>type</replaceable>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Refer to <xref linkend=\"s3-bind-zone-rr\" /> for a list of common "
"<replaceable>type</replaceable>s."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Looking Up a Nameserver"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"To look up a nameserver for a particular domain, use the command in the "
"following form:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "<command>dig</command> <replaceable>name</replaceable> NS"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"In <xref linkend=\"example-bind-dig-ns\" />, the <command>dig</command> "
"utility is used to display nameservers for <systemitem "
"class=\"domainname\">example.com</systemitem>."
msgstr ""

#. Tag: title
#, no-c-format
msgid "A Sample Nameserver Lookup"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"~]$ <command>dig example.com NS</command>\n"
"\n"
"; &lt;&lt;&gt;&gt; DiG 9.7.1-P2-RedHat-9.7.1-2.P2.fc13 &lt;&lt;&gt;&gt; example.com NS\n"
";; global options: +cmd\n"
";; Got answer:\n"
";; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: NOERROR, id: 57883\n"
";; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0\n"
"\n"
";; QUESTION SECTION:\n"
";example.com.                   IN      NS\n"
"\n"
";; ANSWER SECTION:\n"
"example.com.            99374   IN      NS      a.iana-servers.net.\n"
"example.com.            99374   IN      NS      b.iana-servers.net.\n"
"\n"
";; Query time: 1 msec\n"
";; SERVER: 10.34.255.7#53(10.34.255.7)\n"
";; WHEN: Wed Aug 18 18:04:06 2010\n"
";; MSG SIZE  rcvd: 77"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Looking Up an IP Address"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"To look up an IP address assigned to a particular domain, use the command in"
" the following form:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid "<command>dig</command> <replaceable>name</replaceable> A"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"In <xref linkend=\"example-bind-dig-a\" />, the <command>dig</command> "
"utility is used to display the IP address of <systemitem "
"class=\"domainname\">example.com</systemitem>."
msgstr ""

#. Tag: title
#, no-c-format
msgid "A Sample IP Address Lookup"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"~]$ <command>dig example.com A</command>\n"
"\n"
"; &lt;&lt;&gt;&gt; DiG 9.7.1-P2-RedHat-9.7.1-2.P2.fc13 &lt;&lt;&gt;&gt; example.com A\n"
";; global options: +cmd\n"
";; Got answer:\n"
";; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: NOERROR, id: 4849\n"
";; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0\n"
"\n"
";; QUESTION SECTION:\n"
";example.com.                   IN      A\n"
"\n"
";; ANSWER SECTION:\n"
"example.com.            155606  IN      A       192.0.32.10\n"
"\n"
";; AUTHORITY SECTION:\n"
"example.com.            99175   IN      NS      a.iana-servers.net.\n"
"example.com.            99175   IN      NS      b.iana-servers.net.\n"
"\n"
";; Query time: 1 msec\n"
";; SERVER: 10.34.255.7#53(10.34.255.7)\n"
";; WHEN: Wed Aug 18 18:07:25 2010\n"
";; MSG SIZE  rcvd: 93"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Looking Up a Hostname"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"To look up a hostname for a particular IP address, use the command in the "
"following form:"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"<command>dig</command> <option>-x</option> "
"<replaceable>address</replaceable>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"In <xref linkend=\"example-bind-dig-x\" />, the <command>dig</command> "
"utility is used to display the hostname assigned to <systemitem "
"class=\"ipaddress\">192.0.32.10</systemitem>."
msgstr ""

#. Tag: title
#, no-c-format
msgid "A Sample Hostname Lookup"
msgstr ""

#. Tag: screen
#, no-c-format
msgid ""
"~]$ <command>dig -x 192.0.32.10</command>\n"
"\n"
"; &lt;&lt;&gt;&gt; DiG 9.7.1-P2-RedHat-9.7.1-2.P2.fc13 &lt;&lt;&gt;&gt; -x 192.0.32.10\n"
";; global options: +cmd\n"
";; Got answer:\n"
";; -&gt;&gt;HEADER&lt;&lt;- opcode: QUERY, status: NOERROR, id: 29683\n"
";; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 5, ADDITIONAL: 6\n"
"\n"
";; QUESTION SECTION:\n"
";10.32.0.192.in-addr.arpa.      IN      PTR\n"
"\n"
";; ANSWER SECTION:\n"
"10.32.0.192.in-addr.arpa. 21600 IN      PTR     www.example.com.\n"
"\n"
";; AUTHORITY SECTION:\n"
"32.0.192.in-addr.arpa.  21600   IN      NS      b.iana-servers.org.\n"
"32.0.192.in-addr.arpa.  21600   IN      NS      c.iana-servers.net.\n"
"32.0.192.in-addr.arpa.  21600   IN      NS      d.iana-servers.net.\n"
"32.0.192.in-addr.arpa.  21600   IN      NS      ns.icann.org.\n"
"32.0.192.in-addr.arpa.  21600   IN      NS      a.iana-servers.net.\n"
"\n"
";; ADDITIONAL SECTION:\n"
"a.iana-servers.net.     13688   IN      A       192.0.34.43\n"
"b.iana-servers.org.     5844    IN      A       193.0.0.236\n"
"b.iana-servers.org.     5844    IN      AAAA    2001:610:240:2::c100:ec\n"
"c.iana-servers.net.     12173   IN      A       139.91.1.10\n"
"c.iana-servers.net.     12173   IN      AAAA    2001:648:2c30::1:10\n"
"ns.icann.org.           12884   IN      A       192.0.34.126\n"
"\n"
";; Query time: 156 msec\n"
";; SERVER: 10.34.255.7#53(10.34.255.7)\n"
";; WHEN: Wed Aug 18 18:25:15 2010\n"
";; MSG SIZE  rcvd: 310"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Advanced Features of BIND"
msgstr "BIND: caratteristiche avanzate"

#. Tag: para
#, no-c-format
msgid ""
"Most BIND implementations only use the <systemitem "
"class=\"service\">named</systemitem> service to provide name resolution "
"services or to act as an authority for a particular domain. However, BIND "
"version 9 has a number of advanced features that allow for a more secure and"
" efficient DNS service."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Important: Make Sure the Feature is Supported"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Before attempting to use advanced features like DNSSEC, TSIG, or IXFR, make "
"sure that the particular feature is supported by all nameservers in the "
"network environment, especially when you use older versions of BIND or non-"
"BIND servers."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"All of the features mentioned are discussed in greater detail in the "
"<citetitle>BIND 9 Administrator Reference Manual</citetitle> referenced in "
"<xref linkend=\"s2-bind-installed-docs\" />."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Multiple Views"
msgstr "Visualizzazioni multiple"

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>features</secondary> <tertiary>multiple "
"views</tertiary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Optionally, different information can be presented to a client depending on "
"the network a request originates from. This is primarily used to deny "
"sensitive DNS entries from clients outside of the local network, while "
"allowing queries from clients inside the local network."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"To configure multiple views, add the <command>view</command> statement to "
"the <filename>/etc/named.conf</filename> configuration file. Use the <option"
">match-clients</option> option to match IP addresses or entire networks and "
"give them special options and zone data."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Incremental Zone Transfers (IXFR)"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>features</secondary> "
"<tertiary>Incremental Zone Transfer (IXFR)</tertiary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"<firstterm>Incremental Zone Transfers</firstterm> "
"(<firstterm>IXFR</firstterm>) allow a secondary nameserver to only download "
"the updated portions of a zone modified on a primary nameserver. Compared to"
" the standard transfer process, this makes the notification and update "
"process much more efficient."
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>features</secondary> <tertiary>Automatic "
"Zone Transfer (AXFR)</tertiary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Note that IXFR is only available when using dynamic updating to make changes"
" to master zone records. If manually editing zone files to make changes, "
"<firstterm>Automatic Zone Transfer</firstterm> (<firstterm>AXFR</firstterm>)"
" is used."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Transaction SIGnatures (TSIG)"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>features</secondary> "
"<tertiary>Transaction SIGnature (TSIG)</tertiary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"<firstterm>Transaction SIGnatures</firstterm> (TSIG) ensure that a shared "
"secret key exists on both primary and secondary nameserver before allowing a"
" transfer. This strengthens the standard IP address-based method of transfer"
" authorization, since attackers would not only need to have access to the IP"
" address to transfer the zone, but they would also need to know the secret "
"key."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Since version 9, BIND also supports <firstterm>TKEY</firstterm>, which is "
"another shared secret key method of authorizing zone transfers."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Important: Secure the Transfer"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"When communicating over an insecure network, do not rely on IP address-based"
" authentication only."
msgstr ""

#. Tag: title
#, no-c-format
msgid "DNS Security Extensions (DNSSEC)"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>features</secondary> <tertiary>DNS "
"Security Extensions (DNSSEC)</tertiary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"<firstterm>Domain Name System Security Extensions</firstterm> "
"(<firstterm>DNSSEC</firstterm>) provide origin authentication of DNS data, "
"authenticated denial of existence, and data integrity. When a particular "
"domain is marked as secure, the <literal>SERFVAIL</literal> response is "
"returned for each resource record that fails the validation."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Note that to debug a DNSSEC-signed domain or a DNSSEC-aware resolver, you "
"can use the <command>dig</command> utility as described in <xref "
"linkend=\"s1-bind-dig\" />. Useful options are <option>+dnssec</option> "
"(requests DNSSEC-related resource records by setting the DNSSEC OK bit), "
"<option>+cd</option> (tells recursive nameserver not to validate the "
"response), and <option>+bufsize=512</option> (changes the packet size to "
"512B to get through some firewalls)."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Internet Protocol version 6 (IPv6)"
msgstr ""

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>features</secondary> <tertiary>Internet "
"Protocol version 6 (IPv6)</tertiary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"<firstterm>Internet Protocol version 6</firstterm> "
"(<firstterm>IPv6</firstterm>) is supported through the use of "
"<option>AAAA</option> resource records, and the <option>listen-"
"on-v6</option> directive as described in <xref linkend=\"table-bind-"
"namedconf-common-options\" />."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Common Mistakes to Avoid"
msgstr "Errori comuni da evitare"

#. Tag: indexterm
#, no-c-format
msgid "<primary>BIND</primary> <secondary>common mistakes</secondary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The following is a list of advices how to avoid common mistakes users make "
"when configuring a nameserver:"
msgstr ""

#. Tag: term
#, no-c-format
msgid "Use semicolons and curly brackets correctly"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"An omitted semicolon or unmatched curly bracket in the "
"<filename>/etc/named.conf</filename> file can prevent the <systemitem "
"class=\"service\">named</systemitem> service from starting."
msgstr ""

#. Tag: term
#, no-c-format
msgid "Use period (that is, the <literal>.</literal> character) correctly"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"In zone files, a period at the end of a domain name denotes a fully "
"qualified domain name. If omitted, the <systemitem "
"class=\"service\">named</systemitem> service will append the name of the "
"zone or the value of <option>$ORIGIN</option> to complete it."
msgstr ""

#. Tag: term
#, no-c-format
msgid "Increment the serial number when editing a zone file"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"If the serial number is not incremented, the primary nameserver will have "
"the correct, new information, but the secondary nameservers will never be "
"notified of the change, and will not attempt to refresh their data of that "
"zone."
msgstr ""

#. Tag: term
#, no-c-format
msgid "Configure the firewall"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"If a firewall is blocking connections from the <systemitem "
"class=\"service\">named</systemitem> service to other nameservers, the "
"recommended best practice is to change the firewall settings whenever "
"possible."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Warning: Avoid Using Fixed UDP Source Ports"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"According to the recent research in DNS security, using a fixed UDP source "
"port for DNS queries is a potential security vulnerability that could allow "
"an attacker to conduct cache-poisoning attacks more easily. To prevent this,"
" configure your firewall to allow queries from a random UDP source port."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Additional Resources"
msgstr "Risorse aggiuntive"

#. Tag: para
#, no-c-format
msgid ""
"The following sources of information provide additional resources regarding "
"BIND."
msgstr ""
"Le seguenti fonti potranno fornirvi ulteriori informazioni relative all'uso "
"di BIND."

#. Tag: title
#, no-c-format
msgid "Installed Documentation"
msgstr "Documentazione installata"

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>additional resources</secondary> "
"<tertiary>installed documentation</tertiary>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"BIND features a full range of installed documentation covering many "
"different topics, each placed in its own subject directory. For each item "
"below, replace <replaceable>version</replaceable> with the version of the "
"<package>bind</package> package installed on the system:"
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<filename "
"class=\"directory\">/usr/share/doc/bind-<replaceable>version</replaceable>/</filename>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The main directory containing the most recent documentation."
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<filename "
"class=\"directory\">/usr/share/doc/bind-<replaceable>version</replaceable>/arm/</filename>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The directory containing the <citetitle>BIND 9 Administrator Reference "
"Manual</citetitle> in HTML and SGML formats, which details BIND resource "
"requirements, how to configure different types of nameservers, how to "
"perform load balancing, and other advanced topics. For most new users of "
"BIND, this is the best place to start."
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<filename "
"class=\"directory\">/usr/share/doc/bind-<replaceable>version</replaceable>/draft/</filename>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The directory containing assorted technical documents that review issues "
"related to the DNS service, and propose some methods to address them."
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<filename "
"class=\"directory\">/usr/share/doc/bind-<replaceable>version</replaceable>/misc/</filename>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The directory designed to address specific advanced issues. Users of BIND "
"version 8 should consult the <filename>migration</filename> document for "
"specific changes they must make when moving to BIND 9. The "
"<filename>options</filename> file lists all of the options implemented in "
"BIND 9 that are used in <filename>/etc/named.conf</filename>."
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<filename "
"class=\"directory\">/usr/share/doc/bind-<replaceable>version</replaceable>/rfc/</filename>"
msgstr ""

#. Tag: para
#, no-c-format
msgid "The directory providing every RFC document related to BIND."
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"There is also a number of man pages for the various applications and "
"configuration files involved with BIND:"
msgstr ""

#. Tag: term
#, no-c-format
msgid "<command>man rndc</command>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The manual page for <command>rndc</command> containing the full "
"documentation on its usage."
msgstr ""

#. Tag: term
#, no-c-format
msgid "<command>man named</command>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The manual page for <systemitem class=\"service\">named</systemitem> "
"containing the documentation on assorted arguments that can be used to "
"control the BIND nameserver daemon."
msgstr ""

#. Tag: term
#, no-c-format
msgid "<command>man lwresd</command>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The manual page for <systemitem class=\"service\">lwresd</systemitem> "
"containing the full documentation on the lightweight resolver daemon and its"
" usage."
msgstr ""

#. Tag: term
#, no-c-format
msgid "<command>man named.conf</command>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The manual page with a comprehensive list of options available within the "
"<systemitem class=\"service\">named</systemitem> configuration file."
msgstr ""

#. Tag: term
#, no-c-format
msgid "<command>man rndc.conf</command>"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The manual page with a comprehensive list of options available within the "
"<command>rndc</command> configuration file."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Useful Websites"
msgstr "Siti Web utili"

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>additional resources</secondary> "
"<tertiary>useful websites</tertiary>"
msgstr ""

#. Tag: term
#, no-c-format
msgid "<ulink url=\"http://www.isc.org/software/bind\" />"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"The home page of the BIND project containing information about current "
"releases as well as a PDF version of the <citetitle>BIND 9 Administrator "
"Reference Manual</citetitle>."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Related Books"
msgstr "Libri correlati"

#. Tag: indexterm
#, no-c-format
msgid ""
"<primary>BIND</primary> <secondary>additional resources</secondary> "
"<tertiary>related books</tertiary>"
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<citetitle>DNS and BIND</citetitle> by Paul Albitz and Cricket Liu; O'Reilly"
" &amp; Associates"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"A popular reference that explains both common and esoteric BIND "
"configuration options, and provides strategies for securing a DNS server."
msgstr ""

#. Tag: term
#, no-c-format
msgid ""
"<citetitle>The Concise Guide to DNS and BIND</citetitle> by Nicolai "
"Langfeldt; Que"
msgstr ""

#. Tag: para
#, no-c-format
msgid ""
"Looks at the connection between multiple network services and BIND, with an "
"emphasis on task-oriented, technical topics."
msgstr ""