Routers and resolv.conf: [was: extremely slow to ssh out from my machine]
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
Reply to: