Bind 9.1.3 vs solaris8 bind?

[Brad Knowles]

At 4:51 PM +0000 8/22/01, Pierre Girard wrote:

>      we setup a dns server sometime ago and only recently we noticed that
>  some domains don't get resolved properly.  Since we have 3 dns servers
>  running, we looked on the other and it was working as expected.  After
>  looking a bit more, we noticed that if we used the named shipped with
>  solaris 8 with the same configuration files that it worked but not if we
>  used bind 9.1.3 (or 9.1.1 initially).

	You've got some problems.  Here are the results of using DNS 
Expert Professional 1.6 (see 
<http://www.menandmice.com/2000/2100_dns_expert.html>) on your domain:

                               DNS Expert
                      Detailed Report for inro.ca.
       8/22/01, 9:39 PM, using the analysis setting "Everything"
======================================================================

Information
----------------------------------------------------------------------
Serial number:           1615396030
Primary name server:     inronet.inro.ca.
Primary mail server:     inronet.inro.ca.
Number of records:       N/A


Errors
----------------------------------------------------------------------
o Non-authoritative data received from the server
   "twinkle.generation.net."
     The server "twinkle.generation.net." is listed as being
     authoritative for the domain, but it does not contain
     authoritative data for it.

o Unable to contact "inronet.inro.ca."
     It was not possible to establish a connection with the server
     "inronet.inro.ca.".  This server will not be used to check
     information about the zone.


Warnings
----------------------------------------------------------------------
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 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 zone contains more than one A record with the address
   206.167.22.3
     There is more than one A record in the zone with the IP address
     206.167.22.3.

o There is only one NS record in the zone
     The zone contains only one NS record.  Every zone should contain
     two or more NS records, and the NS records in the zone should
     match the delegation data for the domain.

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


	When one server is non-authoritative and the other doesn't 
answer, there's not much more you can do.  You've got major, major 
problems to fix.

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

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