Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #211946 > unrolled thread

Re: Which resolv.conf file?

Started byReco <recoverym4n@enotuniq.net>
First post2019-07-31 08:10 +0200
Last post2019-08-02 05:20 +0200
Articles 12 — 6 participants

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Which resolv.conf file? Reco <recoverym4n@enotuniq.net> - 2019-07-31 08:10 +0200
    Re: Which resolv.conf file? Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-31 08:20 +0200
      Re: Which resolv.conf file? Reco <recoverym4n@enotuniq.net> - 2019-07-31 08:30 +0200
        Re: Which resolv.conf file? Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-31 15:00 +0200
          Re: Which resolv.conf file? David Wright <deblis@lionunicorn.co.uk> - 2019-07-31 16:00 +0200
            Re: Which resolv.conf file? Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-31 16:30 +0200
              Re: Which resolv.conf file? Reco <recoverym4n@enotuniq.net> - 2019-07-31 16:40 +0200
              Re: Which resolv.conf file? <tomas@tuxteam.de> - 2019-07-31 18:00 +0200
                Re: Which resolv.conf file? Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-31 18:10 +0200
                  Re: Which resolv.conf file? <tomas@tuxteam.de> - 2019-07-31 18:40 +0200
            Re: Which resolv.conf file? Andrei POPESCU <andreimpopescu@gmail.com> - 2019-07-31 22:30 +0200
            Re: Which resolv.conf file? Celejar <celejar@gmail.com> - 2019-08-02 05:20 +0200

#211946 — Re: Which resolv.conf file?

FromReco <recoverym4n@enotuniq.net>
Date2019-07-31 08:10 +0200
SubjectRe: Which resolv.conf file?
Message-ID<ypPYe-5Ud-3@gated-at.bofh.it>
	Hi.

On Wed, Jul 31, 2019 at 01:46:45AM -0400, Bob Bernstein wrote:
> I want to make a change or two to resolv.conf, but every time I come
> across it I flee in terror, warned that my changes will be destroyed
> and the linux gods angered.

Have you meant this resolv.conf line?

# 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


> What is the approved method for changing the list of DNS servers
> called upon by, in my case, Stretch on amd-64?

Assuming it is, and you're using ifupdown, you need to change
"dns-nameserver" stanza in the interface definition.

Reco

[toc] | [next] | [standalone]

#211949

FromAndrei POPESCU <andreimpopescu@gmail.com>
Date2019-07-31 08:20 +0200
Message-ID<ypQ7U-5XW-3@gated-at.bofh.it>
In reply to#211946

[Multipart message — attachments visible in raw view] — view raw

On Mi, 31 iul 19, 09:06:36, Reco wrote:
> 	Hi.
> 
> On Wed, Jul 31, 2019 at 01:46:45AM -0400, Bob Bernstein wrote:
> > I want to make a change or two to resolv.conf, but every time I come
> > across it I flee in terror, warned that my changes will be destroyed
> > and the linux gods angered.
> 
> Have you meant this resolv.conf line?
> 
> # 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
> 
> 
> > What is the approved method for changing the list of DNS servers
> > called upon by, in my case, Stretch on amd-64?
> 
> Assuming it is, and you're using ifupdown, you need to change
> "dns-nameserver" stanza in the interface definition.

Careful, in /etc/network/interfaces it's 'dns-nameservers' (mind the 
trailing 's'), because you can list more servers ;)

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#211950

FromReco <recoverym4n@enotuniq.net>
Date2019-07-31 08:30 +0200
Message-ID<ypQhA-61x-3@gated-at.bofh.it>
In reply to#211949
	Hi.

On Wed, Jul 31, 2019 at 09:16:03AM +0300, Andrei POPESCU wrote:
> On Mi, 31 iul 19, 09:06:36, Reco wrote:
> > On Wed, Jul 31, 2019 at 01:46:45AM -0400, Bob Bernstein wrote:
> > > I want to make a change or two to resolv.conf, but every time I come
> > > across it I flee in terror, warned that my changes will be destroyed
> > > and the linux gods angered.
> > 
> > Have you meant this resolv.conf line?
> > 
> > # 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
> > 
> > 
> > > What is the approved method for changing the list of DNS servers
> > > called upon by, in my case, Stretch on amd-64?
> > 
> > Assuming it is, and you're using ifupdown, you need to change
> > "dns-nameserver" stanza in the interface definition.
> 
> Careful, in /etc/network/interfaces it's 'dns-nameservers' (mind the 
> trailing 's'), because you can list more servers ;)

/usr/share/doc/resolvconf/README.gz disagrees with you:

* For each inet static logical interface through which a nameserver
  is accessible, add lines like the following to /etc/network/interfaces .

	  dns-nameserver 11.22.33.44
	  dns-nameserver 55.66.77.88
	  dns-search foo.org bar.com

Reco

[toc] | [prev] | [next] | [standalone]

#211970

FromGreg Wooledge <wooledg@eeg.ccf.org>
Date2019-07-31 15:00 +0200
Message-ID<ypWmZ-1oI-3@gated-at.bofh.it>
In reply to#211950
On Wed, Jul 31, 2019 at 09:21:32AM +0300, Reco wrote:
> On Wed, Jul 31, 2019 at 09:16:03AM +0300, Andrei POPESCU wrote:
> > On Mi, 31 iul 19, 09:06:36, Reco wrote:
> > > Assuming it is, and you're using ifupdown, you need to change
> > > "dns-nameserver" stanza in the interface definition.
> > 
> > Careful, in /etc/network/interfaces it's 'dns-nameservers' (mind the 
> > trailing 's'), because you can list more servers ;)
> 
> /usr/share/doc/resolvconf/README.gz disagrees with you:
> 
> * For each inet static logical interface through which a nameserver
>   is accessible, add lines like the following to /etc/network/interfaces .
> 
> 	  dns-nameserver 11.22.33.44
> 	  dns-nameserver 55.66.77.88
> 	  dns-search foo.org bar.com

Reco is correct.

isc-dhcp-client uses "domain-name-servers" in its configuration file,
whereas resolvconf uses "dns-nameserver".  Most likely, Andrei momentarily
confused the two.

[toc] | [prev] | [next] | [standalone]

#211976

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2019-07-31 16:00 +0200
Message-ID<ypXj3-1YP-3@gated-at.bofh.it>
In reply to#211970
On Wed 31 Jul 2019 at 08:50:34 (-0400), Greg Wooledge wrote:
> On Wed, Jul 31, 2019 at 09:21:32AM +0300, Reco wrote:
> > On Wed, Jul 31, 2019 at 09:16:03AM +0300, Andrei POPESCU wrote:
> > > On Mi, 31 iul 19, 09:06:36, Reco wrote:
> > > > Assuming it is, and you're using ifupdown, you need to change
> > > > "dns-nameserver" stanza in the interface definition.
> > > 
> > > Careful, in /etc/network/interfaces it's 'dns-nameservers' (mind the 
> > > trailing 's'), because you can list more servers ;)
> > 
> > /usr/share/doc/resolvconf/README.gz disagrees with you:
> > 
> > * For each inet static logical interface through which a nameserver
> >   is accessible, add lines like the following to /etc/network/interfaces .
> > 
> > 	  dns-nameserver 11.22.33.44
> > 	  dns-nameserver 55.66.77.88
> > 	  dns-search foo.org bar.com
> 
> Reco is correct.
> 
> isc-dhcp-client uses "domain-name-servers" in its configuration file,
> whereas resolvconf uses "dns-nameserver".  Most likely, Andrei momentarily
> confused the two.

It might be the documentation that's confused. Here's an extract from
man resolvconf

✄✄✄✄✄✄✄✄

   ifup
       The ifup program can be used to configure network  interfaces
       according  to  settings  in /etc/network/interfaces.   To  make
       ifup push nameserver information to resolvconf when it
       configures an interface the administrator must add dns- option
       lines to the relevant iface stanza  in  interfaces(5).   The
       following  option  names  are  accepted: dns-nameserver,
       dns-search, and dns-sortlist. To add a nameserver IP address,
       add an option line consisting of  dns-nameserver  and  the
       address.   To  add  multiple  nameserver  addresses,  include
       multiple such dns-nameserver lines.

           dns-nameserver 192.168.1.254
           dns-nameserver 8.8.8.8

       To add search domain names, add a line beginning with dns-search.

           dns-search foo.org bar.com

       The dns-nameservers option is also accepted and, unlike dns-nameserver, can be given  mul‐
       tiple arguments, separated by spaces.

       The dns-domain option is deprecated in favor of dns-search.

       The resulting stanza might look like the following example.

           iface eth0 inet static
               address 192.168.1.3
               netmask 255.255.255.0
               gateway 192.168.1.1
               dns-nameserver 192.168.1.254
               dns-nameserver 8.8.8.8
               dns-search foo.org bar.com

✄✄✄✄✄✄✄✄

IOW you should be able to write

           dns-nameserver 192.168.1.254
           dns-nameserver 8.8.8.8

or

           dns-nameservers 192.168.1.254 8.8.8.8

But I have no idea whether

           dns-nameservers 8.8.8.8

and

           dns-nameservers 192.168.1.254
           dns-nameservers 8.8.8.8

are supported. Messy.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#211979

