Re: IP address fee??

[Brad Knowles <brad.knowles () skynet be>]

At 3:32 PM +0200 2002/09/06, Brad Knowles wrote:

> >   Have a look, for example, at the reverses for 193.109.122.192/28 and
> >   let me know if you can find anything wrong with those.

        The page you originally referenced says:

                The first three records are simply there to make BIND happy
                about loading the "zone" from the database file. (Would that
                it did not require them! But - alas! - it would complain were
                they not there.) Your content DNS server will serve those
                resource records up to the world (the "NS" resource records
                in the authority section of responses and the "SOA" resource
                record in "no such name" responses) but the world will ignore
                them, so this does not matter one iota. A correctly operating
                resolving proxy DNS server must discard them because their
                names are outside of your content DNS server's bailiwick.
                "in-addr.arpa." is not delegated to your content DNS server,
                only subdomains within it are.

	The key phrase is "A correctly operating resolving proxy DNS 
server must discard them ...".


	Do you have any idea whatsoever how many incredibly badly 
mis-configured and incorrectly operating caching nameservers there 
are in the world?!?

	My talk at LISA 2002 is going to cover (in part) how many badly 
mis-configured and incorrectly operating TLD nameservers there are in 
the world, and above all other servers of all other types (except the 
root servers themselves), these should be more correct and properly 
configured.  And yet, there is an unbelievable number of these 
servers that are not correctly configured, and some of them are 
incredibly screwed-up.

	$DEITY!!!  Even trying to conceive of the scale of the numbers of 
screwed-up caching nameservers just totally boggles the mind.  I 
doubt that there is anyone in the world that could come up with an 
accurate estimate.


	Now, if you wanted to do separate zone files, and make sure that 
each zone file doesn't contain any out-of-zone data, that would be a 
different issue.  But this is like handing people sticks of dynamite, 
flamethrowers, and encouraging them to ignite the explosives they're 
holding in their hands.

	If you really want to do this (and especially do it this way), 
all I can say is that, sooner or later, you *will* get what you 
deserve.

>         Bizarre.  Truly bizarre.  Somehow, I feel compelled to make some
>  remark about "perverting the course of the DNS", or somesuch.

        Now *this* is pretty cool:

                              DNS Expert
          Detailed Report for 192.122.109.193.in-addr.arpa.
       9/6/02, 4:05 PM, using the analysis setting "Everything"
======================================================================

Information
----------------------------------------------------------------------
Serial number:           1031317961
Primary name server:     ns.dataloss.nl.
Primary mail server:     N/A
Number of records:       N/A


Errors
----------------------------------------------------------------------
o The reverse zone contains one or more A records
    The reverse domain "192.122.109.193.in-addr.arpa." contains one
    or more A records.  A records should only be placed in
    forward-mapping domains.


Warnings
----------------------------------------------------------------------
o The name server "ns.dataloss.nl." does not permit zone transfers
    The name server "ns.dataloss.nl." has been configured to reject
    unauthorized zone transfers and the application will not be able
    to use data from this server while analyzing the zone.

o The name server "ns3.dataloss.nl." does not permit zone transfers
    The name server "ns3.dataloss.nl." has been configured to reject
    unauthorized zone transfers and the application will not be able
    to use data from this server while analyzing the zone.

o Zone transfer from authoritative servers not possible
    It was not possible to perform a zone transfer from any of the
    authoritative name servers for the zone.  This will limit the
    range of tests performed for the zone.

o The TTL field in the SOA record contains an unusually low value
    The value 2560 of the TTL field in the SOA record field is
    unusually low.  The value for this field should be within the
    range 3600 - 172800.

o The Minimum TTL field in the SOA record contains an unusually low
  value
    The value 2560 of the Minimum field in the SOA record is
    unusually low.  The value for this field should be within the
    range 3600 - 172800.

o The Serial number field in the SOA record contains an unusual value
    It appears that the Serial number field in the SOA record is
    based on a date value that is in the future.

o The TTL value 259200, in the A record "ns.dataloss.nl." is rather
  high
    The TTL value 259200, used in the A record "ns.dataloss.nl.", is
    unusually high.  The TTL value should be within the range 3600 -
    172800.

