Mailinglist Archive: opensuse (3349 mails)

< Previous Next >
Re: [SLE] cable modem
  • From: Mike McMullin <mwmcmlln@xxxxxxxx>
  • Date: Sat, 28 May 2005 23:46:45 -0400
  • Message-id: <1117338403.8812.8.camel@xxxxxxxxxxxxxx>
On Sat, 2005-05-28 at 11:22, Scott Leighton wrote:
> On Saturday 28 May 2005 2:56 am, Greg Wallace wrote:
> > On Friday, May 27, 2005 5:17 PM, Scott Leighton wrote:
> > >On Thursday 26 May 2005 9:57 pm, Greg Wallace wrote:
> > >> On Thursday, May 26, 2005 3:30 AM, Ken Schneider wrote:
> > >> >On Wed, 2005-05-25 at 23:31 -0800, Greg Wallace wrote:
> > >> >> On Wednesday, May 25, 2005 @ 5:51 AM, Joe Morris wrote:
> > >> >> >Ken Schneider wrote:
> > >> >> >>The Linksys router will be your default route but -not- your
> > >>
> > >> nameserver.
> > >>
> > >> >> >>Use the name servers provided by your ISP.
> > >> >> >
> > >> >> >Is this a common problem with routers? I have a Netgear with the
> >
> > same
> >
> > >> >> >name server problems. For my linux machines I usually set up a
> > >> >> > local caching DNS using the ISPs DNS as forwarders, which works
> > >> >> > great for Linux but no such luck for Windows. Since they configure
> > >> >> > via DHCP,
> >
> > it
> >
> > >> >> >makes it a pain for a laptop. I thought it was maybe a Netgear
> > >> >> > problem,
> > >> >> >
> > >> >> >but maybe not. I was just wondering if this is a common router
> > >> >> > problem. --
> > >> >> >Joe Morris
> > >> >> >New Tribes Mission
> > >> >> >Email Address: Joe_Morris@xxxxxxx
> > >> >> >Registered Linux user 231871
> > >> >>
> > >> >> The setup you say you have now is what I had at one point and changed
> > >> >> because my entire network would be unavailable if that name server
> > >> >> was unavailable (say the ISP was unreachable). You then have no name
> > >> >> server. You should be able to just tell your machine that 192.168.1.1
> >
> > IS
> >
> > >> >> the name server.
> > >> >>
> > >> >> Greg Wallace
> > >> >
> > >> >What version of bind is running on your linksys router?
> > >> >
> > >> >--
> > >> >Ken Schneider
> > >> >UNIX since 1989, linux since 1994, SuSE since 1998
> > >> >
> > >> > "The day Microsoft makes something that doesn't suck is probably
> > >> > the day they start making vacuum cleaners." -Ernst Jan Plugge
> > >>
> > >> That I don't know. I logged into it but couldn't find any reference to
> > >> a bind version.
> > >
> > > Probably because the Linksys router does not run bind.
> > >
> > > On mine, a BEFSR41, I can configure the dns server entries to hand out
> > > to
> > >
> > >DHCP clients on the Linksys DHCP page, but that's not the same as running
> > > a
> > >
> > >DNS server.
> > >
> > > Scott
> >
> > But it's just grabbing the ip address from the name server it sees at the
> > ISP and handing it off to Linux, right? So as far as Linux is concerned,
> > it is the name server (it doesn't know the difference).
> >
>
> No, that's not the way I understand it. It's passing the address of the
> nameservers to your Linux box via DHCP, your Linux box then uses
> those addresses for /etc/resolv.conf, so the end result is that your
> Linux box gets its list of DNS servers from the Linksys, but after
> that, it is simply resolving addresses using the servers that
> were on the list, the Linksys isn't directly involved. The Linksys
> isn't running a nameserver, it is only passing out the addresses
> of nameservers.

Seems to make sense. So the OP seems to need the DNS server info for
the Linksys configuration, and point his boxes to the router\switch.


< Previous Next >