Create Reverse Zone

Re: Create Reverse Zone

From:

Date:

Time:

At 11:21 AM +0100 7/11/00, Simon Forster wrote:
>Short version of my question:
>
>To manage my own DNS records I've been asked by my ISP to create a reverse
>zone of "176-28.39.219.213.in-addr.arpa". I do not know how to set-up a
>reverse zone. Help would be appreciated!
>
>In slightly more detail:
>
>I've just moved a couple of boxes to a co-lo facility and I would like to
>have a secondary DNS server running from one of the co-lo boxes. This
>secondary would pull all its data from my primary (which sits on a slower
>line on a completely different network but is in my office so is easier to
>admin).
>
>I'd like to be (ir)responsible for ptr records for my co-lo boxes. Partly
>for operational reasons (if I want things changing, I want it doing now),
>partly because I like to learn :-)
>
>I understand the broad principles behind DNS but am a bit flaky on the
>details.
>
>Specific questions:
>
>- Can I create a reverse zone in Quick DNS Pro?

Absolutely.

>- Even though my co-lo box has no primary domains? (I'd like to manage
>everything from my office server.)

No problem. Presumably, you'd host this on both servers anyway, just
like your domain zones.

>- How?

Two methods, automatic and manual. Do this on the primary server,
then configure the secondary to host the zone (again, just like with
your domain zones).

Automatic:
o Open QuickDNS Pro Admin.
o From the File menu, select New....
o In the resulting dialog, select Use Domain Assistant and hit OK.
o In panel 2 of the assistant, select Reverse Domain.
o In panel 3, select Create a classless reverse domain.
o In panel 4, enter 213.219.39.178.
o In panel 5, change the entry to 176-28.39.219.213.in-addr.arpa.
(including the dot on the end).
o In panel 6, click on Go ahead.

The assistant will search your files for A records using IP addresses
that start with 213.219.39, and will put appropriate records in your
reverse zone. (The assistant confuses the terms "domain" and "zone".)

When it's done, save the file.

Manual:
o Open QuickDNS Pro Admin.
o From the File menu, select New....
o In the resulting dialog, just hit OK.
o A new file appears. From the Domain menu, select Domain Information.
o In the Name field, enter 176-28.39.219.213.in-addr.arpa.
o In the Primary and Hostmaster fields, enter the same values you've
been using in your other files.
o Click OK to close the dialog.
o Create NS records for the new zone, using the usual names for your servers.

(and now, the potentially tedious part:)
o For each IP address you use in the 213.219.39.176/28 block, create
a PTR record. In the Name field, enter just the last octet of the IP
address - the program will fill in the rest when you leave the field.
In the Parameter 1 field, enter a name to use as the default for that
IP address - it should be a name that has a corresponding A record in
one of your domain zone files.

>- Or do I have a basic misunderstanding here?

No, but your co-lo provider does. His delegation to your server won't
do much good, since the parent zone isn't delegated to him. He needs
to fix this; the whole 219.213.in-addr.arpa. zone isn't delegated
from ns.ripe.net.

>My DNS records are probably all over the place at the moment as various
>changes filter through. However, feel free to look at ldml.com which I'm
>trying to get served by:
>primary: ns.ldml.com (62.6.164.2)
>secondary: oxford.ldml.com (213.219.39.178).
>
>For the time being I've removed the restrictions I had in place for zone
>transfers from ns.ldml.com.
>
>oxford.ldml.com is not picking up the secondary data at this time. Why I'm
>not too sure.

oxford.ldml.com isn't responding at all. Maybe that's the problem...?
Or are you working on it right now?
____________________________________________________________________
Chris Buxton cbuxton@menandmice.com
Men & Mice http://www.menandmice.com
Makers of: QuickDNS Pro

Sales:
888/4-DPOINT

Support:
858/452-3696