Problem DNS NSLookup

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

we are using a Windows 2003 DC with installed DNS-Server. Our company Domain is "local.mycompany.de" and the webserver Domain is "mycompany.de". When i check a host of our network with nslookup it works fine, but when i check a webaddress for example "www.google.de" i receive the answer "www.google.de.mycompany.de" and the IP of our webserver. So where is the problem.

Thanks! Christian
 
In
Christian S. said:
Hi,

we are using a Windows 2003 DC with installed DNS-Server. Our company
Domain is "local.mycompany.de" and the webserver Domain is
"mycompany.de". When i check a host of our network with nslookup it
works fine, but when i check a webaddress for example "www.google.de"
i receive the answer "www.google.de.mycompany.de" and the IP of our
webserver. So where is the problem.

Thanks! Christian
Click to expand...

This sounds like there is a wildcard record in the mycompany.de zone and you
have mycompany.de in your search list on the DNS tab.
When using nslookup you need to add a trailing "." to queries, do a lookup
for www.google.de. to see if that stops this. Unless you have local hosts
that need to resolve in the mycompany.de domain and you have a forward
lookup zone for that domain you should remove the domain from you search
order.
 
When using NSLOOKUP it will append your primary DNS suffix to the end of the query. In this case it appears that your web
domain has a wildcard entry for your website. So any queries going to this domain will result in an answer that points to your
website. So when you querid for www.google.de the dns suffix mydomain.de was appended making the query
"www.google.de.mydomain.de.". To prevent NSLOOKUP from doing this, add a trailing "." period to the end of the query. For
instance, make the query "www.google.de." and it should resolve correctly.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.
 
Back
Top