named 9.2.1 external resolution problem on 2nd slave (Solaris 9)

From: Gene Matthews (gene@xogent.com)
Date: Wed Mar 09 2005 - 17:31:30 EST


Hi all,

I have added a third dns server to the mix. All are Solaris 9 running
bind 9.2.1. The master and existing slave are working great. They
resolve internally as well as external domain names just fine.

The 2nd slave was pretty much cloned from the existing slave as far as
OS and bind. I can't see any differences in named.conf or zone.conf
files, file permissions, etc. Their may be something different, but if
so, I haven't found it yet.

named starts ok with no errors on the 2nd (new) slave but it will not
resolve anything external. The hints zone is defined on this one just
as it is on the first slave, but name resolution times out.

Some (hopefully) pertinent file sections are below:

===========
1st slave (working ok):
named.conf:
===========
controls {
       inet 127.0.0.1 port 953
       allow { 127.0.0.1; } keys { "rndc-key"; };
};

options {
        directory "/"; #working directory
        pid-file "etc/named.pid"; #pid file in working dir
        query-source address * port 53;
        statistics-file "stats/named.stats";
        recursion no;
        allow-transfer { none; };
};

view "thishost" {
        match-clients { 127.0.0.1; };
        recursion yes;
        include "etc/zones.conf";
};

view "otherhosts" {
        match-clients { any; };
        include "etc/zones.conf";
};

===========
1st slave (working ok):
zonesconf:
===========

zone "." {
        type hint;
        file "zones/named.root";
        # not allowed here # allow-transfer { can-axfr; };
};

zone "0.0.127.IN-ADDR.ARPA" {
        type master;
        file "zones/named.local";
        notify no;
        allow-transfer { can-axfr; };
};

Above is all from a working slave. Some sections were left out. Below
is from the slave that won't resolv external names. Otherwise it
appears to be working fine. Zone transfers are occuring. The
named.root (hints) files are identical. In fact, the 2nd slave's
/var/named directory was copied from the 1st slave servers.

===========
2nd slave (not working ok):
named.conf:
===========
controls {
       inet 127.0.0.1 port 953
               allow { 127.0.0.1; } keys { "rndc-key"; };
};

options {
        directory "/"; #working directory
        pid-file "etc/named.pid"; #pid file in working dir
        query-source address * port 53;
        statistics-file "stats/named.stats";
        recursion no;
        allow-transfer { none; };
};

view "thishost" {
        match-clients { 127.0.0.1; };
        recursion yes;
        include "etc/zones.conf";
};

view "otherhosts" {
        match-clients { any; };
        include "etc/zones.conf";
};

===========
2nd slave (not working ok):
zonesconf:
===========

zone "." {
        type hint;
        file "zones/named.root";
        # not allowed here # allow-transfer { can-axfr; };
};

zone "0.0.127.IN-ADDR.ARPA" {
        type master;
        file "zones/named.local";
        notify no;
        allow-transfer { can-axfr; };
};

I'm certainly not a bind expert, and I'm open for suggestions on what to
look at next.

Thanks,

Gene
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers



This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:30:19 EDT