[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Why is FQDN not found?

On 07/27/2012 10:06 AM, Kent West wrote:

On 07/27/2012 09:57 AM, Kelly Clowers wrote:

On Fri, Jul 27, 2012 at 7:45 AM, Kent West<westk@acu.edu>  wrote:
Why can I ping the hostname, but not the fully-qualified domain name of a 
box?


westk@westek:~$ ping k1000
PING k1000.acu.local (150.252.149.1) 56(84) bytes of data.
64 bytes from 150.252.149.1: icmp_req=1 ttl=62 time=0.128 ms
^C64 bytes from 150.252.149.1: icmp_req=2 ttl=62 time=0.138 ms

--- k1000.acu.local ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 5002ms
rtt min/avg/max/mdev = 0.128/0.133/0.138/0.005 ms


westk@westek:~$ ping k1000.acu.local
ping: unknown host k1000.acu.local


westk@westek:~$ cat /etc/resolv.conf
# Generated by NetworkManager
domain acu.local
search acu.local
nameserver 150.252.134.8
nameserver 150.252.134.159
nameserver 150.252.228.8
nameserver 150.252.135.4


westk@westek:~$ nslookup k1000
Server:         150.252.134.8
Address:        150.252.134.8#53

Name:   k1000.acu.local
Address: 150.252.149.1

westk@westek:~$ nslookup k1000.acu.local
Server:         150.252.134.8
Address:        150.252.134.8#53

Name:   k1000.acu.local
Address: 150.252.149.1
I googled for this problem and found instructions to change 1 to 0 in the 
/etc/default/avahi-daemon file (after which I did a "sudo
/etc/init.d/avahi-daemon restart" command), but that didn't solve the
problem (so I put the /etc/default/avahi-daemon file back to the way it
was).

I have a MacBook running an up-to-date OS/X, and it can ping both the
hostname and the FQDN (and it's resolv.conf file looks pretty much the same 
as the above), so it seems to be a problem in this Debian box (westek).

Odd. What does your routing table look like ("ip route" or "route")?

I don't see why it should matter but have you tried "ping
k1000.acu.local." (trailing dot)



westk@westek:~$ ping k1000.acu.local.
ping: unknown host k1000.acu.local.

westk@westek:~$ ip route
default via 150.252.16.1 dev eth0  proto static
150.252.16.0/21 dev eth0  proto kernel  scope link  src 150.252.17.3

westk@westek:~$ sudo route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface default 150.252.16.1 0.0.0.0 UG 0 0 0 eth0 150.252.16.0 * 255.255.248.0 U 0 0 0 eth0 


Oh, and are you running nscd (name server cache daemon) or similar on
the box that cannot ping?
Just throwing stuff out there.



westk@westek:~$ ps ax | grep nscd
20075 pts/2 S+ 0:00 grep nscd


I'm not sure what would similar. So do I need to "aptitude install nscd"?




westk@westek:~$ sudo aptitude install nscd
The following NEW packages will be installed:
  nscd
0 packages upgraded, 1 newly installed, 0 to remove and 104 not upgraded.
Need to get 211 kB of archives. After unpacking 348 kB will be used.
Get: 1 http://ftp.us.debian.org/debian/ unstable/main nscd amd64 2.13-35 [211 kB] 
Fetched 211 kB in 3s (69.9 kB/s)
Selecting previously unselected package nscd.
(Reading database ... 228989 files and directories currently installed.)
Unpacking nscd (from .../nscd_2.13-35_amd64.deb) ...
Processing triggers for man-db ...
Setting up nscd (2.13-35) ...
[ ok ] Starting Name Service Cache Daemon: nscd.

westk@westek:~$ ping k1000.acu.local
ping: unknown host k1000.acu.local


--
Kent West<*)))><
http://kentwest.blogspot.com
Praise Yah! \o/
Reply to: