Routers and resolv.conf: [was: extremely slow to ssh out from my machine]

From: michael (linux_at_networkingnewsletter.org.uk)
Date: 02/28/05

  • Next message: Lee Braiden: "Re: Routers and resolv.conf: [was: extremely slow to ssh out from my machine]"
    To: debian user <debian-user@lists.debian.org>
    Date: Mon, 28 Feb 2005 09:24:03 +0000
    
    

    Following on from...

    On Sun, 2005-02-27 at 20:51 +0000, michael wrote:
    > On Sun, 2005-02-27 at 20:45 +0000, michael wrote:
    > > On Sun, 2005-02-27 at 21:32 +0100, Jan C. Nordholz wrote:
    >
    > Jan & co
    > > >
    > > > Hm, your resolv.conf mentions the host 192.168.0.1 as primary
    > > > DNS server... this is giving problems later on... are you sure
    > > > that there's a DNS server running (and responding) there?
    > >
    > > 192.168.0.1 is the IP of my router/modem...
    > > Here's what the resolv.conf looks like
    > > search
    > > nameserver 192.168.0.1
    > > nameserver 212.1.130.32
    > >
    > >
    > >
    > > {snip}
    > >
    > > > I'd suggest checking the DNS server on 192.168.0.1, or at least
    > > > temporarily swapping the order in /etc/resolv.conf, so the one
    > > > that's most likely to respond is listed first.
    > > >
    > >
    > > I've just tried that and restarted sshd but that hasn't helped (does it
    > > required a full reboot or something else like resolver or named?)
    > >
    > aha - checking what the DNS IP is from my router and putting that as the
    > first nameserver makes it works much faster!
    >

    Upon reboot I noticed that the /etc/resolv.conf is rebuilt. Looking at
    the router (a D-Link) config again I see it has entries
     Configuration -> ProxyDNS 212.85.249.130
     Configuration -> DHCP configuration on LAN Primary DNS=192.168.0.1
     Configuration -> DHCP configuration on LAN Secondary DNS=212.1.130.32
    which lead to a /etc/resolv.conf of
      $ cat /etc/resolv.conf
      search
      nameserver 192.168.0.1
      nameserver 212.1.130.32

    giving the probs for ssh as before. Could some kind soul clarify to me
    the diffs between the 3 entries in the router config and why the
    proxyDNS doesn't appear in the resolv.conf?

    Thanks, Michael

    -- 
    To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
    

  • Next message: Lee Braiden: "Re: Routers and resolv.conf: [was: extremely slow to ssh out from my machine]"

    Relevant Pages

    • Re:SOLVVED vinum crashes the Box... WRONG POSTING
      ... vinum crashes the Box by using more then ten disks on ... > With this configuration vinum crashes the Machine with this Message: ... > I'm going to enable the kernel debugger now... ... >> while devfs rules works for those, but they vanish on reboot. ...
      (freebsd-stable)
    • Re: Lost files after using "Last Known Good Configuration"
      ... reboot would have placed this as your Last Known Good Configuration. ... Last Known Good Configuration was prior to the password change, hence, your ... > When coming out of hibernation mode I was asked to by Windows to change my ... > I purchased a copy of Recover Lost Data 2005 from StompSoft at my local ...
      (microsoft.public.windowsxp.general)
    • Re: Lost files after using "Last Known Good Configuration"
      ... "Using Last Known Good Configuration ... > reboot would have placed this as your Last Known Good Configuration. ... you went into hibernation without rebooting. ... >> I purchased a copy of Recover Lost Data 2005 from StompSoft at my local ...
      (microsoft.public.windowsxp.general)
    • Re: Well, duh. Was Re: New laptop with Vista, cant connect
      ... but it took a router/modem reboot to allow me to connect. ... the router cached the wrong address for the wow server. ... Normal net access on both, ... some seemed to require configuration, ...
      (alt.games.warcraft)
    • Re: TOT computer hassle
      ... But this afternoon when I went back to the machine after lunch, having used it all morning, as soon as I moved the mouse it froze, and could not be rebooted by Cont Alt Del. ... When it came back on it got half way thro loading Windows and froze, so I rebooted it, and this time it came up with a DOS message which included the option to adopt the 'last configuration that worked normally'. ... This is a known bug that affects a small number of systems - they get stuck in a reboot cycle. ... You may currently have it set to not change networks and hence it is stuck looking for the caravan club one. ...
      (uk.tech.digital-tv)