nixCraft

I have windows 2000 and 2003 server. While 2000 server DNS is working fine my windows 2003 server is not working. It works for some client and it does not work for some clients at all

What command do you use for Windows server troubleshooting DNS problem?

I use nslookup command which is more than sufficient to solve the problem. However you can also try out following URL for more ease of use:

http://www.samspade.org/
http://www.dnsstuff.com/
http://www.dnsreport.com/
http://www.analogx.com/contents/dnsdig.htm

If you have any specify error reply back

__________________
Rocky Jr.
You may have my body & soul, but you will never touch my pride!

If you have knowledge, let others light their candles at it.

Certified to work on HP-UX / Sun Solaris / RedHat

What OS are the clients using?

All clients are uwing Windows XP or 2000. No UNIX box here. How do i use nslookup solve the problem? All it does is give back ip of server

Let me try out those urls, thanks

I was thinking more along the lines of Win98 boxes having trouble with 2003.
Are there any errors in the DNS event logs?
What DNS setup is it? AD integrated or Primary, Secondary setup?

Hi Beresford!

To my luck we have upgraded all windows 98 system to windows xp. As Microsoft send us letter informing that they will not provide any update and support.

Ok the problem is windows Server 2003 cannot resolve addresses that windows 2000 and XP box can. This is wired problem. DNS is still on 2000 server (which not upgraded to 2003 due to cost cutting issue … LOL). Do I need to apply any patch to window 2003 w/o dns this system is useless since last couple of days.

Also above urls are not good for me as Cisco pix blocks incoming request to everything exepct for our branch offices.

Please someone help out.

Disable EDNS0 request mechanisms used by windows 2003 server. Go to Windows Server 2003 Support Tools folder and type the command:
See article for more info:
http://www.microsoft.com/technet/its...fund_ch09.mspx

Let us know how you get along with Tom's suggestion.

I just wanted to double check, so it's only your 2003 server having trouble resolving names?
Can it resolve internal names, external names or neither? What DNS server is it pointing to? Your internal 2000 server?

I've never had a problem with 2003 using 2000 DNS but most of the sites I look after aren't too complicated.

Also, here is an URL on how to use nslookup
http://www.windowsnetworking.com/art...diagnosis.html

Thanks guys; I did lots of thing including toms suggestion it is working now.