Home / ubuntu / Questions / 144636
Accepted
nelaaro
Asked: 2012-06-01 07:02:15 +0800 CST

Why do none of my local servers resolve?

  • 772

When I try to ping or browse using a web browser certain domains names that we host on our local network, it does not work. Yet, dig and nslookup correctly return their details. What do I need to do to fix this?

The DNS server and DHCP server at our local network work fine on the Windows clients.

$ ping ns1.domain.local
ping: unknown host ns1.domain.local
aaron@aaron-laptop:~
$ nslookup ns1.domain.local
Server:     127.0.0.1
Address:    127.0.0.1#53

Name:    ns1.domain.local
Address: 172.16.0.254

$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.0.1
search domain.local

$ nm-tool

NetworkManager Tool

State: connected (global)

- Device: eth0  [Wired connection 1] -------------------------------------------

  IPv4 Settings:
    Address:         172.16.0.93
    Prefix:          24 (255.255.255.0)
    Gateway:         172.16.0.2

    DNS:             172.16.0.254

</pre>

**Added additional info**

As per http://askubuntu.com/a/146310/10998
> For some reason avahi-daemon interferes with name resolver
<pre>
ping ns1
PING ns1.domain.local (172.16.0.254) 56(84) bytes of data.
64 bytes from ns1.domain.local (172.16.0.254): icmp_req=1 ttl=64 time=0.381 ms
networking

2 Answers

  1. Best Answer

    Edit the /etc/nsswitch.conf file.

    cat /etc/nsswitch.conf
...
#hosts:          files mdns4_minimal [NOTFOUND=return] dns mdns4
hosts:          files mdns4_minimal dns [NOTFOUND=return] mdns4
...

    That change fixed it for me. mdns is a particular implementation of DNS services which is meant to be faster than DNS. It does not resolve the names correctly and with the [NOTFOUND=return] option standard DNS is never used. This works fine for most of the Internet at large, but for some reason it is not working for our office resolutions.

    By changing the resolution to include DNS, I can now ping the domain controller as I expected. As well as the other services we are running on our local office domain.

    ping ns1.bidorbuy.local
PING ns1.domain.local (172.16.0.254) 56(84) bytes of data.
64 bytes from controler.domain.local (172.16.0.254): icmp_req=1 ttl=64 time=0.394 ms

ping office-blog.domain.local
PING officewebserver.domain.local (172.16.0.252) 56(84) bytes of data.
64 bytes from officewebserver.domain.local (172.16.0.252): icmp_req=1 ttl=64 time=0.914 ms
    • 13

  2. You can try to disable avahi-daemon. For some reason avahi-daemon interferes with name resolver. A side effect for me was that if you ping ns1, it works but if you try to use FQDN it does not.

    • 2