Search Again:

Re: in-addr.arpa files....

From: Chris Buxton
Date: Saturday, March 8, 1997
Time: 1:27:00 am

>Is it me or does it not seem like in this day and age that we should not
>have to maintain a separate in-addr.arpa file for each domain? Granted
>that there is a bit more flexibility with having the file, but it would
>seem to me that if you already are using a proprietary domain file
>format then why not just use the same file and index on the IP # for the
>in-addr.arpa entries? All of the information is already there.

The answer is that you shouldn't necessarily have a reverse file for every
domain file. In fact, with today's proliferation of domain names, most
likely such a setup would be incorrect.

You should have a reverse file for every network. For instance, if you've
got one class C network and 15 domain names, you should have 15 domain zone
files and one reverse file.

For a more complex example, suppose you've got a RAIC of 6 servers, but for
greater reliability, you've spread them out across 6 offices, each with a
separate class C network. Further suppose that each one is responsible for
15 websites, each with a different domain name, so that no two sites are in
the same second-level domain. Now, since this is a RAIC, suppose that each
webserver is responsible for the same 15 websites, so that altogether, they
constitute 15 websites. You should have 15 domain zone files and 6 reverse
zone files. None of the domain zones contain all the information of any of
the reverse zones, and vice versa.

The PTR records must be kept in a location that is determinable by the IP
address, and all other records need to be kept in a location that is
determinable by the domain name.

Sorry if this sounds like a rant...


-------------------------------
Chris Buxton
Independent Consultant
Specializing in Web Development



Messages In This Thread:



Return to Digital Point Solutions' Home Page