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@ntm.org 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). Greg W.