Re: A problem with "hosts" file: hostnames with dots are not being resolved
- From: "Ace Fekay [MVP]" <PleaseAskMe@xxxxxxxxxxxxxx>
- Date: Wed, 31 Jan 2007 00:08:03 -0500
In news:1169790243.133883.140450@xxxxxxxxxxxxxxxxxxxxxxxxxxxx,
Yarik <yarik@xxxxxxxxxx> stated, which I commented on below:
Did you eliminate the possibitlity of a virus (the Qhosts virus), or
spyware that may have hijacked thefile?
No. I would appreciate any pointer on how to do that.
Not to sound facetious, but a qualified antivirus program can do this. You
can physically check the registry under H+HKLM\CCS\services\TCP\database
path. That should point to system32\drivers\etc\
When you do an ipconfig /flushdns, then an ipconfig displaydns, does
the entries you put in show up with thedots?
Yes.
Right after that, try to ping both
entries, and post your results.
Below is what I get (just in case, I restarted DNS Client service
right before the experiment).
NOTE: In our intranet, failure to resolve a host/domain name has
some... peculiarity. It never happens. :-) I don't know why, but our
IT folks use OpenDNS service: whenever their DNS server can't resolve
a host/domain name it returns IP of their OpenDNS's website,
208.67.219.41. I guess, the goal of this trick (IMHO, a dirty one) is
to make a misdirected browser show a page advertizing OpenDNS and full
of Google ads. In any case, on the screenshots below, ping's failure
to resolve a domain name actually looks like successful discovery of
208.67.219.41 address.
================================= Flush DNS Cache
P:\Projects>ipconfig /flushdns
Windows 2000 IP Configuration
Successfully flushed the DNS Resolver Cache.
================================= Display DNS Cache
P:\Projects>ipconfig /displaydns
Windows 2000 IP Configuration
localhost.
------------------------------------------------------
Record Name . . . . . : localhost
Record Type . . . . . : 1
Time To Live . . . . : 31525413
Data Length . . . . . : 4
Section . . . . . . . : Answer
A (Host) Record . . . :
127.0.0.1
zzyzx.
------------------------------------------------------
Record Name . . . . . : zzyzx
Record Type . . . . . : 1
Time To Live . . . . : 31525413
Data Length . . . . . : 4
Section . . . . . . . : Answer
A (Host) Record . . . :
192.168.1.22
1.0.0.127.in-addr.arpa.
------------------------------------------------------
Record Name . . . . . : 1.0.0.127.in-addr.arpa
Record Type . . . . . : 12
Time To Live . . . . : 31525413
Data Length . . . . . : 4
Section . . . . . . . : Answer
PTR Record . . . . . :
localhost
zzyzx.com.
------------------------------------------------------
Record Name . . . . . : zzyzx.com
Record Type . . . . . : 1
Time To Live . . . . : 31525413
Data Length . . . . . : 4
Section . . . . . . . : Answer
A (Host) Record . . . :
192.168.1.22
22.1.168.192.in-addr.arpa.
------------------------------------------------------
Record Name . . . . . : 22.1.168.192.in-addr.arpa
Record Type . . . . . : 12
Time To Live . . . . : 31525413
Data Length . . . . . : 4
Section . . . . . . . : Answer
PTR Record . . . . . :
zzyzx.com
Record Name . . . . . : 22.1.168.192.in-addr.arpa
Record Type . . . . . : 12
Time To Live . . . . : 31525413
Data Length . . . . . : 4
Section . . . . . . . : Answer
PTR Record . . . . . :
zzyzx
================== Ping hostname WITHOUT a dot - succeeds
P:\Projects>ping zzyzx
Pinging zzyzx [192.168.1.22] with 32 bytes of data:
Reply from 192.168.1.22: bytes=32 time<10ms TTL=128
Reply from 192.168.1.22: bytes=32 time<10ms TTL=128
Reply from 192.168.1.22: bytes=32 time<10ms TTL=128
Reply from 192.168.1.22: bytes=32 time<10ms TTL=128
Ping statistics for 192.168.1.22:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
================== Ping hostname WITHOUT a dot - fails
P:\Projects>ping zzyzx.com
Pinging zzyzx.com [208.67.219.41] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 208.67.219.41:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
That is sad that OpenDNS does that. Kind of crazy if you ask me.
But anyway, I know youmeant ping hostname with a dot fails (you said
without).
Is the DHCP Client service running? That is actually a required service for
resolution whether the machine is configured for DHCP or is statically
configured (like a server).
Alsom, you have two reverse entries for 192.168.1.22. There should only be
ONE. Choose one of them.
Curious, when you ping:
ping -a 192.168.1.22
what happens?
Ace
.
- References:
- Prev by Date: Windows 2000 DNS and Exchange Server 2003 problems
- Next by Date: Re: Windows 2000 DNS and Exchange Server 2003 problems
- Previous by thread: Re: A problem with "hosts" file: hostnames with dots are not being resolved
- Next by thread: Does this mean reverse DNS was not setup?
- Index(es):
Relevant Pages
|
