Re: Reverse DNS using Microsoft DNS

Mitchell B. Wagers ( (no email) )
Tue, 17 Mar 1998 11:02:52 -0800

If you don't have it create the PTR file when you FIRST make the A
record, it won't happen, you will have to do it manually. If you delete
an A record, it will not automatically delete the PTR record. You do have
the ZONES for the Reverse DNS, correct? You will also need whoever
handles your SWIP registration to point to your servers, which should be
a one-to-one, not a trickle-down syndrome most providers use, see

-InterNIC/ARIN designates DNS to IP's

-Your upstream's upstream carries the Reverse Authority, pointed to your

-Your upstream points Reverse Authotiry to you.

That is a trickle-down approach, very inconvenient and unreliable. I have
heard that "you can't register just one class C for reverse DNS." That is
incorrect, you can and it should be done, unless you carry more than a
class C all your own. They should be registered in the largest blocks

Sorry if I just confused anyone, I can write a longer explanation if need

At 01:44 PM 3/17/98 -0500, you wrote:


<excerpt><smaller>So far, I have figured out Microsoft DNS, mostly. When
it comes to the reverse DNS look up though for A records I am hesitant to
add them. Currently I only have 2 A records that do not have an
associated PTR record in the file. In the properties of
these A records, it says to update the associated PTR file. Should I go
ahead and add these PTR files so reverse DNS can take place?


<smaller>Beverly L. Wise

Systems Operator

Falls City Net Services