Windows XP name resolution question...

10 Oct 2006 9:53 PM

Michaelk

Hi everyone,

This is probably basic for all you network wizard :-)

Why does windows need the dot to resolve the name when the domainname
is empty?
(following the first label in the FQDN)

Check this example below:

C:\>nslookup dreambox
Server:   dns
Address: 192.168.0.1

Name:    dreambox
Address: 192.168.0.124

C:\>ping dreambox
Ping request could not find host dreambox. Please check the name and
try again.

C:\>ping dreambox.

Pinging dreambox [192.168.0.124] with 32 bytes of data:

Reply from 192.168.0.124: bytes=32 time=1ms TTL=64
Reply from 192.168.0.124: bytes=32 time=1ms TTL=64
Reply from 192.168.0.124: bytes=32 time=1ms TTL=64
Reply from 192.168.0.124: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.0.124:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 90ms, Average = 23ms

Client is DHCP
Node type = Hybrid
Both the "Primary Dns Suffix" and the "Connection-specific DNS Suffix"
are empty

My linux hosts do not have this problem...

I there a way to turn this (annoying) feature of? All hosts are on my
internal home network so I don't really need a domain name...

Any other hints or clues?

Thanks in advance

Michael

11 Oct 2006 2:32 PM

Peter R. Fletcher

Are you sure that you haven't named it with the dot? Ping works on a
"bare" name (and doesn't work if I add the dot) on my small XP
network.

Show quoteHide quote

On 10 Oct 2006 14:53:52 -0700, "Michaelk" <michael.kal***@gmail.com>
wrote:

>Hi everyone,
>
>This is probably basic for all you network wizard :-)
>
>Why does windows need the dot to resolve the name when the domainname
>is empty?
>(following the first label in the FQDN)
>
>Check this example below:
>
>C:\>nslookup dreambox
>Server:   dns
>Address: 192.168.0.1
>
>Name:    dreambox
>Address: 192.168.0.124
>
>C:\>ping dreambox
>Ping request could not find host dreambox. Please check the name and
>try again.
>
>C:\>ping dreambox.
>
>Pinging dreambox [192.168.0.124] with 32 bytes of data:
>
>Reply from 192.168.0.124: bytes=32 time=1ms TTL=64
>Reply from 192.168.0.124: bytes=32 time=1ms TTL=64
>Reply from 192.168.0.124: bytes=32 time=1ms TTL=64
>Reply from 192.168.0.124: bytes=32 time=1ms TTL=64
>
>Ping statistics for 192.168.0.124:
>    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>Approximate round trip times in milli-seconds:
>    Minimum = 1ms, Maximum = 90ms, Average = 23ms
>
>Client is DHCP
>Node type = Hybrid
>Both the "Primary Dns Suffix" and the "Connection-specific DNS Suffix"
>are empty
>
>My linux hosts do not have this problem...
>
>I there a way to turn this (annoying) feature of? All hosts are on my
>internal home network so I don't really need a domain name...
>
>Any other hints or clues?
>
>Thanks in advance
>
>Michael

Please respond to the Newsgroup, so that others may benefit from the exchange.
Peter R. Fletcher

11 Oct 2006 8:41 PM

Michaelk

Peter R. Fletcher skrev:

> Are you sure that you haven't named it with the dot? Ping works on a
> "bare" name (and doesn't work if I add the dot) on my small XP
> network.

Yes, I'm sure. This is how it looks on my linux box ( se below)

Note that I don't have the name "dreambox" in my hosts file, It's
beeing
resolved by the DNS on my linksys router.
(running Dnsmasq: http://thekelleys.org.uk/dnsmasq/doc.html)

$ nslookup dreambox
Server:         192.168.0.1
Address:        192.168.0.1#53

Name:   dreambox
Address: 192.168.0.124

$ ping -c 4 dreambox
PING dreambox (192.168.0.124) 56(84) bytes of data.
64 bytes from dreambox (192.168.0.124): icmp_seq=1 ttl=64 time=2.04 ms
64 bytes from dreambox (192.168.0.124): icmp_seq=2 ttl=64 time=1.93 ms
64 bytes from dreambox (192.168.0.124): icmp_seq=3 ttl=64 time=2.00 ms
64 bytes from dreambox (192.168.0.124): icmp_seq=4 ttl=64 time=1.96 ms

--- dreambox ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 1.932/1.988/2.049/0.062 ms

It's not a big problem but a bit annoying...because it affects all
other commands
i.e. telnet, ftp, ssh....

//Michael

12 Oct 2006 6:37 AM

Peter R. Fletcher

Show quote Hide quote

On 11 Oct 2006 13:41:23 -0700, "Michaelk" <michael.kal***@gmail.com>
wrote:

>Peter R. Fletcher skrev:
>> Are you sure that you haven't named it with the dot? Ping works on a
>> "bare" name (and doesn't work if I add the dot) on my small XP
>> network.
>
>Yes, I'm sure. This is how it looks on my linux box ( se below)
>
>Note that I don't have the name "dreambox" in my hosts file, It's
>beeing
>resolved by the DNS on my linksys router.
>(running Dnsmasq: http://thekelleys.org.uk/dnsmasq/doc.html)
>
>$ nslookup dreambox
>Server:         192.168.0.1
>Address:        192.168.0.1#53
>
>Name:   dreambox
>Address: 192.168.0.124
>
>$ ping -c 4 dreambox
>PING dreambox (192.168.0.124) 56(84) bytes of data.
>64 bytes from dreambox (192.168.0.124): icmp_seq=1 ttl=64 time=2.04 ms
>64 bytes from dreambox (192.168.0.124): icmp_seq=2 ttl=64 time=1.93 ms
>64 bytes from dreambox (192.168.0.124): icmp_seq=3 ttl=64 time=2.00 ms
>64 bytes from dreambox (192.168.0.124): icmp_seq=4 ttl=64 time=1.96 ms
>
>--- dreambox ping statistics ---
>4 packets transmitted, 4 received, 0% packet loss, time 3000ms
>rtt min/avg/max/mdev = 1.932/1.988/2.049/0.062 ms
>
>It's not a big problem but a bit annoying...because it affects all
>other commands
>i.e. telnet, ftp, ssh....
>
>//Michael

Could it be a quirk of your router? As noted, my all XP network,
hooked up to an old Netgear cable router, behaves as you (and I) would
expect. I don't think its an XP issue. I don't have anything in my
HOSTS files, either.

Please respond to the Newsgroup, so that others may benefit from the exchange.
Peter R. Fletcher

12 Oct 2006 9:15 AM

Michaelk

> Could it be a quirk of your router? As noted, my all XP network,

Could be...

But what strange to me is that windows resolves the name correctly
(nslookup dreambox) witout a dot but can't use it...

//Michael