Again - running a Kubuntu desktop at work. I'll lay out a log of
what's happening...
<ctpaterson@company-220> nslookup company-231
Server: 192.168.0.8
Address: 192.168.0.8#53
Name: company-231.companysys.local
Address: 192.168.1.119
<ctpaterson@company-220> ping company-231
PING company-231.companysys.local (192.168.1.119) 56(84) bytes of data.
64 bytes from company-231.companysys.local (192.168.1.119): icmp_seq=1
ttl=64 time=0.151 ms
64 bytes from company-231.companysys.local (192.168.1.119): icmp_seq=2
ttl=64 time=0.160 ms
64 bytes from company-231.companysys.local (192.168.1.119): icmp_seq=3
ttl=64 time=0.181 ms
--- company-231.companysys.local ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.151/0.164/0.181/0.012 ms
<ctpaterson@company-220> nslookup company-231.companysys.local
Server: 192.168.0.8
Address: 192.168.0.8#53
Name: company-231.companysys.local
Address: 192.168.1.119
<ctpaterson@company-220> ping company-231.companysys.local
ping: unknown host company-231.companysys.local
<ctpaterson@company-220>
So my problem, essentially, is that my Linux machine can not seem to
ping a colleague's machine if I include the domain. I asked another
colleague with a Windows box to try pinging
"company-231.companysys.local" and it was able to do so, reporting the
correct IP.
The problem is not unique to trying to reach company-231; on my Linux
box, I can not ping any of the machines I have tried in my company's
LAN if I include ".companysys.local".
Can anyone suggest likely causes? Places I could look? Googling
keeps coming back with ways to setup bind. ;>
Thanks.
--
"My country is the world, and my religion is to do good."
-- Thomas Paine