Advanced DNS and BIND9 Configuration Guide
Learn about configuring master, slave, and caching name servers using BIND9. This tutorial covers zone configuration, root servers, localhost setup, and reverse mapping for example.com.
Advanced DNS and BIND9 Configuration Guide
E N D
Presentation Transcript
DNS - BIND9 Přednášející Vaše jméno
Master and caching name server options { directory "/var/named"; allow-transfer {“none”;}; }; zone "." { type hint; file “root.servers"; }; zone "example.com" in{ type master; file “master/master.example.com"; allow-transfer {192.168.23.1;192.168.23.2;); }; zone "0.168.192.IN-ADDR.ARPA" in{ type master; file “192.168.0.rev"; }; zone "localhost" in{ type master; file “master.localhost"; allow-update{none;}; }; zone "0.0.127.in-addr.arpa" in{ type master; file “localhost.rev"; allow-update{none;}; };
Slave and caching name server options { directory "/var/named"; allow-notify {192.168.0.1}; allow-transfer {“none”;}; }; zone "." { type hint; file “root.servers"; }; zone "example.com" in{ type slave; file "slave/slave.example.com"; masters {192.168.0.1;}; }; zone "0.168.192.IN-ADDR.ARPA" in{ type slave; file "sec.192.168.0.rev "; masters {192.168.0.1;}; }; zone "localhost" in{ type master; file “pri.localhost"; allow-update{none;}; }; zone "0.0.127.in-addr.arpa" in{ type master; file “localhost.rev"; allow-update{none;}; };
Caching name server options { directory "/var/named"; allow-notify {192.168.0.1}; allow-query {192.168.3.0/24; }; }; zone "." { type hint; file “root.servers"; }; zone "localhost" in{ type master; file “master.localhost"; allow-update{none;}; }; zone "0.0.127.in-addr.arpa" in{ type master; file “localhost.rev"; allow-update{none;}; };
Root servers . 3600000 IN NS A.ROOT-SERVERS.NET. A.ROOT-SERVERS.NET. 3600000 A 198.41.0.4 ; . 3600000 NS B.ROOT-SERVERS.NET. B.ROOT-SERVERS.NET. 3600000 A 192.228.79.201 ; . 3600000 NS L.ROOT-SERVERS.NET. L.ROOT-SERVERS.NET. 3600000 A 198.32.64.12 ; . 3600000 NS M.ROOT-SERVERS.NET. M.ROOT-SERVERS.NET. 3600000 A 202.12.27.33 ; End of File
localhost $TTL 86400 ; 24 hours could have been written as 24h $ORIGIN localhost. ; line below = localhost 1D IN SOA localhost root.localhost @ 1D IN SOA @ root ( 2002022401 ; serial 3H ; refresh 15 ; retry 1w ; expire 3h ; minimum ) @ 1D IN NS @ 1DIN A 127.0.0.1
Localhost reverse $TTL 86400 ; ; could use $ORIGIN 0.0.127.IN-ADDR.ARPA. @ IN SOA localhost. root.localhost. ( 1997022700 ; Serial 3h ; Refresh 15 ; Retry 1w ; Expire 3h ) ; Minimum IN NS localhost. 1IN PTR localhost.
Example.com $TTL 86400 ; 24 hours could have been written as 24h or 1d $ORIGIN example.com. @ 1DIN SOA ns1.example.com. hostmaster.example.com. ( 2002022401 ; serial 3H ; refresh 15 ; retry 1w ; expire 3h ; minimum ) IN NS ns1.example.com. ; in the domain IN NS ns2.smokeyjoe.com. ; external to domain IN MX 10 mail.another.com. ; external mail provider ; server host definitions ns1 IN A 192.168.0.1 ;name server definition www IN A 192.168.0.2 ;web server definition ftp IN CNAME www.example.com. ;ftp server definition bill IN A 192.168.0.3 fred IN A 192.168.0.4
Example.com reverse map • $TTL 86400 ; 24 hours could have been written as 24h or 1d • $ORIGIN 0.168.192.IN-ADDR.ARPA. • @ 1D IN SOA ns1.example.com. mymail.example.com. ( • 2002022401 ; serial • 3H ; refresh • 15 ; retry • 1w ; expire • 3h ; minimum ) • ; server host definitions • INPTR ns1.example.com. • 2 IN PTR www.example.com. ; non server domain hosts • IN PTR bill.example.com. • IN PTR fred.example.com.