 |  |
At 10:10 AM -0700 8/23/00, Warren Michelsen wrote:
Re: My Provider''s Reverse Zone
From: Men & Mice Support
Date: Wednesday, August 23, 2000
Time: 5:53:42 pm
>At 4:01 PM -0700 8/22/00, Men & Mice Support wrote:
>>>...
>>>I'm thinking that the az.net DNS is pretty screwed up but DNS Expert
>>>can't tell me much. (Or I haven't learned how to use it effectively
>>>in the short time since I bought it.)
>>>
>>>Can any of you human DNS experts help out? Where's the problem? Whom
>>>do I need to call and write about this?
>>
>>az.net is truly screwy. However, fortunately, that has no effect on
>>your reverse records.
>
>Sure it does since AZ.net is supposed to be doing my reverse zone. I
>have a small subnet with assigned IPs of 209.140.24.58-62 and none
>of my reverse is working. It used to be but then someone upstream of
>AZ.net changed something.
Problems in their domain are independent of problems in their reverse zone.
Your reverse records are part of a zone that is delegated to
conx.net. That domain works just fine.
az.net is delegated to ns1.conx.net and ns1.az.net. ns1.az.net is
badly misconfigured for az.net, to the point that ns1.conx.net can't
get a zone transfer for the zone.
>>Their servers, which are apparently ns1.conx.net and ns2.conx.net,
>>give the following answer when queried about one of your IP
>>addresses:
>>
>> 61.24.140.209.in-addr.arpa. PTR lists.mdcclxxvi.com.
>>
>> 24.140.209.in-addr.arpa. NS ns1.conx.net.
>> 24.140.209.in-addr.arpa. NS ns2.conx.net.
>>
>>That looks correct to me.
>
>And correct it may be but conx.net is not doing my reverse for me.
They are now.
>AZ.net is supposed to be delegated 24.140.209.in-addr.arpa. and they
>are supposed to be doing my reverse. In fact, their servers
>209.75.187.134 and 135 are, they tell me, configured with my reverse
>zones. But the world does not know to go to AZ.net's name servers
>for 24.140.209.in-addr.arpa.
Right. It's delegated as follows:
from f.root-servers.net:
140.209.in-addr.arpa. NS ns1.good.net.
140.209.in-addr.arpa. NS ns2.good.net.
140.209.in-addr.arpa. NS ns3.good.net.
from ns1.good.net:
24.140.209.in-addr.arpa. NS ns1.conx.net.
24.140.209.in-addr.arpa. NS ns2.conx.net.
>Personally, I'd rather they delegated my little subnet to me but
>AZ.net can't even seem to get the 209.140.24.xx class C properly
>delegated to them!
Do you have any contact with conx.net? If I had to guess, I'd say
that either conx.net is az.net's ISP, or else conx.net just bought
az.net.
>I'd be interested in your insights into AZ.net's DNS. Care to expand
>upon "truly screwy"? I'd like to take something more concrete and
>constructive when I go visit them to talk DNS.
As stated above. In more detail:
az.net is delegated as follows:
az.net. NS ns1.conx.net.
az.net. NS ns1.az.net.
ns1.az.net returns results with TTL's that don't decrement, but are
nevertheless marked non-authoritative. Since QuickDNS Pro has never
exhibited this behavior, I frankly can't tell you how they managed
that; I can only say that I've seen it before. Their server doesn't
report an SOA record - maybe they left it off the beginning of the
file.
At any rate, the server doesn't give zone transfers, probably because
it doesn't believe it has an authoritative copy of the zone. So
ns1.conx.net doesn't have any copy of the zone.
Oddly, though both servers are essentially lame, asking one of those
servers (ns1.az.net) for information about the zone generally yields
information. For example, if I query it for A records for www.az.net,
it gives me one. Of course, the answer is marked as
non-authoritative, but this shouldn't cause other servers to
disbelieve it. It appears to work.
____________________________________________________________________
Chris Buxton Men & Mice
cbuxton@menandmice.com We Make DNS Easy!
Messages In This Thread:
Return to Digital Point Solutions' Home Page