|
|
 |  |
Re: Which way is best-ReverseFrom: Men & Mice Support Date: Monday, January 24, 2005
Time: 11:51:36 amThe name of your reverse zone (for a subnet smaller than a class C,
and even occasionally for larger subnets) is arbitrarily defined by
your ISP. Do whatever they say.
In this case, atgi.net has defined your reverse zone name as
panavise.202.210.216.in-addr.arpa. So your PTR record should look
like this:
70.panavise.202.210.216.in-addr.arpa. PTR some.canonical.name.
It currently looks like this:
70.panavise.202.210.216.in-addr.arpa. PTR panavise.com.
So that looks fine (at least on the surface - I can't say whether
that's the correct canonical name [panavise.com.] to use in this
case).
Chris Buxton
Men & Mice - Making DNS Easy
At 11:20 AM -0800 1/24/05, Gary Richter wrote:
>Been following the thread on reverse records recently, and might be
>confused a touch. Just upgraded ns1 and ns2 to OSX QDNS Bind 9.3.0
>with the -4 mod.
>
>In the past (under classic) we had our reverse records set like this
>for an A record of 216.210.202.70
>
>70.panavise.202.210.216.in-addr.arpa. PTR panavise.com
>
>
>dnsstuff.com doing a reverse check returns:
>
>
>
>Looking up at the 2 202.210.216.in-addr.arpa. parent servers:
>ns1.atgi.net [216.174.194.53]
> 70.202.210.216.in-addr.arpa.->70.panavise.202.210.216.in-addr.arpa.
>panavise.com.
>ns2.atgi.net [216.174.194.54]
> 70.202.210.216.in-addr.arpa.->70.panavise.202.210.216.in-addr.arpa.
>panavise.com
>
>
>Asking i.root-servers.net for 70.202.210.216.in-addr.arpa PTR record:
> i.root-servers.net says to go to figwort.arin.net. (zone:
>216.in-addr.arpa.)
>Asking figwort.arin.net. for 70.202.210.216.in-addr.arpa PTR record:
> figwort.arin.net [192.42.93.32] says to go to ns1.atgi.net.
>(zone: 202.210.216.in-addr.arpa.)
>Asking ns1.atgi.net. for 70.202.210.216.in-addr.arpa PTR record:
>Got CNAME referral to ns1.atgi.net. (zone
>70.panavise.202.210.216.in-addr.arpa.) [from 216.174.194.53]
>Asking ns1.atgi.net. for 70.panavise.202.210.216.in-addr.arpa. PTR record:
> ns1.atgi.net [216.174.194.53] says to go to ns1.panavise.com.
>(zone: panavise.202.210.216.in-addr.arpa.)
>Asking ns1.panavise.com. for 70.panavise.202.210.216.in-addr.arpa.
>PTR record: Got NODATA response type 3 [from 216.210.202.66].
>Answer:
>There is no PTR record for 70.panavise.202.210.216.in-addr.arpa.
>(but 70.panavise.202.210.216.in-addr.arpa. is valid).
>--------
>
>It says there is no PTR record but it says
>70.panavise.202.210.216.in-addr.arpa. is valid
>
>My recollection is that atgi.net is the one that directed us to use
>70.panavise.202.210.216.in-addr.arpa vs what the recent thread makes
>me believe it might need to be changed to
>70.202.210.216.in-addr.arpa instead.
>
>comments
>===============================================
>Gary Richter, President
> PanaVise Products, Inc.
> 7540 Colbert Dr. Reno, Nevada 89511
> Ph: 775.850.2900 Fx: 775.850.2929
> Email: grichter@panavise.com
> http://www.panavise.com
>===============================================
|

Return to Digital Point Solutions' Home Page |