bind 9.7.2-P3 does not resolve www.microsoft.com

[T. Wunderlich]

I have a problem with a bind 9.7.2-P3 (selfcompiled) on a SLES 11.0 machine.
It acts as master for several domains and as resolver for users in our network.
The machine is running as a VM on an ESX server.

trying to resolve www.microsoft.com or microsoft.com results in a 
"connection timed out; no servers could be reached"

all other domains (as far as I know) work fine.

-------------------------------
dig microsoft.com @localhost

; <<>> DiG 9.7.2-P3 <<>> microsoft.com @localhost
;; global options: +cmd
;; connection timed out; no servers could be reached


---------------------------------

but using +trace I'll get a result:

dig +trace microsoft.com @localhost

; <<>> DiG 9.7.2-P3 <<>> +trace microsoft.com @localhost
;; global options: +cmd
.                       454737  IN      NS      h.root-servers.net.
.                       454737  IN      NS      i.root-servers.net.
.                       454737  IN      NS      j.root-servers.net.
.                       454737  IN      NS      k.root-servers.net.
.                       454737  IN      NS      l.root-servers.net.
.                       454737  IN      NS      m.root-servers.net.
.                       454737  IN      NS      a.root-servers.net.
.                       454737  IN      NS      b.root-servers.net.
.                       454737  IN      NS      c.root-servers.net.
.                       454737  IN      NS      d.root-servers.net.
.                       454737  IN      NS      e.root-servers.net.
.                       454737  IN      NS      f.root-servers.net.
.                       454737  IN      NS      g.root-servers.net.
;; Received 260 bytes from 127.0.0.1#53(127.0.0.1) in 1 ms

com.                    172800  IN      NS      a.gtld-servers.net.
com.                    172800  IN      NS      b.gtld-servers.net.
com.                    172800  IN      NS      c.gtld-servers.net.
com.                    172800  IN      NS      d.gtld-servers.net.
com.                    172800  IN      NS      e.gtld-servers.net.
com.                    172800  IN      NS      f.gtld-servers.net.
com.                    172800  IN      NS      g.gtld-servers.net.
com.                    172800  IN      NS      h.gtld-servers.net.
com.                    172800  IN      NS      i.gtld-servers.net.
com.                    172800  IN      NS      j.gtld-servers.net.
com.                    172800  IN      NS      k.gtld-servers.net.
com.                    172800  IN      NS      l.gtld-servers.net.
com.                    172800  IN      NS      m.gtld-servers.net.
;; Received 503 bytes from 198.41.0.4#53(a.root-servers.net) in 42 ms

microsoft.com.          172800  IN      NS      ns3.msft.net.
microsoft.com.          172800  IN      NS      ns1.msft.net.
microsoft.com.          172800  IN      NS      ns5.msft.net.
microsoft.com.          172800  IN      NS      ns2.msft.net.
microsoft.com.          172800  IN      NS      ns4.msft.net.
;; Received 209 bytes from 192.54.112.30#53(h.gtld-servers.net) in 18 ms

microsoft.com.          3600    IN      A       207.46.232.182
microsoft.com.          3600    IN      A       207.46.197.32
;; Received 63 bytes from 65.55.37.62#53(ns1.msft.net) in 175 ms

----------------------------------------------------

I have duplicated this virtual machine while trying to find out whats going on and it did resolve 
then - but without traffic from our users.
But as soon as I try this on the real DNS server and it gets requests from users, 
microsoft.com won't resolve.

----------------------------------------------------

How can I debug this problem further?

I have experimented with "max-cache-size" but didn't help. 
How can I see how much memory bind uses for the cache at the moment?


Thanks a lot
 Thilo

-- 
Das Impressum der EUROIMMUN AG Deutschland finden Sie unter
www.euroimmun.de/impressum.htm