[112838] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: NANOG Digest, Vol 14, Issue 44

daemon@ATHENA.MIT.EDU (Mike Bailey)
Sat Mar 21 08:16:48 2009

Date: Sat, 21 Mar 2009 07:16:33 -0500
From: Mike Bailey <mike@steadfast.net>
To: nanog@nanog.org
In-Reply-To: <mailman.1.1237636802.7967.nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org

nanog-request@nanog.org wrote:
> hi,
>
>  I want to ask some folks out there that maintain reverse DNS queries
> of their respective IP blocks. I want to know if there is a need for
> me to contact my upstream provider. I am in charge of 2 /24's under
> LACNIC. I've already registered my DNS servers on LACNIC. but for some
> weird reason it's not owning reverse resolves. any tips would be
> gladly appreciated.
>
>
> thanks,
> b
>
>   

You can use the dig utility that usually comes with bind to trace the NS 
records for the ip block down, just run:

# dig 255.254.253.252.in-addr.arpa @a.root-servers.net NS +trace

That will tell you what nameserver is directing you where. You can also 
use this web-based utility to query the root nameservers to figure out 
where your queries are being directed to: http://www.squish.net/dnscheck 
. Just make sure you are entering your ip in the reverse-dns, 
*.in-addr.arpa format, and not the actual ip address.

> > Slighty related...
> >
> > Can people please post their recommended reverse dns naming 
> conventions for a small ISP with growth and scalability in mind.
> > I already have one drawn up, but I would like to contrast and compare :D
> >
> > Thanks
ip4.1-2-3.static.ourdomain.net


home help back first fref pref prev next nref lref last post