BIND 9.2.4 Slow on Solaris 10 01/06

Question

Hi There,
Have an issue with 2 x Solaris 10 (Sparc) external DNS servers that we put in. The servers are very quick to resolve local zone files and any cached queries. When i'm requesting a new internet DNS record that is not in the cache, it can take 5-6 seconds for the query to come back.
I've been doing some reading and other people have had similar issues with IPV4/IPV6 queries. When looking at my bind debug logs i can see that requests go out for AAAA records. The servers are not running IPV6 themselves.
Is there any way to disable IPV6 in Bind 9.2.4 or has anyone come across this problem before and its something completely different?
Thanks

Answer 1

We only have one search domain that is used internally, the external dns servers host about 25 zones on them that they are authoritive for. The 2 external servers are also used by the 2 internal servers to handle internet resolution. Its only slow when requesting FQDN's from the internet that are not int he cache. If i clear the bind cache and look up say www.microsoft.com it takes 5-6 seconds to resolve. Next time its instant.
Here is most of the named.conf (cut out some of the hosted zones to limit the length);
acl bogusnets { 0.0.0.0/8; 2.0.0.0/8; 224.0.0.0/3; };
acl local { 172.19.220.0/32; 172.22.280.0/32; };
acl local { 127.0.0.1/8; };
options {
     directory "/var/zones";
     allow-recursion { local; };
     allow-transfer { 172.19.82.17; 172.19.220.4; 172.19.280.5; };
     blackhole { bogusnets; };
logging {
     category default { default_log; };
     category queries { query_log; };
     category network { network_log; };
     channel default_log {
          file "/var/logs/default.log" versions 7 size 10m;
          print-category     yes;
          print-severity     yes;
          print-time     yes;
     channel query_log {
          file "/var/logs/query.log" versions 7 size 10m;
          print-category     yes;
          print-severity     yes;
          print-time     yes;
     channel network_log {
          file "/var/logs/network.log" versions 7 size 10m;
          print-category     yes;
          print-severity     yes;
          print-time     yes;
     category lame-servers { null; };
zone "." {
     type hint;
     file "named.cache";
zone "0.0.127.IN-ADDR.ARPA" {
     type master;
     file "master/db.reverse.127.0.0";
# Reverse lookups for 172.20
zone "20.172.IN-ADDR.ARPA" {
     type master;
     file "master/db.reverse.172.20";
# Reverse lookups for 172.19
zone "191.150.IN-ADDR.ARPA" {
     type master;
     file "master/db.reverse.172.19";
# Reverse lookups for 172.20
zone "205.155.IN-ADDR.ARPA" {
     type master;
     file "master/db.reverse.172.20";
zone "example.com" {
     type master;
     file "master/db.example.com";     
zone "abc.int" {
     type stub;
     file "slave/db.abc.int";
     allow-query { internal; local; };
     masters { 172.20.7.120; 172.20.7.121; };
zone "testing.com" {
     type stub;
     file "slave/db.testing.com";
     allow-query { internal; local; };
     masters { 172.20.8.161; 172.20.7.119; };
Message was edited by:
jgooding