No servers can be reached

[Kevin Darcy]

Tell them that the NS records in the zone should match the NS records in the
delegation from "net", and _vice_versa_.


- Kevin

Ken Smith wrote:

> Any ideas on how I should explain this to the ISP Earthlink who bought the ISP
> onemain.com who bought out  ISP thegrid.net.
> Ken
>
> Mark_Andrews at isc.org wrote:
>
> > >
> > > When we do a  nslookup -query=mx thegrid.net  ns.pathstar.com using our
> > > nameserver running RH 7.1 & Bind 9.1  we get the following error:
> > > ;; connection timed out; no servers could be reached
> > >
> > > Everything has worked fine till we switched from RH 7.0 & Bind 8.2.3 (We
> > > use this box as a nameserver only)
> > >
> > > If we use someone elses nameserver i.e.  nslookup -query=mx thegrid.net
> > > 204.127.129.1 the correct infomation is returned.
> > > Our webhosting customers resolve correctly in our nameservers
> > > (ns.pathstar.com and ns2.pathstar.com) we  provide webhosting and email
> > > services only. This problem was brought to our attentionlast  week when
> > > we could not forward mail to a  thegrid.net email address.
> > >
> > > Anyone have any ideas.
> >
> >         Yes.  The delegation for thegrid.net is stuffed.  Different sets
> >         of nameservers in the zone compared to the parent (net) zone.
> >
> >         Mark
> > --
> > Mark Andrews, Internet Software Consortium
> > 1 Seymour St., Dundas Valley, NSW 2117, Australia
> > PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at isc.org