nslookup response ???

[Brad Knowles]

At 5:31 PM -0400 8/31/01, Bill wrote:

>  Hm-m-m. Everything would have probobly made more sense if I had asked the
>  right question. When I try to get sarahwoody.com, the browser always looks
>  to 63.90.....while never looking at the primary dns which is 216.253...
>  The site is actually on the 216 server. The 63 server is actually a dead
>  issue backup. (If I ever figure out bind, I will have a back-up dns box at
>  the end of a cable modem.

	This domain is definitely pretty screwed up.  I checked it out 
with the full registered version of DNS Expert Professional 1.6 (see 
<http://www.menandmice.com/2000/2100_dns_expert.html>), and here's 
what I got:

                               DNS Expert
                  Detailed Report for sarahwoody.com.
        9/1/01, 1:20 AM, using the analysis setting "Everything"
======================================================================

Information
----------------------------------------------------------------------
Serial number:           82501
Primary name server:     sarahwoody.com.
Primary mail server:     bertha.mysp.net.
Number of records:       N/A


Errors
----------------------------------------------------------------------
o The server "ns1.bicity.net." did not reply
     The server "ns1.bicity.net." did not reply when it was queried
     for the name "sarahwoody.com.".  This indicates that the server
     is not running, or it is currently unreachable.

o The name server "bertha.mysp.net." is only listed in delegation data
     The server "bertha.mysp.net." is listed as being authoritative
     for the zone according to the delegation data, but there is no NS
     record for that server in the zone data.  Delegation data and
     zone data should always match.

o Unable to resolve the host name "ns1.bluestar.net." used in the NS
   record "sarahwoody.com."
     It was not possible to resolve the host name "ns1.bluestar.net."
     which is used in the NS record for "sarahwoody.com."  This
     indicates that a host with the name "ns1.bluestar.net." does not
     exist.

o Unable to resolve the host name "ns2.bluestar.net." used in the NS
   record "sarahwoody.com."
     It was not possible to resolve the host name "ns2.bluestar.net."
     which is used in the NS record for "sarahwoody.com."  This
     indicates that a host with the name "ns2.bluestar.net." does not
     exist.


Warnings
----------------------------------------------------------------------
o "bertha.mysp.net." does not contain the latest version of the zone
     "bertha.mysp.net." contains an old version of the zone.  The
     latest version of the zone has the serial number "2001020301",
     but the version contained at "bertha.mysp.net." has the serial
     number "82501".

o The name server "ns1.thepurist.org." does not permit zone transfers
     The name server "ns1.thepurist.org." 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 Expire field in the SOA record contains an unusually low value
     The value 7200 of the Expire field in the SOA record is unusually
     low.  The value for this field should be within the range 86400 -
     3600000.

o The expire value in the SOA record is too close to the refresh value
     The value of the Expire field in the SOA record (currently 7200)
     should be at least three times bigger than the value of the
     Refresh field (currently 3600).

o The refresh value in the SOA record is too close to the retry value
     The value of the Refresh field in the SOA record (currently 3600)
     should be at least three times bigger than the value of the Retry
     field (currently 1800).

o The zone contains more than one A record with the address
   216.253.137.36
     There is more than one A record in the zone with the IP address
     216.253.137.36.

o There is only one MX record in the zone
     The zone contains only one MX record.  This will cause mail
     delivery problems if the primary mail server becomes unavailable.
      For safety purposes, there should be two or more mail servers
     for every zone, the extra mail servers being used as backup
     (secondary) servers for the primary server.


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

-- 
Brad Knowles, <brad.knowles at skynet.be>

H4sICIFgXzsCA2RtYS1zaWcAPVHLbsMwDDvXX0H0kkvbfxiwVw8FCmzAzqqj1F4dy7CdBfn7
Kc6wmyGRFEnvvxiWQoCvqI7RSWTcfGXQNqCUAnfIU+AT8OZ/GCNjRVlH0bKpguJkxiITZqes
MxwpSucyDJzXxQEUe/ihgXqJXUXwD9ajB6NHonLmNrUSK9nacHQnH097szO74xFXqtlbT3il
wMsBz5cnfCR5cEmci0Rj9u/jqBbPeES1I4PeFBXPUIT1XDSOuutFXylzrQvGyboWstCoQZyP
dxX4dLx0eauFe1x9puhoi0Ao1omEJo+BZ6XLVNaVpWiKekxN0VK2VMpmAy+Bk7ZV4SO+p1L/
uErNRS/qH2iFU+iNOtbcmVt9N16lfF7tLv9FXNj8AiyNcOi1AQAA