[lug] Reverse domain registry question

[Nate Duehr]

On Thu, Feb 17, 2000 at 04:00:31PM -0700, Chip Atkinson wrote:

Basically there are about three ways to do this, and the ISP needs to do
all of them.  If you're ready to start doing the reverses on your DNS
server, they need to delegate those IP's down to you.

Easiest way to do that for them is to put NS records pointing to your
nameserver's IP address in place of PTR records in the in-addr.arpa zone
for your IP addresses.  This will cause these lookups to be referred to
your nameserver.  

Other methods include actually registering that IP range as being *yours*
and not theirs with ARIN and the powers that be, at which point reverse
lookups would come directly to your nameserver and not go to theirs first.
For a really big group of IP's, this is a must as it speeds things up and
is a better use of DNS server resources, but for a small group of IP's, 
it's easier just to delegate via recursion.

One other thing, someone said you were on dialup?  That didn't make any
sense to me as you are serving from that machine.  I'll assume you have
static IP's, or otherwise there's a whole other mess that needs to be
dealt with.  :)

If you have a /28 or /29 network, getting USWest to type in the delegations 
isn't too bad.  Otherwise, if you have a lot of IP's, it's time for them to
break out the macro preprocessor to attack the zone files!  :) 

BTW, expect them to get this wrong at least once.  Their DNS guys were
very green a couple months ago, and a friend of mine had to e-mail them
a zone file to use to get his DNS set up correctly.  That's just sad.


> I'm setting up a few domains and am trying to get reverse lookups working.
> I have the static IPs and both forward and reverse lookups work on the 
> local box with the name server, but only forward lookups work in the
> outside world.  How do I get the inaddr.arpa domain information to the
> outside world?  Is this something that my ISP needs to do?  If so, how is
> it done?  I have US Wurst as an ISP so I need to understand it so I can
> explain it to them :-)

-- 
Nate Duehr <nate at natetech.com>

GPG Key fingerprint = DCAF 2B9D CC9B 96FA 7A6D AAF4 2D61 77C5 7ECE C1D2
Public Key available upon request, or at wwwkeys.pgp.net and others.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20000218/2251330b/attachment.pgp>