We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you a podcast all about Citrix Workspace, moving to the cloud, and analytics & intelligence. Episode 2 coming soon!Listen Now

x

Windows 2000 Server DNS Issue

nauman_ahmed
nauman_ahmed asked
on
Medium Priority
184 Views
Last Modified: 2010-04-13
Hi,

I have a Windows 2000 Server with no AD installed. Time to time, the nslookup start saying "can not find server name for address X.X.X.X. This problem goes away as soon as the server is restarted. Please advise.

Thanks,
Nauman.
Comment
Watch Question

Kevin HaysIT Analyst
CERTIFIED EXPERT

Commented:
Sounds like an issue with a reverse lookup zone in the DNS server.  I would look into your DNS servers settings and check the reverse lookup zone records.  Might just be a issue of issuing ipconfig /flushdns.

Kevin

Commented:
Does the problem happen only with nslookup? Are you able to actually connect to remote computers via DNS?
By the way is your machine a DNS server?

Author

Commented:
I can connect to the server remotely from any other machine. The server is not running any DNS server and the nslookup issue on the server itself: it fails to resolve the TCP servers added in TCP/IP settings and hence doing an nslookup for any domain from the server fails. I tried ipconfig /flushdns but it did not work. The problem goes away as soon as the server is restarted.

--Nauman

Commented:
The problem you're describing is indeed odd because nslookup has its own implementation of the DNS protocol (it does not use the gethostbyname() system call). The fact that two completely unrelated implementations of DNS makes thing a bit weird.
Let try another approach: When it happens next, try nslookuping using a different DNS server. Use this command:
nslookup www.google.com 192.9.9.3
Does this work?
Kevin HaysIT Analyst
CERTIFIED EXPERT

Commented:
Have you looked in the event logs to see if you are getting any errors?  When the problem goes away when you reboot is very odd.
Steve KnightIT Consultancy
CERTIFIED EXPERT

Commented:
As I'm sure you know nslookup reports an error if it can't reverse lookup the address of the dns server specified in it's tcpip properties.  It sounds simply like a comms issue, i.e. it can't comunicate with the dns servers you have defined -- are these are the ISP?

do as suggested above or

nslookup
server 158.43.128.1
www.yahoo.com.  (inc. the last period)

I would also suggest just some simple PINGs of the DNS servers you are using by IP address when it isn't working --in fact at that point can you PING anything on the internet (e.g. the above address I gave). Perhaps you lose the default gateway for some reason which is why you can get to the server from your other machines still?

Also might be worth checking the DNS client service and others haven't failed (and check the server event logs as suggested already)

Steve

Author

Commented:
It is still happening. I think I may need to reinstall Windows. Thanks for your inputs.

--Nauman.
Steve KnightIT Consultancy
CERTIFIED EXPERT

Commented:
Does the server have multiple network cards at all?  If so can you supply us output of ipconfig /all.  Did the above nslookup commands work or not when the comms had gone down btw?

Author

Commented:
The server has two network cards: one has local IP and one has WAN IP. None of the nslookup command work in this case. Nothing is in the eventlog. This server has SMTP service installed and when nslookup is failed, none of the e-mails are delivered. I am installing a local DNS server to see if it solves the issue.

--Nauman.
IT Consultancy
CERTIFIED EXPERT
Commented:
It may be down to default gateways.... do you have a default gateway defined on both NIC's?  If so try removing the one from your internal network, there should only ever be one.... that is why I requested the ipconfig /all to see but feel free to check yourself.

If so there is a function called dead gateway detection in Windows whereby if the default gateway becomes unavailable for some reason it will move onto a different default gateway and will not go back unless the other one fails.  This functionality can be turned off by a registry tweak if needed but still there should only be one DG -- use static routes for other internal subnets if needed, i.e.

route -p add 10.0.0.0 mask 255.0.0.0 10.0.0.1

to route all 10.x.x.x traffic to an internal router 10.0.0.1 which goes off to your other subnets.

Steve

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Steve KnightIT Consultancy
CERTIFIED EXPERT

Commented:

Author

Commented:
Thanks for the reply Steve. For one of the NIC, DHCP was enabled, I tried giving it a static IP. Lets see if it solves the issue.

Thanks,
Nauman.
Steve KnightIT Consultancy
CERTIFIED EXPERT

Commented:
Wow that was a long time ago!

Good luck!

Steve

Author

Commented:
yeah I know its been a long time :) We have not faced a lot of issue with the server since then...and I was not logging on to EE because of work...so yeah, lets see now :)

--Nauman.
Steve KnightIT Consultancy
CERTIFIED EXPERT

Commented:
I would like to see the original questioner come back, i think I gave a logical answer to why this may happen but it may or not be correct in this case of course.
Steve KnightIT Consultancy
CERTIFIED EXPERT

Commented:
Thanks for selecting my answer.... was that the issues in the end?
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.