Quite correct (sorry for the top post). I'm surprised, but glad to have learned something. The only difference in the cases I do are that they're MS DNS and the zones I normally use that trick for are forwarded.
----- Original Message ----- From: Barry Margolin [mailto:bar...@alum.mit.edu] Sent: Tuesday, June 04, 2013 01:37 AM To: comp-protocols-dns-b...@isc.org <comp-protocols-dns-b...@isc.org> Subject: Re: any requests In article <mailman.424.1370323734.20661.bind-us...@lists.isc.org>, "Novosielski, Ryan" <novos...@umdnj.edu> wrote: > If it were not already in the cache, I would not need to refresh the cache. > Are you absolutely certain? If so, it is possible that this is a difference > between BIND and AD DNS (I'm generally trying to refresh AD DNS caches), but > I'm nearly certain I've used this to update a cached entry on a BIND-hosted > domain. Try the following test: Pick a name that has both A and MX records, but isn't currently in cache. dig <name> a @server dig <name> any @server I have no idea what MS DNS does, but I'm pretty certain that if you direct this to the BIND server the second query will only return the A record, not the MX record. -- Barry Margolin Arlington, MA _______________________________________________ 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 _______________________________________________ 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