o The TTL value 259200, in the NS record
  "192.122.109.193.in-addr.arpa." is rather high
    The TTL value 259200, used in the NS record
    "192.122.109.193.in-addr.arpa.", is unusually high.  The TTL
    value should be within the range 3600 - 172800.

o All name servers for the zone are on the same subnet.
    All name servers for the zone are on the same subnet
    (193.109.122.*).  If the connection to the network breaks, your
    domain will become inaccessible.


----------------------------------------------------------------------
end of report



                              DNS Expert
          Detailed Report for 193.122.109.193.in-addr.arpa.
       9/6/02, 4:05 PM, using the analysis setting "Everything"
======================================================================

Information
----------------------------------------------------------------------
Serial number:           1031317961
Primary name server:     ns.dataloss.nl.
Primary mail server:     N/A
Number of records:       N/A


Errors
----------------------------------------------------------------------
o The reverse zone contains one or more A records
    The reverse domain "193.122.109.193.in-addr.arpa." contains one
    or more A records.  A records should only be placed in
    forward-mapping domains.


Warnings
----------------------------------------------------------------------
o The name server "ns.dataloss.nl." does not permit zone transfers
    The name server "ns.dataloss.nl." has been configured to reject
    unauthorized zone transfers and the application will not be able
    to use data from this server while analyzing the zone.

o The name server "ns3.dataloss.nl." does not permit zone transfers
    The name server "ns3.dataloss.nl." has been configured to reject
    unauthorized zone transfers and the application will not be able
    to use data from this server while analyzing the zone.

o Zone transfer from authoritative servers not possible
    It was not possible to perform a zone transfer from any of the
    authoritative name servers for the zone.  This will limit the
    range of tests performed for the zone.

o The TTL field in the SOA record contains an unusually low value
    The value 2560 of the TTL field in the SOA record field is
    unusually low.  The value for this field should be within the
    range 3600 - 172800.

o The Minimum TTL field in the SOA record contains an unusually low
  value
    The value 2560 of the Minimum field in the SOA record is
    unusually low.  The value for this field should be within the
    range 3600 - 172800.

o The Serial number field in the SOA record contains an unusual value
    It appears that the Serial number field in the SOA record is
    based on a date value that is in the future.

o The TTL value 259200, in the A record "ns.dataloss.nl." is rather
  high
    The TTL value 259200, used in the A record "ns.dataloss.nl.", is
    unusually high.  The TTL value should be within the range 3600 -
    172800.

o The TTL value 259200, in the NS record
  "193.122.109.193.in-addr.arpa." is rather high
    The TTL value 259200, used in the NS record
    "193.122.109.193.in-addr.arpa.", is unusually high.  The TTL
    value should be within the range 3600 - 172800.

o All name servers for the zone are on the same subnet.
    All name servers for the zone are on the same subnet
    (193.109.122.*).  If the connection to the network breaks, your
    domain will become inaccessible.


----------------------------------------------------------------------
end of report


        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: 6.122.109.193.IN-ADDR.ARPA PTR proxypool-6.undernet.org: unknown host
WARN: 7.122.109.193.IN-ADDR.ARPA PTR proxypool-7.undernet.org: unknown host
WARN: 8.122.109.193.IN-ADDR.ARPA PTR proxypool-8.undernet.org: unknown host
WARN: 9.122.109.193.IN-ADDR.ARPA PTR proxypool-9.undernet.org: unknown host
WARN: 10.122.109.193.IN-ADDR.ARPA PTR proxypool-10.undernet.org: unknown host
WARN: 11.122.109.193.IN-ADDR.ARPA PTR proxypool-11.undernet.org: unknown host
WARN: 12.122.109.193.IN-ADDR.ARPA PTR proxypool-12.undernet.org: unknown host
WARN: 13.122.109.193.IN-ADDR.ARPA PTR proxypool-13.undernet.org: unknown host
WARN: 14.122.109.193.IN-ADDR.ARPA PTR proxypool-14.undernet.org: unknown host
WARN: 15.122.109.193.IN-ADDR.ARPA PTR proxypool-15.undernet.org: unknown host
WARN: 16.122.109.193.IN-ADDR.ARPA PTR proxypool-16.undernet.org: unknown host
WARN: 17.122.109.193.IN-ADDR.ARPA PTR proxypool-17.undernet.org: unknown host
WARN: 18.122.109.193.IN-ADDR.ARPA PTR proxypool-18.undernet.org: unknown host
WARN: 20.122.109.193.IN-ADDR.ARPA PTR proxypool-20.undernet.org: unknown host
WARN: 19.122.109.193.IN-ADDR.ARPA PTR proxypool-19.undernet.org: unknown host
WARN: 21.122.109.193.IN-ADDR.ARPA PTR proxypool-21.undernet.org: unknown host
WARN: 22.122.109.193.IN-ADDR.ARPA PTR proxypool-22.undernet.org: unknown host
WARN: 23.122.109.193.IN-ADDR.ARPA PTR proxypool-23.undernet.org: unknown host
WARN: 24.122.109.193.IN-ADDR.ARPA PTR proxypool-24.undernet.org: unknown host
WARN: 25.122.109.193.IN-ADDR.ARPA PTR proxypool-25.undernet.org: unknown host
WARN: 26.122.109.193.IN-ADDR.ARPA PTR proxypool-26.undernet.org: unknown host
WARN: 27.122.109.193.IN-ADDR.ARPA PTR proxypool-27.undernet.org: unknown host
WARN: 28.122.109.193.IN-ADDR.ARPA PTR proxypool-28.undernet.org: unknown host
WARN: 30.122.109.193.IN-ADDR.ARPA PTR proxypool-30.undernet.org: unknown host
WARN: 29.122.109.193.IN-ADDR.ARPA PTR proxypool-29.undernet.org: unknown host
WARN: 31.122.109.193.IN-ADDR.ARPA PTR proxypool-31.undernet.org: unknown host
WARN: 32.122.109.193.IN-ADDR.ARPA PTR proxypool-32.undernet.org: unknown host
WARN: 33.122.109.193.IN-ADDR.ARPA PTR proxypool-33.undernet.org: unknown host
WARN: 34.122.109.193.IN-ADDR.ARPA PTR proxypool-34.undernet.org: unknown host
WARN: 35.122.109.193.IN-ADDR.ARPA PTR proxypool-35.undernet.org: unknown host
WARN: 36.122.109.193.IN-ADDR.ARPA PTR proxypool-36.undernet.org: unknown host
WARN: 210.122.109.193.IN-ADDR.ARPA PTR ns2.cluecentral.net: A record not found
WARN: 37.122.109.193.IN-ADDR.ARPA PTR proxypool-37.undernet.org: unknown host
WARN: 209.122.109.193.IN-ADDR.ARPA PTR shell.cluecentral.net: unknown host
WARN: 38.122.109.193.IN-ADDR.ARPA PTR proxypool-38.undernet.org: unknown host
WARN: 40.122.109.193.IN-ADDR.ARPA PTR proxypool-40.undernet.org: unknown host
WARN: 39.122.109.193.IN-ADDR.ARPA PTR proxypool-39.undernet.org: unknown host
WARN: 41.122.109.193.IN-ADDR.ARPA PTR proxypool-41.undernet.org: unknown host
WARN: 42.122.109.193.IN-ADDR.ARPA PTR proxypool-42.undernet.org: unknown host
WARN: 43.122.109.193.IN-ADDR.ARPA PTR proxypool-43.undernet.org: unknown host
WARN: 44.122.109.193.IN-ADDR.ARPA PTR proxypool-44.undernet.org: unknown host
WARN: 45.122.109.193.IN-ADDR.ARPA PTR proxypool-45.undernet.org: unknown host
WARN: 46.122.109.193.IN-ADDR.ARPA PTR proxypool-46.undernet.org: unknown host
WARN: 47.122.109.193.IN-ADDR.ARPA PTR proxypool-47.undernet.org: unknown host
WARN: 48.122.109.193.IN-ADDR.ARPA PTR proxypool-48.undernet.org: unknown host
WARN: 50.122.109.193.IN-ADDR.ARPA PTR proxypool-50.undernet.org: unknown host
WARN: 49.122.109.193.IN-ADDR.ARPA PTR proxypool-49.undernet.org: unknown host
WARN: 51.122.109.193.IN-ADDR.ARPA PTR proxypool-51.undernet.org: unknown host
WARN: 52.122.109.193.IN-ADDR.ARPA PTR proxypool-52.undernet.org: unknown host
WARN: 53.122.109.193.IN-ADDR.ARPA PTR proxypool-53.undernet.org: unknown host
WARN: 54.122.109.193.IN-ADDR.ARPA PTR proxypool-54.undernet.org: unknown host
WARN: 55.122.109.193.IN-ADDR.ARPA PTR proxypool-55.undernet.org: unknown host
WARN: 56.122.109.193.IN-ADDR.ARPA PTR proxypool-56.undernet.org: unknown host
WARN: 228.122.109.193.IN-ADDR.ARPA PTR vtun.dappekepatches.net: unknown host
WARN: 57.122.109.193.IN-ADDR.ARPA PTR proxypool-57.undernet.org: unknown host
WARN: 58.122.109.193.IN-ADDR.ARPA PTR proxypool-58.undernet.org: unknown host
WARN: 60.122.109.193.IN-ADDR.ARPA PTR proxypool-60.undernet.org: unknown host
WARN: 59.122.109.193.IN-ADDR.ARPA PTR proxypool-59.undernet.org: unknown host
Checking 192.122.109.193.in-addr.arpa
Getting zone transfer of 192.122.109.193.in-addr.arpa from 
ns.dataloss.nl...failed
FAIL: Zone transfer of 192.122.109.193.in-addr.arpa from 
ns.dataloss.nl failed: NOERROR
Getting zone transfer of 192.122.109.193.in-addr.arpa from 
ns3.dataloss.nl...failed
FAIL: Zone transfer of 192.122.109.193.in-addr.arpa from 
ns3.dataloss.nl failed: NOERROR
BAD: All zone transfer attempts of 192.122.109.193.in-addr.arpa failed!
Checking 193.122.109.193.in-addr.arpa
Getting zone transfer of 193.122.109.193.in-addr.arpa from 
ns.dataloss.nl...failed
FAIL: Zone transfer of 193.122.109.193.in-addr.arpa from 
ns.dataloss.nl failed: NOERROR
Getting zone transfer of 193.122.109.193.in-addr.arpa from 
ns3.dataloss.nl...failed
FAIL: Zone transfer of 193.122.109.193.in-addr.arpa from 
ns3.dataloss.nl failed: NOERROR
BAD: All zone transfer attempts of 193.122.109.193.in-addr.arpa failed!
Checking 194.122.109.193.in-addr.arpa
Getting zone transfer of 194.122.109.193.in-addr.arpa from 
ns.dataloss.nl...failed
FAIL: Zone transfer of 194.122.109.193.in-addr.arpa from 
ns.dataloss.nl failed: NOERROR
Getting zone transfer of 194.122.109.193.in-addr.arpa from 
ns3.dataloss.nl...failed
FAIL: Zone transfer of 194.122.109.193.in-addr.arpa from 
ns3.dataloss.nl failed: NOERROR
BAD: All zone transfer attempts of 194.122.109.193.in-addr.arpa failed!
Checking 195.122.109.193.in-addr.arpa
Getting zone transfer of 195.122.109.193.in-addr.arpa from 
ns.dataloss.nl...failed
FAIL: Zone transfer of 195.122.109.193.in-addr.arpa from 
ns.dataloss.nl failed: NOERROR
Getting zone transfer of 195.122.109.193.in-addr.arpa from 
ns3.dataloss.nl...failed
FAIL: Zone transfer of 195.122.109.193.in-addr.arpa from 
ns3.dataloss.nl failed: NOERROR
BAD: All zone transfer attempts of 195.122.109.193.in-addr.arpa failed!
Checking 196.122.109.193.in-addr.arpa
Getting zone transfer of 196.122.109.193.in-addr.arpa from 
ns.dataloss.nl...failed
FAIL: Zone transfer of 196.122.109.193.in-addr.arpa from 
ns.dataloss.nl failed: NOERROR
Getting zone transfer of 196.122.109.193.in-addr.arpa from 
ns3.dataloss.nl...failed
FAIL: Zone transfer of 196.122.109.193.in-addr.arpa from 
ns3.dataloss.nl failed: NOERROR
BAD: All zone transfer attempts of 196.122.109.193.in-addr.arpa failed!
Checking 197.122.109.193.in-addr.arpa
Getting zone transfer of 197.122.109.193.in-addr.arpa from 
ns.dataloss.nl...failed
FAIL: Zone transfer of 197.122.109.193.in-addr.arpa from 
ns.dataloss.nl failed: NOERROR
Getting zone transfer of 197.122.109.193.in-addr.arpa from 
ns3.dataloss.nl...failed
FAIL: Zone transfer of 197.122.109.193.in-addr.arpa from 
ns3.dataloss.nl failed: NOERROR
BAD: All zone transfer attempts of 197.122.109.193.in-addr.arpa failed!
Checking 198.122.109.193.in-addr.arpa
Getting zone transfer of 198.122.109.193.in-addr.arpa from 
ns.dataloss.nl...failed
FAIL: Zone transfer of 198.122.109.193.in-addr.arpa from 
ns.dataloss.nl failed: NOERROR
Getting zone transfer of 198.122.109.193.in-addr.arpa from 
ns3.dataloss.nl...failed
FAIL: Zone transfer of 198.122.109.193.in-addr.arpa from 
ns3.dataloss.nl failed: NOERROR
BAD: All zone transfer attempts of 198.122.109.193.in-addr.arpa failed!
Checking 199.122.109.193.in-addr.arpa
Getting zone transfer of 199.122.109.193.in-addr.arpa from 
ns.dataloss.nl...failed
FAIL: Zone transfer of 199.122.109.193.in-addr.arpa from 
ns.dataloss.nl failed: NOERROR
Getting zone transfer of 199.122.109.193.in-addr.arpa from 
ns3.dataloss.nl...failed
FAIL: Zone transfer of 199.122.109.193.in-addr.arpa from 
ns3.dataloss.nl failed: NOERROR
BAD: All zone transfer attempts of 199.122.109.193.in-addr.arpa failed!
Checking 200.122.109.193.in-addr.arpa
Getting zone transfer of 200.122.109.193.in-addr.arpa from 
ns.dataloss.nl...failed
FAIL: Zone transfer of 200.122.109.193.in-addr.arpa from 
ns.dataloss.nl failed: NOERROR
Getting zone transfer of 200.122.109.193.in-addr.arpa from 
ns3.dataloss.nl...failed
FAIL: Zone transfer of 200.122.109.193.in-addr.arpa from 
ns3.dataloss.nl failed: NOERROR
BAD: All zone transfer attempts of 200.122.109.193.in-addr.arpa failed!
Checking 201.122.109.193.in-addr.arpa
Getting zone transfer of 201.122.109.193.in-addr.arpa from 
ns.dataloss.nl...failed
FAIL: Zone transfer of 201.122.109.193.in-addr.arpa from 
ns.dataloss.nl failed: NOERROR
Getting zone transfer of 201.122.109.193.in-addr.arpa from 
ns3.dataloss.nl...failed
FAIL: Zone transfer of 201.122.109.193.in-addr.arpa from 
ns3.dataloss.nl failed: NOERROR
BAD: All zone transfer attempts of 201.122.109.193.in-addr.arpa failed!
Checking 202.122.109.193.in-addr.arpa
Getting zone transfer of 202.122.109.193.in-addr.arpa from 
ns.dataloss.nl...failed
FAIL: Zone transfer of 202.122.109.193.in-addr.arpa from 
ns.dataloss.nl failed: NOERROR
Getting zone transfer of 202.122.109.193.in-addr.arpa from 
ns3.dataloss.nl...failed
FAIL: Zone transfer of 202.122.109.193.in-addr.arpa from 
ns3.dataloss.nl failed: NOERROR
BAD: All zone transfer attempts of 202.122.109.193.in-addr.arpa failed!
Checking 203.122.109.193.in-addr.arpa
Getting zone transfer of 203.122.109.193.in-addr.arpa from 
ns.dataloss.nl...failed
FAIL: Zone transfer of 203.122.109.193.in-addr.arpa from 
ns.dataloss.nl failed: NOERROR
Getting zone transfer of 203.122.109.193.in-addr.arpa from 
ns3.dataloss.nl...failed
FAIL: Zone transfer of 203.122.109.193.in-addr.arpa from 
ns3.dataloss.nl failed: NOERROR
BAD: All zone transfer attempts of 203.122.109.193.in-addr.arpa failed!
Checking 204.122.109.193.in-addr.arpa
Getting zone transfer of 204.122.109.193.in-addr.arpa from 
ns.dataloss.nl...failed
FAIL: Zone transfer of 204.122.109.193.in-addr.arpa from 
ns.dataloss.nl failed: NOERROR
Getting zone transfer of 204.122.109.193.in-addr.arpa from 
ns3.dataloss.nl...failed
FAIL: Zone transfer of 204.122.109.193.in-addr.arpa from 
ns3.dataloss.nl failed: NOERROR
BAD: All zone transfer attempts of 204.122.109.193.in-addr.arpa failed!
Checking 205.122.109.193.in-addr.arpa
Getting zone transfer of 205.122.109.193.in-addr.arpa from 
ns.dataloss.nl...failed
FAIL: Zone transfer of 205.122.109.193.in-addr.arpa from 
ns.dataloss.nl failed: NOERROR
Getting zone transfer of 205.122.109.193.in-addr.arpa from 
ns3.dataloss.nl...failed
FAIL: Zone transfer of 205.122.109.193.in-addr.arpa from 
ns3.dataloss.nl failed: NOERROR
BAD: All zone transfer attempts of 205.122.109.193.in-addr.arpa failed!
Checking 206.122.109.193.in-addr.arpa
Getting zone transfer of 206.122.109.193.in-addr.arpa from 
ns.dataloss.nl...failed
FAIL: Zone transfer of 206.122.109.193.in-addr.arpa from 
ns.dataloss.nl failed: NOERROR
Getting zone transfer of 206.122.109.193.in-addr.arpa from 
ns3.dataloss.nl...failed
FAIL: Zone transfer of 206.122.109.193.in-addr.arpa from 
ns3.dataloss.nl failed: NOERROR
BAD: All zone transfer attempts of 206.122.109.193.in-addr.arpa failed!
Checking 207.122.109.193.in-addr.arpa
Getting zone transfer of 207.122.109.193.in-addr.arpa from 
ns.dataloss.nl...failed
FAIL: Zone transfer of 207.122.109.193.in-addr.arpa from 
ns.dataloss.nl failed: NOERROR
Getting zone transfer of 207.122.109.193.in-addr.arpa from 
ns3.dataloss.nl...failed
FAIL: Zone transfer of 207.122.109.193.in-addr.arpa from 
ns3.dataloss.nl failed: NOERROR
BAD: All zone transfer attempts of 207.122.109.193.in-addr.arpa failed!
32 failures, 58 warnings, 16 errors.


        And this:

                              DNS Expert
            Detailed Report for 122.109.193.in-addr.arpa.
       9/6/02, 3:56 PM, using the analysis setting "Everything"
