DNS Problem, should be simple to fix

[Lee M]

Hello All,

I am hoping this will be a simple problem to fix.

I have only noticed this recently but it is causing a problem to users now.

This is what happens when I ping google from my Domain Controller (only one
on the network and it is configured as the DNS server for all the clients
and it points to itself for DNS)


Pinging www.google.akadns.net [66.102.11.99] with 32 bytes of data:

Reply from 66.102.11.99: bytes=32 time=47ms TTL=56


So that is fine, but when I do a NSLOOKUP on a client or from the server
itself I get this response


Default Server: dcmachinename.mysubdomain.mydomain.com
Address: 192.168.103.1

www.google.com

Server: dcmachinename.mysubdomain.mydomain.com

Address: 192.168.103.1

Non-authoritative answer:
Name: www.google.com.mydomain.com
Address: xxx.xxx.xxx.xxx


It is adding my domainname on to the end of google.com and giving the IP
address of the webserver that handles my domains website (I do not own the
domain name that I have used to create my domain)

Any ideas ??

 

[Kevin Goodknecht [MVP]]

In Lee M <[email protected]> posted a question
Then Kevin replied below:
: Hello All,
:
: I am hoping this will be a simple problem to fix.
:
: I have only noticed this recently but it is causing a problem to
: users now.
:
: This is what happens when I ping google from my Domain Controller
: (only one on the network and it is configured as the DNS server for
: all the clients and it points to itself for DNS)
:
:
: Pinging www.google.akadns.net [66.102.11.99] with 32 bytes of data:
:
: Reply from 66.102.11.99: bytes=32 time=47ms TTL=56
:
:
: So that is fine, but when I do a NSLOOKUP on a client or from the
: server itself I get this response
:
:
: Default Server: dcmachinename.mysubdomain.mydomain.com
: Address: 192.168.103.1
:
:: www.google.com
: Server: dcmachinename.mysubdomain.mydomain.com
:
: Address: 192.168.103.1
:
: Non-authoritative answer:
: Name: www.google.com.mydomain.com
: Address: xxx.xxx.xxx.xxx
:
:
: It is adding my domainname on to the end of google.com and giving the
: IP address of the webserver that handles my domains website (I do not
: own the domain name that I have used to create my domain)
:
: Any ideas ??

So you do not own my domain.com?
But mysubdomain.mydomain.com is the name of your internal domain?
When you join a machine to a domain it makes the Primary DNS suffix of the
machine the name of the domain you are making it a member of. Then in TCP/IP
properties on the DNS tab the default setting is to "append primary and
connection specific suffixes" and "append parent suffixes of the primary DNS
suffix" to all DNS queries. Your primary DNS suffix should be
mysubdomain.mydomain.com and the parent will be mydomain.com. Since you do
not own the parent name you need to uncheck "Append parent suffixes of the
primary DNS suffix" Since you don't own it and don't have a local zone for
the name if this name gets appended it is going to give you serious network
issues.
The reason you get back what you are getting is because there is most likely
a wildcard entry in the zone for mydomain.com. So just about every external
query you do will get back this wildcard record.

 

[Alan Wood [MSFT]]

Hi Lee,
This is how NSLOOKUP works and has nothing to do with when you ping or
access it by systems by other means. When using NSLOOKUP make sure you end
the query with a trailing "."
Example: nslookup www.google.com.


Thank you,

Alan Wood[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.