Nameservers being down does not result in NXDOMAIN responses. I suspect that some of the auth servers were producing NXDOMAIN incorrectly. Flushing the name won't help in those cases.
In message <001001d01429$1c857f70$55907e50$@iname.com>, "Frank Bulk" writes: > Our ISP operations are running a mixture of 9.7.3 and 9.8.4 on several > Debian servers and we've noticed that rndc flushname doesn't work many > times. > > This weekend we had a local institution whose own authoritative DNS servers > [all of them] were offline for 48+ hours and so there were several > negatively cached entries in our resolvers' caches from customers who were > querying for their institutions website and MX record. After the > institution restored connectivity to their DNS servers this afternoon I > checked all our resolvers and a few returned NXDOMAIN for the www and MX > record. Issuing rndc flushname <domain> and rndc flushname <www.domain> > didn't clear out the NXDOMAIN. I had to use "rndc flush" to resolve the > issue. > > Is this expected behavior? The next time I see what, what troubleshoot > steps should I take diagnose the issue? Dump the DB? > > Frank > > _______________________________________________ > Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe > from this list > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
