sounds like you have a network redirector working within your org..
Main Topics
Browse All TopicsI have a windows 2003 server running active directory and is also a DNS server. My domain name is domain.com. Whenever I do a lookup (for example nslookup or ping) for an unknown host it always returns the same IP address: 67.15.97.37
For example if I say:
Ping asdhasgdjkh
I get:
Pinging domain.com [ 67.15.97.37] with 32 bytes of data
reply from.... time 70ms ttyl118
etc
If I add a trailing dot at the end of the nonsense host then it fails appropriately. This is messing me up because I'm trying to do pings to check for live hosts and if the host doesn't exist the ping still succeeds. How I can I fix this?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Where are you performing your pings or NSLookups:
If on a client, look on that client's HOST file.
Also see if all your client machines produce the same results.
DNS troubleshooting made easy might help you:
http://www.experts-exchang
Nevermind, I figured it out. Apparantly dns queries are first automatically sent using the domain suffix, ie. nslookup asdasdasd is checked first as asdasdasd.domail.local
Since our local dns server didn't have a record for that it went on to check the external dns server, which redirected to our www nameserver which DID have a * entry for domain.lccal and was thus returning the IP address of our www server.
What I still don't quite understand is how then does any other REAL domain get resolved correctly? If I lookup www.yahoo.com it must first go and check www.yahoo.com.domain.local
yes, the dns query does include the originating domain, but it is stripped out if it is found on that domains DNS server, if not, it then tries to find it by forwarding it onto the next forwarder in the chain for resolution, while maintaining the domain suffix.
So blabla.domain.com.yahoo.co
and blablabla will try to resolve locally, using the current domain.
If your query resolved externally, you may be using a generic name, as .local are not normally cached externally via ISP's.
Also, you can change your default query domain name within nslookup, use set domain=domain.com.
Again, this article explains the steps a DNS query takes, from the client to the top-level domain controller.
http://www.experts-exchang
Business Accounts
Answer for Membership
by: LingerLongerPosted on 2009-11-04 at 14:17:58ID: 25744627
Do you have a * entry in your DNS for that IP?