FromGreg Wooledge <wooledg@eeg.ccf.org>
Date2019-07-31 16:30 +0200
Message-ID<ypXM5-2oE-9@gated-at.bofh.it>
In reply to#211976
On Wed, Jul 31, 2019 at 08:59:11AM -0500, David Wright wrote:
> It might be the documentation that's confused. Here's an extract from
> man resolvconf
> 
> ✄✄✄✄✄✄✄✄
> 
>    ifup
>        The ifup program can be used to configure network  interfaces
[...]

Mine doesn't... wait, what...

wooledg:~$ dpkg -S resolvconf.1
systemd: /usr/share/man/man1/resolvconf.1.gz

Well, THAT's confusing as hell.

[toc] | [prev] | [next] | [standalone]

#211980

FromReco <recoverym4n@enotuniq.net>
Date2019-07-31 16:40 +0200
Message-ID<ypXVL-2rY-5@gated-at.bofh.it>
In reply to#211979
On Wed, Jul 31, 2019 at 10:27:01AM -0400, Greg Wooledge wrote:
> On Wed, Jul 31, 2019 at 08:59:11AM -0500, David Wright wrote:
> > It might be the documentation that's confused. Here's an extract from
> > man resolvconf
> > 
> > ✄✄✄✄✄✄✄✄
> > 
> >    ifup
> >        The ifup program can be used to configure network  interfaces
> [...]
> 
> Mine doesn't... wait, what...
> 
> wooledg:~$ dpkg -S resolvconf.1
> systemd: /usr/share/man/man1/resolvconf.1.gz
> 
> Well, THAT's confusing as hell.

Read it ;) It's not about resolvconf(1).
Real resolvconf is resolvconf(8).
It's impossible to understand, it's only possible to remember.

Reco

[toc] | [prev] | [next] | [standalone]

#211987

From<tomas@tuxteam.de>
Date2019-07-31 18:00 +0200
Message-ID<ypZbc-38O-15@gated-at.bofh.it>
In reply to#211979

[Multipart message — attachments visible in raw view] — view raw

On Wed, Jul 31, 2019 at 10:27:01AM -0400, Greg Wooledge wrote:
> On Wed, Jul 31, 2019 at 08:59:11AM -0500, David Wright wrote:
> > It might be the documentation that's confused. Here's an extract from
> > man resolvconf
> > 
> > ✄✄✄✄✄✄✄✄
> > 
> >    ifup
> >        The ifup program can be used to configure network  interfaces
> [...]
> 
> Mine doesn't... wait, what...
> 
> wooledg:~$ dpkg -S resolvconf.1
> systemd: /usr/share/man/man1/resolvconf.1.gz

tomas@trotzki:~$ dpkg -S resolv.conf
manpages: /usr/share/man/man5/resolv.conf.5.gz

Hmmm.

Cheers
-- t

[toc] | [prev] | [next] | [standalone]

#211988

FromGreg Wooledge <wooledg@eeg.ccf.org>
Date2019-07-31 18:10 +0200
Message-ID<ypZkS-3rN-13@gated-at.bofh.it>
In reply to#211987
On Wed, Jul 31, 2019 at 05:55:17PM +0200, tomas@tuxteam.de wrote:
> On Wed, Jul 31, 2019 at 10:27:01AM -0400, Greg Wooledge wrote:
> > wooledg:~$ dpkg -S resolvconf.1
> > systemd: /usr/share/man/man1/resolvconf.1.gz
> 
> tomas@trotzki:~$ dpkg -S resolv.conf
> manpages: /usr/share/man/man5/resolv.conf.5.gz

resolv.conf(5) is the configuration file for the DNS resolver in libc.

resolvconf(8) is a Debian package that intercepts attempts by various
other packages to mangle your /etc/resolv.conf file, and lets you control
how they can or cannot do so.

resolvconf(1) is apparently an alias for resolvctl(1) which is part of
systemd, and has absolutely nothing to do with ANYTHING, other than
getting in the way if a naive person (in this example, me) tries to
run "man resolvconf".

[toc] | [prev] | [next] | [standalone]

#211990

From<tomas@tuxteam.de>
Date2019-07-31 18:40 +0200
Message-ID<ypZNT-3Cb-11@gated-at.bofh.it>
In reply to#211988

[Multipart message — attachments visible in raw view] — view raw

