|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: IP address fee??
On Fri, 6 Sep 2002, Brad Knowles wrote:
> What about this?
>
> % dnswalk -ralF 122.109.193.in-addr.arpa.
> Checking 122.109.193.in-addr.arpa.
> Getting zone transfer of 122.109.193.in-addr.arpa. from ns2.bit.nl...done.
> SOA=ns.bit.nl contact=root.bit.nl
> WARN: 210.122.109.193.IN-ADDR.ARPA PTR ns2.cluecentral.net: A record not found
Typo, should be ns1.cluecentral.net
> WARN: 209.122.109.193.IN-ADDR.ARPA PTR shell.cluecentral.net: unknown host
Stale entry, removed.
> WARN: 228.122.109.193.IN-ADDR.ARPA PTR vtun.dappekepatches.net: unknown host
Domain expired.
> WARN: 60.122.109.193.IN-ADDR.ARPA PTR proxypool-60.undernet.org: unknown host
The *.undernet.org are a special thing. The non-existing forwards are on
purpose.
> And this:
>
> DNS Expert
> Detailed Report for 122.109.193.in-addr.arpa.
> 9/6/02, 3:56 PM, using the analysis setting "Everything"
> ======================================================================
> ----------------------------------------------------------------------
> o Server name in the SOA record differs from server name in an NS
> record
> The name server with the IP address 213.136.0.66 is identified by
> the name "ns.bit.nl." in the SOA record but the NS record uses
> the name "ns1.bit.nl." for the host.
Same box. Non-issue but fixt anyway.
> o All name servers for the zone are on the same subnet.
> All name servers for the zone are on the same subnet
> (213.136.0.*). If the connection to the network breaks, your
> domain will become inaccessible.
Which brings us partly back to the originating discussion. 213.136.0.66
and 213.136.0.77 do not necesarily have to be on the same subnet.
--
Sabri Berisha - www.cluecentral.net - "I route, therefore you are"
- nooit meer naar Bonaire: http://nu.nl/document?n=59946 -
"Waarom draait er een mailserver op die $mailserver?"
- Pim van Pelt
|