|
|
1738.
|
|
|
;
; BIND data file for local loopback interface
;
$TTL 604800
@ IN SOA ns.example.com. root.example.com. (
1 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
;
@ IN NS ns.example.com.
@ IN A 192.168.1.10
ns IN A 192.168.1.10
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
|
1742.
|
|
|
Once you have made a change to the zone file <application>BIND9</application> will need to be restarted for the changes to take affect:
|
|
|
|
|
(no translation yet)
|
|
|
|
|
1760.
|
|
|
zone "example.com" {
[tab]type slave;
file "db.example.com";
masters { 192.168.1.10; };
};
zone "1.168.192.in-addr.arpa" {
[tab]type slave;
file "db.192";
masters { 192.168.1.10; };
};
|
|
|
[tab] represents a tab character.
Please write it exactly the same way, [tab], in your
translation.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
|
1772.
|
|
|
Once a host has been configured to use the new nameserver one of the simplest tests is the <application>ping</application> utility. From a terminal prompt enter:
|
|
|
|
|
(no translation yet)
|
|
|
|
|
1774.
|
|
|
This tests if the nameserver can resolve the name <emphasis>example.com</emphasis> to an IP Address. The command output should resemble:
|
|
|
|
|
(no translation yet)
|
|
|
|
|
1775.
|
|
|
PING example.com (192.168.1.10) 56(84) bytes of data.
64 bytes from ns (192.168.1.10): icmp_seq=1 ttl=64 time=0.800 ms
64 bytes from ns (192.168.1.10): icmp_seq=2 ttl=64 time=0.813 ms
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
|
1800.
|
|
|
<application>BIND9</application> has a wide variety of logging configuration options available. There are two main options. The <emphasis>channel</emphasis> option configures where logs go, and the the <emphasis>category</emphasis> option determines what information to log.
|
|
|
|
|
(no translation yet)
|
|
Translated and reviewed by
Peter Mráz
|
|
|
|
|
1817.
|
|
|
Now restart <application>BIND9</application> for the changes to take affect:
|
|
|
|
|
(no translation yet)
|
|
|
|
|
1826.
|
|
|
IN MX mail.example.com.
mail IN A 192.168.1.13
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
represents a space character.
Enter a space in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
Translated and reviewed by
Peter Mráz
|
|
|
|
|
1844.
|
|
|
tcp 0 0 localhost.localdomain:mysql *:* LISTEN -
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
serverguide/C/databases.xml:70(programlisting)
|
