Announcement

Collapse
No announcement yet.

apt-get DNS problem

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    apt-get DNS problem

    Hi,

    I have a DNS problem that affects apt-get. Konqueror reliably connects to the web, but a default apt-get configuration always freezes at:

    0% [Connecting to gb.archive.ubuntu.com (1.0.0.0)]

    I can achieve a temporary fix to this problem by adding extra DNS servers to /etc/resolv.conf as detailed here: http://www.linuxquestions.org/questi...d.php?t=381026 , but the final suggestion in that thread about modifying dhclient.conf to prevent DHCP refreshes from overwriting resolv.conf doesn't work for me. I modified /etc/dhcp3/dhclient.conf. Is that the correct file?

    I also tried adding DNS servers in the desktop tool System Settings - Network Settings. Again, this provides a temporary fix, but the additional servers get removed again every time the DHCP refreshes (which is every few minutes).

    Is there any way to permanently add DNS servers to a DHCP based system, or can someone suggest why Konqueror can successfully use my router's DNS forwarding, but apt-get can't?

    -Foob

    #2
    Re: apt-get DNS problem

    I think I had the exact same problem (original thread: http://kubuntuforums.net/forums/inde...28742#msg28742) and found the same fix. I've since tried that trick modifying /etc/dhcp3/dhclient.conf and it works fine for me (yes, that is indeed the correct file). Could you maybe post your dhclient.conf so we can see it?

    Comment


      #3
      Re: apt-get DNS problem

      I just found the problem. I forgot the semi-colon at the end of the line in the dhclient.conf script. You'd think a C programmer would have spotted that

      Comment


        #4
        Re: apt-get DNS problem

        I have the same problem. I have installed kubuntu dapper on 4 or 5 machines so far. Each time the same thing happens. After installation I open adept and enable all repos and do a full upgrade. No problem. But as soon as run apt-get then I get errors like 404 page not found and others. I then have to into network settings and add a second DNS address and remove the ill gotten IP address (192.168.0.1). At this very moment adept is doing a full upgrade with no problems and my /etc/resolve.conf file looks like the following:

        search domain.actdsltmp
        nameserver 192.168.0.1
        nameserver 65.101.121.10

        So why is it that when I run apt-get I have to add my ISP's second DNS addy for it to work
        This also happened with Breezy on 3 machines.
        Charlie
        I tried Enlightenment once, it was pretty cool.

        Comment


          #5
          Re: apt-get DNS problem

          Are you connected with DSL? Are you using an Actiontec DSL modem/router? If so, that may be your problem. I had this exact same problem and it ended up being a problem with the DNS cache in the Actiontec router (I believe).

          Comment


            #6
            Re: apt-get DNS problem

            No idea why it's doing that. Have you tried altering the dhclient.conf file? By using "prepend", it should append the nameserver line ahead of the 192.168.0.1 one, so it should take priority (I think).

            Comment


              #7
              Re: apt-get DNS problem

              Are you connected with DSL?  Are you using an Actiontec DSL modem/router?

              Yes.

              Have you tried altering the dhclient.conf file? By using "prepend",

              not yet.  My problem with this is laptops.  If one is using a laptop and is connecting to different networks then it will be just as hard to to updates, yes? Because the wrong DNS address will be added to the configuration?
              Charlie
              I tried Enlightenment once, it was pretty cool.

              Comment


                #8
                Re: apt-get DNS problem

                not yet. My problem with this is laptops. If one is using a laptop and is connecting to different networks then it will be just as hard to to updates, yes? Because the wrong DNS address will be added to the configuration?
                Ah yes. I didn't realise - in which case, that workaround is completely useless for you. Sorry!

                Comment

                Working...
                X