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

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

"Alex" <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
>
> 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

In news:F14F84C4-2946-4AC7-BAAC-(E-Mail Removed),
Martin <(E-Mail Removed)> posted a question
Then Kevin replied below:
> 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...b;en-us;828731

--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
============================
--
When responding to posts, please "Reply to Group" via your
newsreader so that others may learn and benefit from your issue.
To respond directly to me remove the nospam. from my email.
==========================================
http://www.lonestaramerica.com/
==========================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
==========================================
Keep a back up of your OE settings and folders with
OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
==========================================