On Wed, Jul 31, 2019 at 12:09:38PM -0400, Greg Wooledge wrote:
> On Wed, Jul 31, 2019 at 05:55:17PM +0200, tomas@tuxteam.de wrote:
> > On Wed, Jul 31, 2019 at 10:27:01AM -0400, Greg Wooledge wrote:
> > > wooledg:~$ dpkg -S resolvconf.1
> > > systemd: /usr/share/man/man1/resolvconf.1.gz
> > 
> > tomas@trotzki:~$ dpkg -S resolv.conf
> > manpages: /usr/share/man/man5/resolv.conf.5.gz
> 
> resolv.conf(5) is the configuration file for the DNS resolver in libc.
> 
> resolvconf(8) is a Debian package that intercepts attempts by various
> other packages to mangle your /etc/resolv.conf file, and lets you control
> how they can or cannot do so.
> 
> resolvconf(1) is apparently an alias for resolvctl(1) which is part of
> systemd, and has absolutely nothing to do with ANYTHING, other than
> getting in the way if a naive person (in this example, me) tries to
> run "man resolvconf".

:-)

Cheers
-- t

[toc] | [prev] | [next] | [standalone]

#212012

FromAndrei POPESCU <andreimpopescu@gmail.com>
Date2019-07-31 22:30 +0200
Message-ID<yq3ot-5W0-3@gated-at.bofh.it>
In reply to#211976

[Multipart message — attachments visible in raw view] — view raw

On Mi, 31 iul 19, 08:59:11, David Wright wrote:
> On Wed 31 Jul 2019 at 08:50:34 (-0400), Greg Wooledge wrote:
> > On Wed, Jul 31, 2019 at 09:21:32AM +0300, Reco wrote:
> > > On Wed, Jul 31, 2019 at 09:16:03AM +0300, Andrei POPESCU wrote:
> > > > On Mi, 31 iul 19, 09:06:36, Reco wrote:
> > > > > Assuming it is, and you're using ifupdown, you need to change
> > > > > "dns-nameserver" stanza in the interface definition.
> > > > 
> > > > Careful, in /etc/network/interfaces it's 'dns-nameservers' (mind the 
> > > > trailing 's'), because you can list more servers ;)
> > > 
> > > /usr/share/doc/resolvconf/README.gz disagrees with you:
> > > 
> > > * For each inet static logical interface through which a nameserver
> > >   is accessible, add lines like the following to /etc/network/interfaces .
> > > 
> > > 	  dns-nameserver 11.22.33.44
> > > 	  dns-nameserver 55.66.77.88
> > > 	  dns-search foo.org bar.com
> > 
> > Reco is correct.
> > 
> > isc-dhcp-client uses "domain-name-servers" in its configuration file,
> > whereas resolvconf uses "dns-nameserver".  Most likely, Andrei momentarily
> > confused the two.
> 
> It might be the documentation that's confused. Here's an extract from
> man resolvconf

[...]
 
>        The dns-nameservers option is also accepted and, unlike dns-nameserver, can be given  mul‐
>        tiple arguments, separated by spaces.

Ok, the 'dns-nameserver' option must have been added in the meantime, as 
'dns-nameservers' was quite confusing (I got bit by it several times).

Let's see... according to the changelog it was added in Jessie ;)

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#212125

FromCelejar <celejar@gmail.com>
Date2019-08-02 05:20 +0200
Message-ID<yqwgO-7xs-5@gated-at.bofh.it>
In reply to#211976
On Wed, 31 Jul 2019 08:59:11 -0500
David Wright <deblis@lionunicorn.co.uk> wrote:

> On Wed 31 Jul 2019 at 08:50:34 (-0400), Greg Wooledge wrote:
> > On Wed, Jul 31, 2019 at 09:21:32AM +0300, Reco wrote:
> > > On Wed, Jul 31, 2019 at 09:16:03AM +0300, Andrei POPESCU wrote:
> > > > On Mi, 31 iul 19, 09:06:36, Reco wrote:
> > > > > Assuming it is, and you're using ifupdown, you need to change
> > > > > "dns-nameserver" stanza in the interface definition.
> > > > 
> > > > Careful, in /etc/network/interfaces it's 'dns-nameservers' (mind the 
> > > > trailing 's'), because you can list more servers ;)
> > > 
> > > /usr/share/doc/resolvconf/README.gz disagrees with you:

...

> > Reco is correct.
> > 
> > isc-dhcp-client uses "domain-name-servers" in its configuration file,
> > whereas resolvconf uses "dns-nameserver".  Most likely, Andrei momentarily
> > confused the two.
> 
> It might be the documentation that's confused. Here's an extract from
> man resolvconf

...

> IOW you should be able to write
> 
>            dns-nameserver 192.168.1.254
>            dns-nameserver 8.8.8.8
> 
> or
> 
>            dns-nameservers 192.168.1.254 8.8.8.8
> 
> But I have no idea whether
> 
>            dns-nameservers 8.8.8.8
> 
> and
> 
>            dns-nameservers 192.168.1.254
>            dns-nameservers 8.8.8.8
> 
> are supported. Messy.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718021

Celejar

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web