======================================================================

Information
----------------------------------------------------------------------
Serial number:           2002090401
Primary name server:     ns.bit.nl.
Primary mail server:     N/A
Number of records:       112 (34 NS, 0 MX, 0 A, 0 CNAME, 78 PTR, 0
                         Other)


Errors
----------------------------------------------------------------------
o Lame delegation received from "ns.ansible.org." for "undernet.org."
    The server "ns.ansible.org." is listed as being authoritative for
    "undernet.org.", but "ns.ansible.org." does not contain
    authoritative data for the zone.

o There is no A record for the host name "6.122.109.193.in-addr.arpa."
    The host "proxypool-6.undernet.org." (referred to by
    "6.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name "7.122.109.193.in-addr.arpa."
    The host "proxypool-7.undernet.org." (referred to by
    "7.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name "8.122.109.193.in-addr.arpa."
    The host "proxypool-8.undernet.org." (referred to by
    "8.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name "9.122.109.193.in-addr.arpa."
    The host "proxypool-9.undernet.org." (referred to by
    "9.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "10.122.109.193.in-addr.arpa."
    The host "proxypool-10.undernet.org." (referred to by
    "10.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "11.122.109.193.in-addr.arpa."
    The host "proxypool-11.undernet.org." (referred to by
    "11.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "12.122.109.193.in-addr.arpa."
    The host "proxypool-12.undernet.org." (referred to by
    "12.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "13.122.109.193.in-addr.arpa."
    The host "proxypool-13.undernet.org." (referred to by
    "13.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "14.122.109.193.in-addr.arpa."
    The host "proxypool-14.undernet.org." (referred to by
    "14.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "15.122.109.193.in-addr.arpa."
    The host "proxypool-15.undernet.org." (referred to by
    "15.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "16.122.109.193.in-addr.arpa."
    The host "proxypool-16.undernet.org." (referred to by
    "16.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "17.122.109.193.in-addr.arpa."
    The host "proxypool-17.undernet.org." (referred to by
    "17.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "18.122.109.193.in-addr.arpa."
    The host "proxypool-18.undernet.org." (referred to by
    "18.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "20.122.109.193.in-addr.arpa."
    The host "proxypool-20.undernet.org." (referred to by
    "20.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "19.122.109.193.in-addr.arpa."
    The host "proxypool-19.undernet.org." (referred to by
    "19.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "21.122.109.193.in-addr.arpa."
    The host "proxypool-21.undernet.org." (referred to by
    "21.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "22.122.109.193.in-addr.arpa."
    The host "proxypool-22.undernet.org." (referred to by
    "22.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "23.122.109.193.in-addr.arpa."
    The host "proxypool-23.undernet.org." (referred to by
    "23.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "24.122.109.193.in-addr.arpa."
    The host "proxypool-24.undernet.org." (referred to by
    "24.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "25.122.109.193.in-addr.arpa."
    The host "proxypool-25.undernet.org." (referred to by
    "25.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "26.122.109.193.in-addr.arpa."
    The host "proxypool-26.undernet.org." (referred to by
    "26.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "27.122.109.193.in-addr.arpa."
    The host "proxypool-27.undernet.org." (referred to by
    "27.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "28.122.109.193.in-addr.arpa."
    The host "proxypool-28.undernet.org." (referred to by
    "28.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "30.122.109.193.in-addr.arpa."
    The host "proxypool-30.undernet.org." (referred to by
    "30.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "29.122.109.193.in-addr.arpa."
    The host "proxypool-29.undernet.org." (referred to by
    "29.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "31.122.109.193.in-addr.arpa."
    The host "proxypool-31.undernet.org." (referred to by
    "31.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "32.122.109.193.in-addr.arpa."
    The host "proxypool-32.undernet.org." (referred to by
    "32.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "33.122.109.193.in-addr.arpa."
    The host "proxypool-33.undernet.org." (referred to by
    "33.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "34.122.109.193.in-addr.arpa."
    The host "proxypool-34.undernet.org." (referred to by
    "34.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "35.122.109.193.in-addr.arpa."
    The host "proxypool-35.undernet.org." (referred to by
    "35.122.109.193.in-addr.arpa.") does not exist.

o The host "ns2.cluecentral.net." referred to by
  "210.122.109.193.in-addr.arpa." does not have the IP address
  193.109.122.210
    The PTR record "210.122.109.193.in-addr.arpa." refers to the host
    "ns2.cluecentral.net.", but a query for "ns2.cluecentral.net."
    found a host with a different IP address than 193.109.122.210

o There is no A record for the host name
  "36.122.109.193.in-addr.arpa."
    The host "proxypool-36.undernet.org." (referred to by
    "36.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "209.122.109.193.in-addr.arpa."
    The host "shell.cluecentral.net." (referred to by
    "209.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "37.122.109.193.in-addr.arpa."
    The host "proxypool-37.undernet.org." (referred to by
    "37.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "40.122.109.193.in-addr.arpa."
    The host "proxypool-40.undernet.org." (referred to by
    "40.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "38.122.109.193.in-addr.arpa."
    The host "proxypool-38.undernet.org." (referred to by
    "38.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "41.122.109.193.in-addr.arpa."
    The host "proxypool-41.undernet.org." (referred to by
    "41.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "39.122.109.193.in-addr.arpa."
    The host "proxypool-39.undernet.org." (referred to by
    "39.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "42.122.109.193.in-addr.arpa."
    The host "proxypool-42.undernet.org." (referred to by
    "42.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "43.122.109.193.in-addr.arpa."
    The host "proxypool-43.undernet.org." (referred to by
    "43.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "44.122.109.193.in-addr.arpa."
    The host "proxypool-44.undernet.org." (referred to by
    "44.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "45.122.109.193.in-addr.arpa."
    The host "proxypool-45.undernet.org." (referred to by
    "45.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "46.122.109.193.in-addr.arpa."
    The host "proxypool-46.undernet.org." (referred to by
    "46.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "47.122.109.193.in-addr.arpa."
    The host "proxypool-47.undernet.org." (referred to by
    "47.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "50.122.109.193.in-addr.arpa."
    The host "proxypool-50.undernet.org." (referred to by
    "50.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "48.122.109.193.in-addr.arpa."
    The host "proxypool-48.undernet.org." (referred to by
    "48.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "51.122.109.193.in-addr.arpa."
    The host "proxypool-51.undernet.org." (referred to by
    "51.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "49.122.109.193.in-addr.arpa."
    The host "proxypool-49.undernet.org." (referred to by
    "49.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "52.122.109.193.in-addr.arpa."
    The host "proxypool-52.undernet.org." (referred to by
    "52.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "53.122.109.193.in-addr.arpa."
    The host "proxypool-53.undernet.org." (referred to by
    "53.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "54.122.109.193.in-addr.arpa."
    The host "proxypool-54.undernet.org." (referred to by
    "54.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "55.122.109.193.in-addr.arpa."
    The host "proxypool-55.undernet.org." (referred to by
    "55.122.109.193.in-addr.arpa.") does not exist.

o The server "not-renewed.joker.com." did not reply
    The server "not-renewed.joker.com." did not reply when it was
    queried for the name "vtun.dappekepatches.net.".  This indicates
    that the server is not running, or it is currently unreachable.

o There is no A record for the host name
  "228.122.109.193.in-addr.arpa."
    The host "vtun.dappekepatches.net." (referred to by
    "228.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "56.122.109.193.in-addr.arpa."
    The host "proxypool-56.undernet.org." (referred to by
    "56.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "57.122.109.193.in-addr.arpa."
    The host "proxypool-57.undernet.org." (referred to by
    "57.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "60.122.109.193.in-addr.arpa."
    The host "proxypool-60.undernet.org." (referred to by
    "60.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "58.122.109.193.in-addr.arpa."
    The host "proxypool-58.undernet.org." (referred to by
    "58.122.109.193.in-addr.arpa.") does not exist.

o There is no A record for the host name
  "59.122.109.193.in-addr.arpa."
    The host "proxypool-59.undernet.org." (referred to by
    "59.122.109.193.in-addr.arpa.") does not exist.


Warnings
----------------------------------------------------------------------
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.

o There is more than one PTR record referring to
  "ns2.cluecentral.net."
    The zone contains more than one PTR record referring to the host
    "ns2.cluecentral.net."

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.


----------------------------------------------------------------------
end of report

--
Brad Knowles, <brad.knowles () skynet be>

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
    -Benjamin Franklin, Historical Review of Pennsylvania.

GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E W+++(--) N+ !w---
O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)