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

[Mark.Andrews at nominum.com]

> 
> <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!

	Your ISP has set up the CAMES to point into
	32-28.178.175.216.in-addr.arpa.  Create *this* zone on your
	servers and populate it.

	32-28.178.175.216.in-addr.arpa is currently delegated to
	fsn2.frontstreetnetworks.com and fsn1.frontstreetnetworks.net.

@	SOA 	...
@	NS	fsn2.frontstreetnetworks.com.
@	NS	fsn1.frontstreetnetworks.net.
;32	PTR	<network name>
33	PTR	...
34	PTR	...
46	PTR	...
;47	PTR	<network broadcast>

	I would also make your servers slaves for 178.175.216.in-addr.arpa
	so that reverse lookups will work disconnected from the net.

	Mark
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com