reverse-lookup-problems was (No forward lookup for one domain )

[Kevin Darcy]

Gerald Waugh wrote:

> <Mark.Andrews at nominum.com> wrote
> gerald at waugh.com wrote >
> > > I have a domain name frontstreetnetworks.net 216.175.178.41
> > > in a subclass 'c' network 216.175.178.32/28
> > > Nameservers:
> > > fsn1.frontstreetnetworks.net.     86400   A       216.175.178.41
> > > fsn2.frontstreetnetworks.com.   86400   A       216.175.178.46
> > > fsn3.frontstreetnetworks.com.   86400   A       216.175.178.45
> > > My reverse lookup does not seem to work,
> > > following is output from 'dig' 216.175.178.41
> > > any ideas?
> >
> > Yes.  Driver error.  The query you should have made is "dig
> > -x 216.175.178.41 ptr".  This returns a partial answer then
> > SERVFAIL.  The servers for 32-28.178.175.216.in-addr.arpa
> > are not set up.
> > Mark
>
> Ok, how do I fix it? I am using Cobalt Networks Servers, my ISP is dsl.net.
> They have made my nameservers authoritive for 216.175.178.32/28 subnet
> by making each of the IPs a CNAME record on their nameservers.
> I don't exactly know how to resolve my problem, is it my nameservers or is
> it my ISPs nameservers?
> Thanks, for any help!

32-28.178.175.216.in-addr.arpa has been delegated to the servers
fsn1.frontstreetnetworks.net and fsn2.frontstreetnetworks.com, but both of
those servers return SERVFAIL for an SOA query of the zone. If those are your
servers, then set up a master zone on one, containing your PTR records, and
set up the other one as a slave. They both appear to be on the same subnet. If
that's true, then for redundancy, you might want to arrange for some other
nameserver(s) on (a) different subnet(s) or network(s) to be (an) additional
slave(s) for the zone. Otherwise a router or some other device in the network
path to those servers is a single point of failure for your entire zone.


- Kevin