On Fri, 10 Jun 2005 19:20:10 +0200, Phil Dyer wrote:
> The other way would be to edit /etc/dhclient.conf and tell it to prepend
> to the list of dns servers
>
> prepend domain-name-servers x.x.x.x;
Or there's the supersede option in dhclient.conf which makes
resolv.conf only contain whatever you p
Paul Johnson writes:
> But they're not modems, they're bridges or routers.
They contain DSL modems in addition to bridges and/or routers. Look up how
DSL works.
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Friday June 10 2005 8:52 am, David Nicholls wrote:
> gpgkeys: key EB6AF9F2ED602A59 not found on keyserver
> Hi,
>
> I've got a few Debian (sarge) boxes connected to isp's via either
> ADSL modems (dlink dsl-300t's) or with a internal pci adsl modems.
That's nice. But they're not modems, they'r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Nicholls said:
> I've been having a few problems with dns lookups and have been given a
> new set up dns servers and not the same ones placed into resolv.conf by
> dhcp.
>
> Obviously if I make a change to resolv.conf, it will be soon-after be
>
You could just write a quick script that writes a good resolv.conf
file, and then stick it in your system-wide crontab. I don't know how
often it would need to run, but it should be pretty trivial.
Good luck,
Cameron Matheson
On 6/10/05, David Nicholls <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I've got a few Debian (sarge) boxes connected to isp's via either ADSL
modems (dlink dsl-300t's) or with a internal pci adsl modems.
I've been having a few problems with dns lookups and have been given a
new set up dns servers and not the same on
6 matches
Mail list logo
