DNS doesn't work -- domain names cannot be parsed!

  • Thread starter Thread starter VVIPI
  • Start date Start date
V

VVIPI

I create a new Zone, Standard primary type, Forward Lookup, with a name
"testmydns.com". And under this zone, create a new host named "www" and its
IP is 192.168.1.101 (the address of the Server to be configed).

What I expected is that if I "ping www.testmydns.com" from the server, I
should see the following results:


Pinging www.testmydns.com [192.168.1.101] with 32 bytes of data:

Reply from 192.168.1.101: bytes=32 time<10ms TTL=128
....


However, what I see is "Unknown host www.".

My server is not a domain controller, it's in a workgroup. I upgrade the
server to a domain controller, this DNS setting still does not work.

Why?

Thanks for help!
 
VVIPI said:
I create a new Zone, Standard primary type, Forward Lookup, with a name
"testmydns.com". And under this zone, create a new host named "www" and its
IP is 192.168.1.101 (the address of the Server to be configed).

What I expected is that if I "ping www.testmydns.com" from the server, I
should see the following results:

Pinging www.testmydns.com [192.168.1.101] with 32 bytes of data:
Reply from 192.168.1.101: bytes=32 time<10ms TTL=128
...
However, what I see is "Unknown host www.".
Click to expand...

Do you really see JUST "www." without the testmydns.com AND did you
really type all of that in the Ping and not JUST "ping www"???

If you were using the short form (implied by the response) one would expect
the above if you machine did NOT have the SAME domain name set in the
System Control panel (nor in the NIC's additional suffix settings.)
My server is not a domain controller, it's in a workgroup. I upgrade the
server to a domain controller, this DNS setting still does not work.
Click to expand...

Otherwise, it is likely because you don't have the CLIENT (NIC) pointed
at the internal DNS and ONLY at the internal DNS.
 
Try resolving as "www.testmydns.com". If that works you
need to modify the IP setings on the client to append the
DNS suffic "testmydns.com". Adding the DNS suffix you
just created to the DNS suffix search list on the client
should resolve this issue.

mac
-----Original Message-----
VVIPI said:
I create a new Zone, Standard primary type, Forward Lookup, with a name
"testmydns.com". And under this zone, create a new
Click to expand...
host named "www" and
its
IP is 192.168.1.101 (the address of the Server to be configed).

What I expected is that if I "ping www.testmydns.com" from the server, I
should see the following results:

Pinging www.testmydns.com [192.168.1.101] with 32 bytes of data:
Reply from 192.168.1.101: bytes=32 time<10ms TTL=128
...
However, what I see is "Unknown host www.".
Click to expand...

Do you really see JUST "www." without the testmydns.com AND did you
really type all of that in the Ping and not JUST "ping www"???

If you were using the short form (implied by the response) one would expect
the above if you machine did NOT have the SAME domain name set in the
System Control panel (nor in the NIC's additional suffix settings.)
My server is not a domain controller, it's in a workgroup. I upgrade the
server to a domain controller, this DNS setting still
Click to expand...
does not work.

Otherwise, it is likely because you don't have the CLIENT (NIC) pointed
at the internal DNS and ONLY at the internal DNS.


--
Herb Martin
Why?

Thanks for help!
Click to expand...


.
Click to expand...
 
You need to add a DNS suffix for testmydns.com. Once you add this, the DNS resolver will appending it to the end of you
request for www, resulting in a DNS query for www.testmydns.com.

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