Need extra dot when ping static host

[MJaat]

Hi,

We do not have FQDN's.

I have enabled dns proxy and added static host "testikuu".

dns proxy enable
ip host testikuu 192.168.16.10

When i ping from MSR then ok.

ping testikuu
Ping testikuu (192.168.16.10):....

The problem is when i ping from Windows 10 host.

ping testikuu
Ping request could not find host testikuu. Ple...

But when i ping from Windows 10 host with extra dot.

ping testikuu.
Pinging testikuu [192.168.16.10] with 32...

Is this how it should work?

HPE Comware Software, Version 7.1.064, Release 0605P13

[sdide]

Hi,

Probably.

I'm not sure exactly how windows implements its local resolver, but putting a "dot" at the end of a dns-name means its absolute. Not putting it there, means the name is relative, and the resolver will probably look for search-domains and add those to the relative label.
So my guess is, if your machine has lets say "somedomain.com" and "someotherdomain.com" as search domains, when you ping "testikuu" the resolver will ask for testikuu.somedomain.com and testikuu.someotherdomain.com and not find them.
But when you ping "testikuu." it will ask for "testikuu." and the dns proxy will answer.

You could try calling your test something common and test it. For example "www" instead of "testikuu".
Then from windows try ping'ing "www" and "www." Because now "www.somedomain.com" will probably exist.

Regards

[MJaat]

Hi,

Done and with same results:

Comware:

ip host www 192.168.16.10

ping www
Ping www (192.168.16.10): 56 data byte...

ping www.
ping: Unknown host.

Windows 10:

ping www
Ping request could not find host www. Plea...

ping www.

Pinging www [192.168.16.10] with 32...

[MJaat]

One permutation still.

Comware:

ip host wwe. 192.168.16.10

ping wwe
ping: Unknown host.

ping wwe.
Ping wwe. (192.168.16.10): 56 data by...

Windows 10:

ping wwe
Ping request could not find host wwe. Plea...

ping wwe.
Ping request could not find host wwe.. Ple...

ping wwe..
Ping request could not find host wwe... Plea...

[Dunky]

It looks to me as though you are trying to use the switch as a DNS server.

The ip host is designed to enable you to refer to other devices by name FROM THE SWITCH, instead of using their ip address. ie ping etc.

Your Windows 10 cleint probably has a domain suffix appended hence the switch cannot resolve it.  Not saying it will work, but have you tried defining the domain on the switch so that it matches your windows client suffix?