1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
|
Good Zones for Testing Dlint
Some nameservers are set up to disallow AXFR's by non authorized hosts.
What's worse, some of them return _zero_records_ rather than an error!
All nameservers USWest has set up for DHCP-serving IP addresses to their
customers have this "bug" as of Feb 1998:
csh# dig @ns2.uswest.net. 190.225.207.in-addr.arpa. axfr
; <<>> DiG 2.2 <<>> @ns2.uswest.net. 190.225.207.in-addr.arpa. axfr
; (1 server found)
;; Received 0 answers (0 records).
;; FROM: fire.domtools.com to SERVER: 206.196.128.1
;; WHEN: Sun May 17 01:01:41 1998
csh# echo $status
0
This happens with these servers:
ns1.uswest.net.
ns2.uswest.net.
ns3.uswest.net.
----
earthlink.net. Really huge domain with numerous subdomains.
Took >4 hours run-time to lint on a Pentium 166 using
a direct 256KB (ADSL) connection to the Internet.
vix.com. Really good test zone: weird domains & sub-sub-domains,
nonexistent nameservers, multiple levels in 1 zone, etc.
wormhole.p-c-net.net.
defiant.p-c-net.net.
----
|
