Re: Zone file access

[Paul Vixie <paul () vix com>]

> > Dear Customer,
> >
> > Thank you for contacting Network Solutions, Inc., InterNIC
> > Registration Services.
> >
> > We cannot give you access to our database for all records, other than
> > what is in our whois database, is confidential and not available to the
> > public.
> >
> > Best Regards,
> > II
> > Network Solutions, Inc. 

Network Solutions has never actually asked me to stop allowing full outbound
zone transfers of all InterNIC TLD's from F.ROOT-SERVERS.NET.  According to
my logs, "dig @192.5.5.241 xxx axfr > xxx.zone" is a rather popular command:

[dns1.pa:alpha] wc -l xfer.log*
      1702 xfer.log
       306 xfer.log.0
      5560 xfer.log.1
      3219 xfer.log.2
     16859 xfer.log.3
     12066 xfer.log.4
     39712 total
[dns1.pa:alpha] ls -l xfer.log*
-rw-r--r--   1 root     system    162968 May 15 00:22 xfer.log
-rw-r--r--   1 root     system     29856 May  7 17:00 xfer.log.0
-rw-r--r--   1 root     system    546016 May  6 22:01 xfer.log.1
-rw-r--r--   1 root     system    325942 Apr 15 21:05 xfer.log.2
-rw-r--r--   1 root     system   1724302 Apr  6 19:08 xfer.log.3
-rw-r--r--   1 root     system   1194194 Feb 28 11:35 xfer.log.4

If NSI should ask me to restrict outbound zone transfers, then I would of
course immediately ask the IANA whether to comply with that request.  And
so now you all know why BIND-8's first development priority was to stop
forking for outbound zone transfers -- I can export the COM zone 50 times
in parallel (and I sometimes do) without changing the runtime profile of
F.ROOT-SERVERS.NET.
-- 
Paul Vixie
La Honda, CA
<paul () vix com>                       "Many NANOG members have been around
pacbell!vixie!paul               longer than most." --Jim Fleming