If you're making changes to zone files (remember to increment your serial number in the SOA record!) then you'll need to use rndc reload, but on a server with a lot of zones or several large zones, you can minimize the impact on its responsiveness to queries by reloading only the zones that you have updated using rndc reload For assistance with problems and questions for which you have not been able to find an answer in our Knowledge Base, we recommend searching our community mailing list archives and/or posting your question there (you will need to register there first for your posts to be accepted).The slave server will continue to serve up old, stale DNS records, completely ignoring the fact that new data is available on disk after being notified by the master. I would assume that it would always use the most recent data available.At my wit's end, I am considering setting up a crontab to restart the BIND slaves on an hourly basis, just to avoid serving up stale data. odd, the expected behavior is that new records are immediately served from the slaves once they finish processing the zone transfer. You are updating the serial on the zone for every update right?When the serial is incremented on the master zone file, it takes longer than expect for the zone to update on the slave. With a ttl of 5 secs, it takes serveral minutes for the slave to update. Here's my configuration for the master test server: local $TTL 5 @ IN SOA sid. ( 2007010416 ; Serial 5 ; Refresh [1m] 5 ; Retry [10m] 5 ; Expire [1d] 5 ) ; Negative Cache TTL [1h] ; @ IN NS sid. sid IN A 192.168.0.3 etch IN A 192.168.0.3 pop IN CNAME sid www IN CNAME sid mail IN CNAME sid @ IN SOA sid. ( 2007010401 ; Serial 3600 ; Refresh [1h] 600 ; Retry [10m] 86400 ; Expire [1d] 600 ) ; Negative Cache TTL [1h] ; @ IN NS sid. In your case, I don't see the slave server's hostname being listed as an NS record in the zone file.Welcome to Linux Questions.org, a friendly and active Linux Community. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration.
If you make a change to your that you want named to start using then use rndc reconfig will also load any new zones that you've added (and remove any that you no longer have defined), but it won't detect any changes that you've made to zones that are already loaded.
Note that registered members see fewer ads, and Content Link is completely disabled once you log in. Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
Please visit this page to clear all LQ-related cookies.
Click Here to receive this Complete Guide absolutely free.
I have a master - slave setup of Bind9 on a debian installation, which runs as exspected. Everytime a zonefile is changed, it is required to run "rndc reload" command or else bind will never pickup the changes in the zonefile. Running "rndc reload" will also force an update to the slave servers.