yenjungvoy
asked on
DNS problem - internal random host names resolve to our external website address
Here is the issue: we have our internal domain as local.company.com
Our external domain is company.com
Netbios domain name is "company"
we use wildcard in our A record at Netsol:
@.company.com (None) 7200 ourwebsiteip
*.company.com (All other) 7200 ourwebsiteip
All internal severs running Win2003 SP2.
Problem is when we try to ping any random host (non FDQN), it resolves to our website IP:
so if we do "ping kjhkjhkjh" we would get reply back from our website address.
Internally, we have two DNS servers. Both list themselves as primary, and each other as secondary. No external DNS servers listed in TCP/IP properties. When running nslookup with -d2 option, I can see it tries to resolve to kjhkjhkjh.local.company.co m first, then if it doesnt exist, it tries kjhkjhkjh.company.com and that's where it returns our web site address. How can we stop it from going out and returning our website address to every invalid hostname request (without removing wildcard from our domain name at Netsol)?
Our external domain is company.com
Netbios domain name is "company"
we use wildcard in our A record at Netsol:
@.company.com (None) 7200 ourwebsiteip
*.company.com (All other) 7200 ourwebsiteip
All internal severs running Win2003 SP2.
Problem is when we try to ping any random host (non FDQN), it resolves to our website IP:
so if we do "ping kjhkjhkjh" we would get reply back from our website address.
Internally, we have two DNS servers. Both list themselves as primary, and each other as secondary. No external DNS servers listed in TCP/IP properties. When running nslookup with -d2 option, I can see it tries to resolve to kjhkjhkjh.local.company.co
Do you really need "company.com" in the DNS Suffix Search List? Removing it would stop it.
For the latest service packs you should only find that this problem exhibits in NsLookup. This behaviour for the DNS Client can be controlled by changing the "AppendToMultiLabelName" Registry value.
See this blog from MS for details of the registry settings and policy settings for this.
http://blogs.technet.com/networking/archive/2009/04/16/dns-client-name-resolution-behavior-in-windows-vista-vs-windows-xp.aspx
Chris
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Create company.com on internal DNS server and create the necessary (external) records in that zone.