ping hostname from source interface not working

[Filip Grulis]

Hi,

extended ping command from source interface not working when try to ping hostname without DNS suffix or with domain.local suffix.

working fine when trying to ping for example .com domain. 

We are using Cisco C1111-4P with ios-XE, Version 17.3.4a, RELEASE SOFTWARE (fc3)

before we used old Cisco 871 with normal ios and there was no problem with that.

we have servers hosted in cloud and local branches are connected with servers troght IPsec and when i need to troubleshoot DNS it not possible as this command not working. Used to in past on old cisco without any problem.

can anyone help? or any workaround how to verify DNS trough source interface???

see commands output: 

ROUTER#ping 192.168.100.144 source vlan 1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.100.144, timeout is 2 seconds:
Packet sent with a source address of 10.21.26.254
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 40/40/44 ms

ROUTER#ping server-dc source vlan 1

% Invalid input detected at '^' marker.

ROUTER#ping server-dc.company.local source vlan 1
^
% Invalid input detected at '^' marker.

ROUTER#ping google.com source vlan 1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 142.250.75.14, timeout is 2 seconds:
Packet sent with a source address of 10.21.26.254
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 24/26/28 ms

ROUTER#ping server-dc.company.local ?
<cr> <cr>

ROUTER#ping google.com ?
Extended-data specify extended data pattern
data specify data pattern
df-bit enable do not fragment bit in IP header
dscp Specify DSCP value in ASCII/Numeric
egress Force egress interface bypassing routing
ingress LAN source interface for Ingress
repeat specify repeat count
size specify datagram size
source specify source address or name
timeout specify timeout interval
tos specify type of service value
validate validate reply data
<cr> <cr>

[balaji.bandi]

I am running IOS XE 17.3.3 and 3.5 i did  see this issue.

#ping mydomain.local ?   (because of the Local its not recognising at all) - also taking long time to get ? output
<cr> <cr>

#ping mydomain.local
% Unrecognized host or address, or protocol not running.

[Filip Grulis]

so is this a known issue? is there any workaround for that or some plan to fix it?

its little bit frustrated for me as I am not able troubleshoot DNS problems on local branch....

We have moved from standard ios on old cisco routers to new routers with iosxe and there is many other things which are not working and worked well on standard ios on old routers... 

[balaji.bandi]

May be ping command become more intelligent not like before ....expecting FQDN somehow - never observed, since we do not use a Network device to troubleshoot, you can ping an IP that is good enough from network devices.

if this is must, then you may need to have .net DNS entry for you to resolve it correctly its just A and subdomain entry.