On 20.11.09 08:57, Gil Vidals wrote: > I have a master and slave running bind 9.4.3, and there is a problem with > the outside world resolving new domains that I add to my name servers. Here > is the sequence: > > 1) add new domain > 2) dig shows matching SOA and correct zone info. > 3) wait two days > 4) check a random name server such as openDNS and results are wrong - only > about half of their name servers have the correct info. > 5) restart named on my master and slave > 6) re-check openDNS and voila! everything is good. > > Is this a caching issue that requires restarting named daily? What changes > in the config files can I make to solve this issue?
I don't think that's a caching problem. From my experience this is most often caused by mismatch between NS records in your zones and NS delegations from parent zones. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. There's a long-standing bug relating to the x86 architecture that allows you to install Windows. -- Matthew D. Fuller _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
