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

[Mark.Andrews at nominum.com]

> 
> <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.ne
> t.
> > > 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 i
> s
> > > it my ISPs nameservers?
> > > Thanks, for any help!
> > > Gerald
> 
> > 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
> 
> Thanks for having a little patience with me and helping me get this DNS set u
> p
> correctly.
> 
> This is my pri.32-28.178.175.216.in-addr.arpa on my master nameserver
> (fsn1.frontstreetnetworks.net)
> Is there somethning wrong with it? I dont have 32, 33, or 47 in the file
> 32 of course is the network.
> 33 is the sDSL gateway

	Add it in e.g. "33 PTR gateway.frontstreetnetworks.net."

	32 and 47 are not important.

> 47 of course is the broadcast address.
> fsnxn.com are not registered domain names, just placeholders for the IP? (may
> be
> questionable practive)

	If there is no machine there doesn't have to be a PTR record.
	I would normally just have a commented out PTR record.

	e.g.
		;34	PTR	unused

> 
> @ IN SOA fsn1.frontstreetnetworks.net. root.fsn1.frontstreetnetworks.net.
> (      200008
>         2510
>         10800
>         3600
>         604800
>         86400 )

	One too many fields, 1 serial and 4 intervals (not 5 intervals).

>  IN NS fsn1.frontstreetnetworks.net.

	Have all the servers listed.

> 41      in      ptr     fsn1.frontstreetnetworks.net.
> 34      in      ptr     fsn34x.com.
> 35      in      ptr     fsn35x.com.
> 36      in      ptr     fsn36x.com.
> 37      in      ptr     fsn37x.com.
> 38      in      ptr     fsn38x.com.
> 39      in      ptr     fsn39x.com.
> 40      in      ptr     frontstreetnetworks.org.
> 42      in      ptr     fsn42x.com.
> 43      in      ptr     fsn43x.com.
> 44      in      ptr     fsn44x.com.
> 45      in      ptr     fsn3.frontstreetnetworks.com.
> 46      in      ptr     fsn2.frontstreetnetworks.com.

	I would have these in numerical order.  For a small network
	its not a problem but when you start dealing with hundreds
	of machines it does.  It's better to start with good practices
	that to try to pick them up later.

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