ignoring incorrect nameservers in authority section

Matus UHLAR - fantomas uhlar at fantomas.sk
Thu Jan 6 16:19:00 UTC 2011

> Quoting from Chris Buxton's mail on Thu, Dec 23, 2010:
> > > Is there any option to add workarounds for specific domains /
> > > nameservers like the ones listed above?
> > 
> > Possibly. You can try setting up conditional forwarding for the problem domain, setting the authoritative name servers as the 'forwarders' list. This may not work, since the authoritative servers may not respond well to recursive queries, but it's worth a shot. For example:
> > 
> > zone "e-nxt.com." {
> > 	type forward;
> > 	forwarders {
> >;
> >;
> > 	};
> > };

On 24.12.10 13:21, Sunil Shetye wrote:
> That did work. However, this means that I would have to watch the
> zone to see
> - if the IP addresses of their nameservers change
> - if their nameservers change

you will always have to do this if you want to prevent problems if others
misconfigure their servers.

> Here, I can see that the nameserver is giving the right replies to all
> queries except the NS queries. My guess is that they must have
> transferred the zone from one nameserver to another
> (ns[56].zenexpress.com. to ns[12].webpresenceworld.com. for
> e-nxt.com) and updated the domain registration, but did not bother to
> change the NS record on the new nameservers.
> I was hoping that either bind should catch such cases automatically or
> allow some workaround which need not be monitored later.

Just live with it. If a domain maintainer puts incorrect data to the zone,
it will behave incorrectly.

Matus UHLAR - fantomas, uhlar at 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.
My mind is like a steel trap - rusty and illegal in 37 states. 

More information about the bind-users mailing list