Bind slave not updating

// // // // Provided by Red Hat bind package to configure the ISC BIND named(8) DNS // server as a caching only nameserver (as a localhost DNS resolver only).

// // See /usr/share/doc/bind*/sample/ for example named configuration files.

The problem lies with serial which is not updated to current date and number of changes per each day after a zone is changed......

I realized this when I added several A records to a zone and then checked the dns_soa table, the serial was still 2009012401 instead of 2009012405 or 2009012415I have some slave DNS server running BIND that do zone transfers from my ispconfig server.

If you found this Article useful then Like it, Share it, Subscribe our Site for more Linux Tutorials OR If you have any thing to say then feel free to Comment on Comment Box below.

Balamukunda Sahu This is Balamukunda Sahu the Founder and Editor of ELinux Book.

I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing.

Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

IN A 192.168.1.100 ; mail exchanger record (MX record) IN MX 5 ns1.slaves You could convert one of the slave DNS servers to be the new master while updating the remaining slave to reflect the new master.Your question lacks detail chaining The way bind works when you have notify settings relied on based on the NS records in the zone when a zone is updated on the master a notification is sent to NS record servers.[[email protected] ~]# nslookup 192.168.1.101 Server: 127.0.0.1 Address: 127.0.0.1#53 101.1.168.192.name = ns2.So everything looks good and Slave/Secondary DNS Server is working fine as shown on the testing output’s above.Keep visit to our site and I will bring all latest Linux Tutorials, Updates, How To's and News for you.For the most part, if you make sure that your zone’s SOA record contains the domain name of the primary master name server in the MNAME field, you won’t need to worry about update forwarding.Here below I have mentioned my file and Highlighted all required changes I did in Blue Color.// options ; logging ; zone "." IN ; include "/etc/named.rfc1912.zones"; include "/etc/key"; ### Internal DNS Slave Zones ### So we have successfully configured the BIND DNS Service, Now it’s time for testing., We have tools like dig, nslookup to check the DNS service working status. dig [[email protected] ~]# nslookup Server: 127.0.0.1 Address: 127.0.0.1#53 Name: Address: 192.168.1.100 [[email protected] ~]# nslookup ns1.Server: 127.0.0.1 Address: 127.0.0.1#53 Name: ns1.Address: 192.168.1.100 [[email protected] ~]# nslookup ns2.Server: 127.0.0.1 Address: 127.0.0.1#53 Name: ns2.Address: 192.168.1.101 [[email protected] ~]# nslookup 192.168.1.100 Server: 127.0.0.1 Address: 127.0.0.1#53 100.1.168.192.name = ns1.I have some slave DNS server running BIND that do zone transfers from my ispconfig server.The problem occurred when the changes were that were made to zones on ispconfig were not transfered to BIND servers.

454

Leave a Reply