big troubles with DNS

[Alex]

Hi

i've got some very big troubles with Windows 2003 DNS Server (all patches
are installed)! this machines have 10 IPs... maybe my problems are releated
to this...

the troubles are:

1. normal NSlookup works, ping too - BUT sometimes it don't work! this is a
sporadicaly problem with some domains. today i saw - i cannot resolve the MX
records of "CliffordChance.com". a normal DNS query to this domain works and
results in the following:

Server: dns1.internaldomain.local
Address: 10.1.1.10

Non-authoritative answer:
Name: CliffordChance.com
Address: 194.133.109.2

2. if i open the nslookup tool from DNS tool - i got a error - but this is
not the default IP of this machine... :
*** Can't find server name for address 10.1.1.9: No response from server
Default Server: UnKnown
Address: 10.1.1.9

3. if i try the test querys in DNS Manager - i got everytime "fail". i have
no idea...


Gruss
Alex

 

[Guest]

We are experiencing a similar problem. We are using Windows 2003 AD Integrated DNS servers internally. DNS is configured to use root hints (not forwarding) & goes out through a Cisco Firewall. When using NSLookup, domain names are all resolving OK. Nevertheless, when setting the type=MX, these same domains fail to resolve, actually intermittently. Looks like a bug in Win2003 possibly using Cisco firewall. Still researching this problem, will keep you posted. -Martin

 

[Matt Hickman]

Server: dns1.internaldomain.local
Address: 10.1.1.10

Non-authoritative answer:
Name: CliffordChance.com
Address: 194.133.109.2

2. if i open the nslookup tool from DNS tool - i got a error - but this is
not the default IP of this machine... :
*** Can't find server name for address 10.1.1.9: No response from server
Default Server: UnKnown
Address: 10.1.1.9

What, if anything, is at address 10.1.1.9?

Is Address 10.1.1.9 on the list of DNS server configured for
the computer you are using to run the DNS queries?

--
Matt Hickman
'I work for the company too,' the Doctor growled, 'but I
didn't sell myself to it body and soul.'
- Robert A. Heinlein (1907-1988)
_Red Planet_ c. 1949

 

[Kevin D. Goodknecht [MVP]]

In

We are experiencing a similar problem. We are using Windows 2003 AD
Integrated DNS servers internally. DNS is configured to use root
hints (not forwarding) & goes out through a Cisco Firewall. When
using NSLookup, domain names are all resolving OK. Nevertheless,
when setting the type=MX, these same domains fail to resolve,
actually intermittently. Looks like a bug in Win2003 possibly using
Cisco firewall. Still researching this problem, will keep you
posted. -Martin

It is not a bug per se the Cisco firewall doesn't support EDNS0 (UDP packets
over 512 bytes)
828731 - An External DNS Query May Cause an Error Message in Windows Server
2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;828731