Results 1 to 4 of 4

Thread: resolvconf not being smart

  1. #1
    Join Date
    Jan 2007
    Beans
    44

    resolvconf not being smart

    I'm having an issue with resolvconf that I can't seem to figure out. Basically what is happening is that resolvconf is putting the nameserver from my last wireless connection at the top of my resolv.conf file, even if I am not connected to wireless and even if I am connected to a hardline. Obviously the desired behavior here is to put the eth* nameservers ahead of wireless cards... and if wireless is not up then don't put the wlan* nameservers in there.

    Anyone else experience this? Have any tips? I have poked around on it and frankly I don't understand where it picks up the last wireless connection's nameserver. If I bring down all the network connections and then run "resolvconf -u", it still puts the last active wireless connection's dns into resolv.conf!


    James

  2. #2
    Join Date
    Jan 2007
    Beans
    44

    Re: resolvconf not being smart

    Predictably... after fooling around with it for a while and finally resigning myself to posting on here for tips... I fixed it five minutes later. Somehow the act of posting always gives me the last bit of insight I need to fix an issue. Here is the explanation for others who may encounter the same problem:

    Techno description:
    The resolvconf script lists all files in /etc/resolvconf/run/interfaces for nameservers, in the order specified by the file /etc/resolvconf/interface-order. The NetworkManager puts a file into /etc/resolvconf/run/interfaces called "NetworkManager" which has the nameservers for your currently active NM connections. This file gets processed last because it does not match any of the lines in interface-order other than "*". Somehow I had an "eth0" file in the interfaces directory which was not getting correctly updated... just sitting there stuffing my wlan (odd eh?) nameserver into my resolv.conf every time resolvconf update was run.

    Cut to the chase description:
    If you are using NetworkManager to manage your network connections and nameservers/resolv.conf isn't behaving right, make sure that the only file in /etc/resolvconf/run/interfaces is "NetworkManager" and delete any other files.


    James

  3. #3
    Join Date
    Mar 2009
    Location
    Helsinki, Finland
    Beans
    650
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: resolvconf not being smart

    Quote Originally Posted by arsenix View Post
    Predictably... after fooling around with it for a while and finally resigning myself to posting on here for tips... I fixed it five minutes later. Somehow the act of posting always gives me the last bit of insight I need to fix an issue.
    Isn't that always the case? I've been wondering, if one could just begin with asking for help when problems arise, just to cut the tedious "trying everything you can think of" phase out of the loop and just focus on solving the issue in the following 5 minutes after asking for help.

  4. #4
    Join Date
    Mar 2007
    Beans
    131

    Re: resolvconf not being smart

    Doesn't work for me, I still have a 10 second delay connecting to any network because of resolvconf. I only have NetworkManager in /etc/resolvconf/run/interface after removing the file eth0.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •