BIND 9.2.0 named.conf problem

[Danny Mayer]

The only problems that I noticed was that the com. root servers list
TSERV1.TREFFO.SE. as one of the nameservers for izaxon.com
and that server does not exist in the treffo.se zone.  Your nameserver
on server.izaxon.com lists the other nameserver as tserv3.treffo.se.
so you need to contact the registrar to get the name and address changed.

The singularity.se zone looks to be okay and lists tserv3.treffo.se. as the
other server which agrees with what the se. root servers think it is.  However
the SOA serial numbers disagree.  Does tserv3 think that it is the master
for the zone?  Are there any errors on that machine when loading or
transferring the zone?

         Danny
At 08:36 AM 3/5/02, Johan Isaksson wrote:

>I run BIND 9.2.0 on Windows XP Prof. The following named.conf file
>seems to work, but information is not replicated (copied) to other
>name servers (both secondary DNS and other name servers). I have
>updated the serial number.
>Any help is appreciated!
>Thanks,
>Johan
>
>---->named.conf
>options {
>      directory "/windows/system32/dns/etc";           // Working
>directory
>      pid-file "named.pid";              // Put pid file in working dir
>      allow-query { any; };              // This is the default
>      recursion no;                      // Do not provide recursive
>service
>};
>
>// Root server hints
>zone "." {
>      type hint;
>      file "named.cache";
>};
>
>// Provide a reverse mapping for the loopback address 127.0.0.1
>zone "0.0.127.in-addr.arpa" {
>      type master;
>      file "db.127.0.0";
>      notify no;
>};
>
>zone "21.181.212.in-addr.arpa" {
>      type master;
>      notify no;
>      file "db.inaddr";
>};
>
>zone "izaxon.com" {
>      type master;
>      file "izaxon.com";
>};
>
>zone "singularity.se" {
>      type master;
>      file "singularity.se";
>};