Re: Why is FQDN not found?
On Fri, Jul 27, 2012 at 10: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).
Although you're using "acu.local" as a domain, I suspect that it has
the same problem as ".local" and clashes with avahi. Do you have any
"mdns" entries on the "hosts" line of "/etc/resolv.conf"?
(I wouldn't trust what OS X has in "/etc" because it generally doesn't
use these files.)
Reply to: