From: Clive McBarton on
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ron Johnson wrote:
>> I carefully type a domain name and some decent nameservers into
>> resolv.conf.
>>
>> Then all of it gets deleted and replaced by one single nameserver, which
>> is the router and the nameserver of my provider.
>
> Well, yeah, that's how dial-up works!

Hardly. The provider is welcome to provide their own nameserver as a
service, but I certainly can (and in this case want to) use another.

Also, since the machine is always in the same place, there's no need for
the nameservers to change unless I say so.

As for the internal domain name of my machine (and my network for that
matter), that should also be up to me to choose. This would not be
relevant for servers which need to have the same name internally and as
seen from the internet, but for a home machine it makes sense to set the
machine name and domain name independent of the provider.

> You've still never answered why you *care* about whether resolv.conf
> gets overridden on a regular basis.

See above.

> As long as The Internet Just Works,
> why do you care what's in resolv.conf?

It doesn't work because my provider's name servers do not.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkui6OMACgkQ+VSRxYk4409jyQCg5kAaXXZp3caGXc5AeFTYtB3W
kzAAnAwT5xhGDRKTMZGUf4Fa+cCXPNdJ
=plcE
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4BA2E8E3.2090008(a)web.de
From: Clive McBarton on
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ron Johnson wrote:
> You must have missed the BIG BOLD LETTERS that tell you not to write
> into resolv.conf by hand.
>
> $ cat /etc/resolv.conf
> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by
> resolvconf(8)
> # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
> nameserver xx.yy.zz.aa
> nameserver xx.yy.zz.bb
> search snagglefrob

I certainly noticed that comment. Had there also been a description
which file to edit instead, it would even have been a helpful comment.
But there hasn't, so it isn't helpful.

Also the comment stated "generated by resolvconf", indicating that
resolvconf was the program that changed it. But as I said it still
happened to me after deinstalling resolvconf.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkui6qQACgkQ+VSRxYk440+B3ACgmUwELLACZJt6sM4WQElZf/S6
1HsAnjwAPylvSYUsut0ewM2GwY3/0kp5
=3tYh
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4BA2EAA4.4040601(a)web.de
From: Ron Johnson on
On 2010-03-18 22:00, Clive McBarton wrote:
> Ron Johnson wrote:
>>> I carefully type a domain name and some decent nameservers into
>>> resolv.conf.
>>>
>>> Then all of it gets deleted and replaced by one single nameserver, which
>>> is the router and the nameserver of my provider.
>> Well, yeah, that's how dial-up works!
>
> Hardly. The provider is welcome to provide their own nameserver as a
> service, but I certainly can (and in this case want to) use another.
>
> Also, since the machine is always in the same place, there's no need for
> the nameservers to change unless I say so.

The ISP can certainly change name server IP address at their
prerogative.

> As for the internal domain name of my machine (and my network for that
> matter), that should also be up to me to choose. This would not be
> relevant for servers which need to have the same name internally and as
> seen from the internet, but for a home machine it makes sense to set the
> machine name and domain name independent of the provider.

If your machine is connected directly to your ISP (and that's what
happens during dial-up) *you* become part of *their* network.

>> You've still never answered why you *care* about whether resolv.conf
>> gets overridden on a regular basis.
>
> See above.
>
>> As long as The Internet Just Works,
>> why do you care what's in resolv.conf?
>
> It doesn't work because my provider's name servers do not.
>

You know, there's so much stuff you didn't tell us, which would have
made this thread sooo much shorter if you had told us earlier.

--
Obsession with "preserving cultural heritage" is a racist impediment
to moral, physical and intellectual progress.


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/4BA3234A.4030003(a)cox.net
From: Tom H on
In one of the first responses to your email, Camaleon said that there
were three possible culprits:
1. The resolvconf program
2. The network-manager daemon
3. DHCP clients

You have said that you have uninstalled the first two, so you just
have to configure the last one not to request name servers from the
ISP's dhcp server and to add your own by editing
/etc/dhcp3/dhclient.conf
if you have dhcp3-client as your dhcp client


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/6d4219cc1003190319w6196c263k10bc0f0a1064c203(a)mail.gmail.com
From: Mike McClain on
On Fri, Mar 19, 2010 at 04:08:20AM +0100, Clive McBarton wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Ron Johnson wrote:
> > You must have missed the BIG BOLD LETTERS that tell you not to write
> > into resolv.conf by hand.
> >
> > $ cat /etc/resolv.conf
> > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by
> > resolvconf(8)
> > # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
> > nameserver xx.yy.zz.aa
> > nameserver xx.yy.zz.bb
> > search snagglefrob
>
> I certainly noticed that comment. Had there also been a description
> which file to edit instead, it would even have been a helpful comment.
> But there hasn't, so it isn't helpful.
>
> Also the comment stated "generated by resolvconf", indicating that
> resolvconf was the program that changed it. But as I said it still
> happened to me after deinstalling resolvconf.

Try this as root: grep -R /etc/resolv.conf /etc/*

or this:
for d in $( echo $PATH | sed 's/:/ /g' );
do grep /etc/resolv.conf $d/*; done


Mike
--
Satisfied user of Linux since 1997.
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org


--
To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
Archive: http://lists.debian.org/20100319171540.GA31777(a)playground.mcclains.net