When you query a random nameserver there is a 50/50 chance (ok, well 100/N - where N is the number of auth servers) that they will hit your secondary which, it sounds like, doesn't know about the domain yet...
Can you retest and dig against all of your auth servers, making sure that they all return correct data?
W On Nov 20, 2009, at 11:57 AM, Gil Vidals wrote:
Hello,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 days4) 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?Gil Vidals, VCP gvid...@vmracks.com vmracks.com - ESX Hosting t. 760.480.4942 f. 760.480.8271 _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
--I had no shoes and wept. Then I met a man who had no feet. So I said, "Hey man, got any shoes you're not using?"
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
