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 {
> 202.71.131.12;
> 202.71.131.13;
> };
> };
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
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.
--
Sunil Shetye.
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
