Ubuntu – How to fix DNS resolving which doesn’t work after upgrading to Ubuntu 13.10 (Saucy)


After upgrade to 13.10 my DNS resolving fails. It seems the DNS servers which I get by DHCP (LAN) are not used.

I could temporary solve the problem by adding nameserver to /etc/resolv.conf. But then the intranet hosts still can not be resolved.

When clicking on the Connection Information menu item on the network indicator, the Primary DNS and the Secondary DNS are set correctly. But my computer seams not to use them.

So my questions:

  • What should I put into resolv.conf, if anything?
  • How to find out, which name servers my computer is querying?
  • Where to look next, to find out, why name servers received by DHCP are not used?

Best Answer

  • First you need to know a bit about how name resolving works in Ubuntu since Ubuntu 12.04.

    St├ęphane Graber blogged some information about it last year here. The most important thing to know is that both Ubuntu Server and Ubuntu Desktop use resolvconf to manage the resolv.conf file. That means that you should no longer edit /etc/resolv.conf directly; instead you should configure your network interface configuration utility to provide the right information to resolvconf. For Ubuntu Server the network interface configuration utility is ifup and it is configured by the file /etc/network/interfaces. For Ubuntu Desktop the network interface configuration utility is NetworkManager. This is what you are using.

    NetworkManager is configured by means of Network indicator > Edit Connections. However, for network interfaces configured by DHCP it normally isn't necessary to change any settings manually. Normally what happens is that the (remote) DHCP server provides to NetworkManager both an IP address for the local interface and the address of a (remote) DNS nameserver to use. NetworkManager starts an instance of a forwarding nameserver that listens locally at This address,, is sent to resolvconf which puts nameserver in /etc/resolv.conf. NetworkManager also gives the (remote) IP address of the DHCP-provided DNS nameserver to the forwarding nameserver. Thus a program running on the local system asks the resolver to translate a host name into an IP address; the resolver queries the local forwarding nameserver at; the forwarding nameserver queries the remote nameserver(s) it has been told about, receives an answer and sends it back up the chain.

    NetworkManager communicates with the forwarding nameserver process over D-Bus. You can see what NetworkManager told the forwarding nameserver by running the command

    nmcli dev list iface eth0 | grep IP4.DNS

    Update arising from the comments:
    Note that resolvconf actually writes the file /run/resolvconf/resolv.conf to which /etc/resolv.conf is supposed to be a symbolic link. If /etc/resolv.conf is not a symbolic link then you need to recreate it. To do so you can run

    sudo dpkg-reconfigure resolvconf


    sudo ln -sf /run/resolvconf/resolv.conf /etc/resolv.conf        
  • Related Question