Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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
$ nslookup ns1.domain.local

Name:    ns1.domain.local

$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
search domain.local

$ nm-tool

NetworkManager Tool

State: connected (global)

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

  IPv4 Settings:
    Prefix:          24 (



**Added additional info**

As per
> For some reason avahi-daemon interferes with name resolver
ping ns1
PING ns1.domain.local ( 56(84) bytes of data.
64 bytes from ns1.domain.local ( icmp_req=1 ttl=64 time=0.381 ms
share|improve this question
up vote 4 down vote accepted

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 ( 56(84) bytes of data.
64 bytes from controler.domain.local ( icmp_req=1 ttl=64 time=0.394 ms

ping office-blog.domain.local
PING officewebserver.domain.local ( 56(84) bytes of data.
64 bytes from officewebserver.domain.local ( icmp_req=1 ttl=64 time=0.914 ms
share|improve this answer
I was stumped on this one. Thanks for this hint, got me resolving internal domains. Was strange, setup two 14.04 installs back to back, the first had files dns [NOTFOUND=return] mdns4 without me doing anything but the second had files mdns4_minimal [NOTFOUND=return] dns which lead me to your answer. – markdsievers Aug 4 '14 at 2:37

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.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.