Difference between revisions of "Private Nameservers"
(7 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
+ | Tested on CentOS 6.7 | ||
+ | |||
Install bind | Install bind | ||
yum install bind bind-utils nano | yum install bind bind-utils nano | ||
Line 24: | Line 26: | ||
managed-keys-directory "/var/named/dynamic"; | managed-keys-directory "/var/named/dynamic"; | ||
}; | }; | ||
− | + | ||
− | logging { | + | logging { |
channel default_debug { | channel default_debug { | ||
file "data/named.run"; | file "data/named.run"; | ||
severity dynamic; | severity dynamic; | ||
}; | }; | ||
− | }; | + | }; |
− | + | ||
− | zone "." IN { | + | zone "." IN { |
type hint; | type hint; | ||
file "named.ca"; | file "named.ca"; | ||
− | }; | + | }; |
− | + | ||
zone "'''example.com'''" IN { | zone "'''example.com'''" IN { | ||
type master; | type master; | ||
Line 42: | Line 44: | ||
allow-update { none; }; | allow-update { none; }; | ||
}; | }; | ||
+ | |||
+ | include "/etc/named.rfc1912.zones"; | ||
+ | include "/etc/named.root.key"; | ||
− | + | Where '''1.2.3.4''' is the IP of ns2 and '''example.com''' is your domain. | |
− | |||
− | + | If ns1 and ns2 are the same server, then you can put the IP of BIND server as '''1.2.3.4'''. | |
+ | |||
+ | Create zone file: | ||
+ | nano /var/named/example.com.zone | ||
+ | |||
+ | Edit the file: | ||
+ | |||
+ | $TTL 86400 | ||
+ | @ IN SOA ns1.example.com. root.example.com. ( | ||
+ | 2013042201 ;Serial | ||
+ | 3600 ;Refresh | ||
+ | 1800 ;Retry | ||
+ | 604800 ;Expire | ||
+ | 86400 ;Minimum TTL | ||
+ | ) | ||
+ | |||
+ | IN NS ns1.example.com. | ||
+ | IN NS ns2.example.com. | ||
+ | |||
+ | ns1 IN A 1.1.2.2 | ||
+ | ns2 IN A 1.2.3.4 | ||
+ | |||
+ | |||
+ | @ IN A 5.5.6.6 | ||
+ | www IN A 5.6.7.8 | ||
+ | |||
+ | Apply changes: | ||
+ | service named restart | ||
+ | |||
+ | [[Category:Linux]] |
Latest revision as of 17:03, 19 May 2016
Tested on CentOS 6.7
Install bind
yum install bind bind-utils nano
Open BIND conf file:
nano /etc/named.conf
Edit the file so it looks like below:
options { #listen-on port 53 { 127.0.0.1; }; listen-on-v6 port 53 { ::1; }; directory "/var/named"; dump-file "/var/named/data/cache_dump.db"; statistics-file "/var/named/data/named_stats.txt"; memstatistics-file "/var/named/data/named_mem_stats.txt"; allow-query { any; }; allow-transfer { localhost; 1.2.3.4; }; recursion no; dnssec-enable yes; dnssec-validation yes; dnssec-lookaside auto; /* Path to ISC DLV key */ bindkeys-file "/etc/named.iscdlv.key"; managed-keys-directory "/var/named/dynamic"; }; logging { channel default_debug { file "data/named.run"; severity dynamic; }; }; zone "." IN { type hint; file "named.ca"; }; zone "example.com" IN { type master; file "example.com.zone"; allow-update { none; }; }; include "/etc/named.rfc1912.zones"; include "/etc/named.root.key";
Where 1.2.3.4 is the IP of ns2 and example.com is your domain.
If ns1 and ns2 are the same server, then you can put the IP of BIND server as 1.2.3.4.
Create zone file:
nano /var/named/example.com.zone
Edit the file:
$TTL 86400 @ IN SOA ns1.example.com. root.example.com. ( 2013042201 ;Serial 3600 ;Refresh 1800 ;Retry 604800 ;Expire 86400 ;Minimum TTL ) IN NS ns1.example.com. IN NS ns2.example.com. ns1 IN A 1.1.2.2 ns2 IN A 1.2.3.4 @ IN A 5.5.6.6 www IN A 5.6.7.8
Apply changes:
service named restart