Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #188193 > unrolled thread
| Started by | Roberto C. Sánchez <roberto@debian.org> |
|---|---|
| First post | 2017-10-23 04:20 +0200 |
| Last post | 2017-10-25 16:20 +0200 |
| Articles | 20 on this page of 138 — 29 participants |
Back to article view | Back to linux.debian.user
Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-23 04:20 +0200
Re: Why does resolv.conf keep changing? Joe <joe@jretrading.com> - 2017-10-23 11:00 +0200
Re: Why does resolv.conf keep changing? <tomas@tuxteam.de> - 2017-10-23 11:50 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-24 01:40 +0200
Re: Why does resolv.conf keep changing? David Wright <deblis@lionunicorn.co.uk> - 2017-10-24 02:30 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-24 05:10 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-24 09:20 +0200
Re: Why does resolv.conf keep changing? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-24 14:20 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-24 14:30 +0200
Re: Why does resolv.conf keep changing? Curt <curty@free.fr> - 2017-10-24 19:10 +0200
Re: Why does resolv.conf keep changing? David Wright <deblis@lionunicorn.co.uk> - 2017-10-24 18:50 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-25 15:30 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-25 15:40 +0200
Re: Why does resolv.conf keep changing? David Wright <deblis@lionunicorn.co.uk> - 2017-10-25 20:50 +0200
Re: Why does resolv.conf keep changing? Roger Lynn <Roger@rilynn.me.uk> - 2017-10-25 00:30 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-25 04:10 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-23 13:00 +0200
Re: Why does resolv.conf keep changing? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-23 18:10 +0200
Re: Why does resolv.conf keep changing? Jude DaShiell <jdashiel@panix.com> - 2017-10-23 18:10 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-23 23:10 +0200
Re: Why does resolv.conf keep changing? Dan Ritter <dsr@randomstring.org> - 2017-10-24 00:00 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-24 02:40 +0200
Re: Why does resolv.conf keep changing? Michael Stone <mstone@debian.org> - 2017-10-25 03:20 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-25 05:00 +0200
Re: Why does resolv.conf keep changing? Michael Stone <mstone@debian.org> - 2017-10-25 05:10 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-25 06:20 +0200
Re: Why does resolv.conf keep changing? Michael Stone <mstone@debian.org> - 2017-10-25 13:40 +0200
Re: Why does resolv.conf keep changing? Alberto Luaces <aluaces@udc.es> - 2017-10-25 14:10 +0200
Re: Why does resolv.conf keep changing? Michael Stone <mstone@debian.org> - 2017-10-25 15:30 +0200
Re: Why does resolv.conf keep changing? <tomas@tuxteam.de> - 2017-10-25 15:50 +0200
Re: Why does resolv.conf keep changing? Curt <curty@free.fr> - 2017-10-25 16:30 +0200
Re: Why does resolv.conf keep changing? Joe <joe@jretrading.com> - 2017-10-25 17:10 +0200
Re: Why does resolv.conf keep changing? <tomas@tuxteam.de> - 2017-10-25 17:30 +0200
Re: Why does resolv.conf keep changing? rhkramer@gmail.com - 2017-10-25 19:00 +0200
Re: Why does resolv.conf keep changing? <tomas@tuxteam.de> - 2017-10-25 19:10 +0200
Re: Why does resolv.conf keep changing? rhkramer@gmail.com - 2017-10-25 19:40 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-25 14:20 +0200
Re: Why does resolv.conf keep changing? Felix Miata <mrmazda@earthlink.net> - 2017-10-25 05:50 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-25 13:40 +0200
Re: Why does resolv.conf keep changing? <tomas@tuxteam.de> - 2017-10-25 14:00 +0200
Re: Why does resolv.conf keep changing? tomas@tuxteam.de - 2017-10-25 14:20 +0200
Re: Why does resolv.conf keep changing? Nicolas George <george@nsup.org> - 2017-10-25 14:50 +0200
Re: Why does resolv.conf keep changing? Joe <joe@jretrading.com> - 2017-10-25 14:10 +0200
Re: Why does resolv.conf keep changing? <tomas@tuxteam.de> - 2017-10-25 14:20 +0200
Re: Why does resolv.conf keep changing? Joe <joe@jretrading.com> - 2017-10-25 15:00 +0200
Re: Why does resolv.conf keep changing? Dan Ritter <dsr@randomstring.org> - 2017-10-25 17:10 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-25 18:50 +0200
Re: Why does resolv.conf keep changing? Don Armstrong <don@debian.org> - 2017-10-25 21:30 +0200
Re: Why does resolv.conf keep changing? Michael Stone <mstone@debian.org> - 2017-10-25 13:40 +0200
Re: Why does resolv.conf keep changing? Glenn English <ghe2001@gmail.com> - 2017-10-26 17:40 +0200
Re: Why does resolv.conf keep changing? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-26 17:50 +0200
Re: Why does resolv.conf keep changing? The Wanderer <wanderer@fastmail.fm> - 2017-10-26 18:00 +0200
Re: Why does resolv.conf keep changing? Nicholas Geovanis <nickgeovanis@gmail.com> - 2017-10-26 18:20 +0200
Re: Why does resolv.conf keep changing? Nicholas Geovanis <nickgeovanis@gmail.com> - 2017-10-26 18:40 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-27 02:00 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-27 02:00 +0200
Re: Why does resolv.conf keep changing? Jörg-Volker Peetz <jvpeetz@web.de> - 2017-10-23 12:10 +0200
Re: Why does resolv.conf keep changing? Stefan Monnier <monnier@iro.umontreal.ca> - 2017-10-25 05:50 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-25 06:10 +0200
Re: Why does resolv.conf keep changing? Stefan Monnier <monnier@iro.umontreal.ca> - 2017-10-25 06:50 +0200
Re: Why does resolv.conf keep changing? Curt <curty@free.fr> - 2017-10-25 08:50 +0200
Re: Why does resolv.conf keep changing? Stefan Monnier <monnier@iro.umontreal.ca> - 2017-10-25 14:40 +0200
Re: Why does resolv.conf keep changing? <tomas@tuxteam.de> - 2017-10-25 14:50 +0200
Re: Why does resolv.conf keep changing? Stefan Monnier <monnier@iro.umontreal.ca> - 2017-10-25 15:00 +0200
Re: Why does resolv.conf keep changing? <tomas@tuxteam.de> - 2017-10-25 15:10 +0200
Re: Why does resolv.conf keep changing? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-25 15:10 +0200
Re: Why does resolv.conf keep changing? <tomas@tuxteam.de> - 2017-10-25 15:10 +0200
Re: Why does resolv.conf keep changing? Michael Stone <mstone@debian.org> - 2017-10-25 15:30 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-25 15:30 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-25 16:10 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-25 16:10 +0200
[SOLVED] Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-25 20:30 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Michael Stone <mstone@debian.org> - 2017-10-25 20:40 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-25 20:40 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-25 21:00 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-25 21:00 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-26 15:10 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-26 15:40 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-26 16:00 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Don Armstrong <don@debian.org> - 2017-10-26 21:40 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-26 21:40 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Nicholas Geovanis <nickgeovanis@gmail.com> - 2017-10-26 16:30 +0200
The new normal of logging Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM> - 2017-10-26 21:10 +0200
Re: The new normal of logging Nicholas Geovanis <nickgeovanis@gmail.com> - 2017-10-26 21:30 +0200
Re: The new normal of logging Gene Heskett <gheskett@shentel.net> - 2017-10-27 02:10 +0200
Re: The new normal of logging Ben Caradoc-Davies <ben@transient.nz> - 2017-10-27 03:30 +0200
Re: The new normal of logging Gene Heskett <gheskett@shentel.net> - 2017-10-27 07:00 +0200
Re: The new normal of logging Ben Caradoc-Davies <ben@transient.nz> - 2017-10-28 04:50 +0200
Re: The new normal of logging Gene Heskett <gheskett@shentel.net> - 2017-10-28 08:10 +0200
Re: The new normal of logging Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2017-10-27 04:10 +0200
Re: The new normal of logging Darac Marjal <mailinglist@darac.org.uk> - 2017-10-27 11:40 +0200
Plain text vs. binary (was Re: The new normal of logging) The Wanderer <wanderer@fastmail.fm> - 2017-10-27 14:40 +0200
Re: The new normal of logging Roberto C. Sánchez <roberto@debian.org> - 2017-10-26 21:30 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-27 17:10 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-27 17:50 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Curt <curty@free.fr> - 2017-10-27 20:30 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Brian <ad44@cityscape.co.uk> - 2017-10-27 20:50 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Curt <curty@free.fr> - 2017-10-27 21:50 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-27 22:00 +0200
Re: [SOLVED] Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-28 18:30 +0200
Re: Why does resolv.conf keep changing? Stefan Monnier <monnier@iro.umontreal.ca> - 2017-10-26 05:40 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-26 12:50 +0200
Re: Why does resolv.conf keep changing? Darac Marjal <mailinglist@darac.org.uk> - 2017-10-26 13:30 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-26 13:50 +0200
Re: Why does resolv.conf keep changing? David Wright <deblis@lionunicorn.co.uk> - 2017-10-26 16:40 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-26 17:00 +0200
Re: Why does resolv.conf keep changing? Mart van de Wege <mvdwege@gmail.com> - 2017-10-27 10:10 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-27 13:50 +0200
Re: Why does resolv.conf keep changing? Darac Marjal <mailinglist@darac.org.uk> - 2017-10-27 14:20 +0200
Re: Why does resolv.conf keep changing? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-27 14:40 +0200
Re: Why does resolv.conf keep changing? David Wright <deblis@lionunicorn.co.uk> - 2017-10-27 20:50 +0200
Re: Why does resolv.conf keep changing? David Wright <deblis@lionunicorn.co.uk> - 2017-10-27 20:50 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-27 16:20 +0200
Re: Why does resolv.conf keep changing? Mart van de Wege <mvdwege@gmail.com> - 2017-10-28 00:10 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-28 00:10 +0200
Re: Why does resolv.conf keep changing? David Wright <deblis@lionunicorn.co.uk> - 2017-10-28 02:00 +0200
Re: Why does resolv.conf keep changing? Mart van de Wege <mvdwege@gmail.com> - 2017-10-28 15:30 +0200
Re: Why does resolv.conf keep changing? Glenn English <ghe2001@gmail.com> - 2017-10-28 18:50 +0200
Re: Why does resolv.conf keep changing? Mart van de Wege <mvdwege@gmail.com> - 2017-10-28 15:40 +0200
Re: Why does resolv.conf keep changing? Stefan Monnier <monnier@iro.umontreal.ca> - 2017-10-27 16:40 +0200
Re: Why does resolv.conf keep changing? Mart van de Wege <mvdwege@gmail.com> - 2017-10-28 00:10 +0200
Re: Why does resolv.conf keep changing? Stefan Monnier <monnier@iro.umontreal.ca> - 2017-10-27 16:30 +0200
Re: Why does resolv.conf keep changing? Michael Stone <mstone@debian.org> - 2017-10-28 02:40 +0200
Re: Why does resolv.conf keep changing? Stefan Monnier <monnier@iro.umontreal.ca> - 2017-10-26 14:40 +0200
Re: Why does resolv.conf keep changing? Roger Lynn <Roger@rilynn.me.uk> - 2017-11-04 00:30 +0100
Re: Why does resolv.conf keep changing? <tomas@tuxteam.de> - 2017-11-04 08:50 +0100
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-11-04 13:10 +0100
Re: Why does resolv.conf keep changing? Brian <ad44@cityscape.co.uk> - 2017-11-04 22:00 +0100
Re: Why does resolv.conf keep changing? <tomas@tuxteam.de> - 2017-11-04 22:10 +0100
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-11-04 22:10 +0100
Re: Why does resolv.conf keep changing? Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-11-04 15:40 +0100
Re: Why does resolv.conf keep changing? Greg Wooledge <wooledg@eeg.ccf.org> - 2017-10-26 15:30 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-25 15:30 +0200
Re: Why does resolv.conf keep changing? Gene Heskett <gheskett@shentel.net> - 2017-10-25 15:00 +0200
Re: Why does resolv.conf keep changing? Stefan Monnier <monnier@iro.umontreal.ca> - 2017-10-25 15:30 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-25 15:10 +0200
Re: Why does resolv.conf keep changing? Stefan Monnier <monnier@iro.umontreal.ca> - 2017-10-25 15:30 +0200
Re: Why does resolv.conf keep changing? Roberto C. Sánchez <roberto@debian.org> - 2017-10-25 16:20 +0200
Page 3 of 7 — ← Prev page 1 2 [3] 4 5 6 7 Next page →
| From | tomas@tuxteam.de |
|---|---|
| Date | 2017-10-25 14:20 +0200 |
| Message-ID | <uEsP8-8e8-15@gated-at.bofh.it> |
| In reply to | #188270 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Oct 25, 2017 at 02:11:21PM +0200, Nicolas George wrote: > Le quartidi 4 brumaire, an CCXXVI, tomas@tuxteam.de a écrit : > > If I give an > > FQDN (e.g. duckduckgo.com), the dots in the host name tell the resolver > > to bypass the search list. > > You are wrong on this particular point. If the host name contains dots, > it changes the behaviour of the resolver by having it try the bare > domain first, but then it will try the search list too. Right. Thanks for that correction. Still: the mentioned entry should probably not be in resolv.conf, right? Cheers - -- t -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlnwgPMACgkQBcgs9XrR2kb8RACeM9z7A5PrtNXA+0DFyexhLm3u C2YAnjRncPz9orQsom9AsD4O4R6YXo20 =+XfG -----END PGP SIGNATURE-----
[toc] | [prev] | [next] | [standalone]
| From | Nicolas George <george@nsup.org> |
|---|---|
| Date | 2017-10-25 14:50 +0200 |
| Message-ID | <uEsP8-8e8-17@gated-at.bofh.it> |
| In reply to | #188270 |
[Multipart message — attachments visible in raw view] — view raw
Le quartidi 4 brumaire, an CCXXVI, tomas@tuxteam.de a écrit : > If I give an > FQDN (e.g. duckduckgo.com), the dots in the host name tell the resolver > to bypass the search list. You are wrong on this particular point. If the host name contains dots, it changes the behaviour of the resolver by having it try the bare domain first, but then it will try the search list too. You can check the behaviour using, for example, the following command line: strace -e sendmmsg -f -s 1024 socat - tcp:doesnotexist.example:80 |& grep --color doesnotexist With just "doesnotexist", I can see the requests: doesnotexist.first.search.domain doesnotexist.second.search.domain doesnotexist With doesnotexist.example (or .example.com), the requests are: doesnotexist.example doesnotexist.example.first.search.domain doesnotexist.example.second.search.domain To inhibit searching in the specified domain, the syntax requires a final dot: "doesnotexist." or "doesnotexist.example.com.". It is a little known fact that the dot in DNS domain names is not a separator but a terminator, and when it is missing it means a possible ellipsis. Regards, -- Nicolas George
[toc] | [prev] | [next] | [standalone]
| From | Joe <joe@jretrading.com> |
|---|---|
| Date | 2017-10-25 14:10 +0200 |
| Message-ID | <uEsFr-8aT-11@gated-at.bofh.it> |
| In reply to | #188267 |
On Wed, 25 Oct 2017 07:35:35 -0400 Gene Heskett <gheskett@shentel.net> wrote: > > Whereas my theory has always been WRT the search line, that it should > first search the /etc/hosts file for a name match, and failing that, > query my router, which is running dd-wrt which means its running > dnsmasq. > Yes, but that information (among other stuff) lives in /etc/nsswitch.conf, not /etc/resolv.conf. Keep up at the back: why use one configuration file when a couple of dozen will easily do the job? -- Joe
[toc] | [prev] | [next] | [standalone]
| From | <tomas@tuxteam.de> |
|---|---|
| Date | 2017-10-25 14:20 +0200 |
| Message-ID | <uEsP8-8e8-7@gated-at.bofh.it> |
| In reply to | #188272 |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Oct 25, 2017 at 01:06:37PM +0100, Joe wrote: > On Wed, 25 Oct 2017 07:35:35 -0400 > Gene Heskett <gheskett@shentel.net> wrote: > > > > > > Whereas my theory has always been WRT the search line, that it should > > first search the /etc/hosts file for a name match, and failing that, > > query my router, which is running dd-wrt which means its running > > dnsmasq. > > > > Yes, but that information (among other stuff) lives in > /etc/nsswitch.conf, not /etc/resolv.conf. > > Keep up at the back: why use one configuration file when a couple of > dozen will easily do the job? To be fair, those two do quite different things. The one is the configuration for the (host name) resolver, whereas the other is a configuration for generic name services (which encompasses many other things, like user names, protocol names... you name it). So nsswitch is "outside" as seen by the resolver. Of course, one might envision one highly-integrated naming service doing "all of that", and that was probably Sun's original vision. But things like the DNS are complex (and important) enough that they develop a life of their own. The usual balance between integration and granularity which makes the engineer's bread and butter, I guess. Cheers - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlnwgKYACgkQBcgs9XrR2kYKbACeKWCV5QhtzpCArz4HLTmzN7ig vYcAnitmadGQZqfCuwvbg14uBlcgj2hm =jnSe -----END PGP SIGNATURE-----
[toc] | [prev] | [next] | [standalone]
| From | Joe <joe@jretrading.com> |
|---|---|
| Date | 2017-10-25 15:00 +0200 |
| Message-ID | <uEtrQ-8qX-13@gated-at.bofh.it> |
| In reply to | #188273 |
On Wed, 25 Oct 2017 14:16:38 +0200 <tomas@tuxteam.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Wed, Oct 25, 2017 at 01:06:37PM +0100, Joe wrote: > > On Wed, 25 Oct 2017 07:35:35 -0400 > > Gene Heskett <gheskett@shentel.net> wrote: > > > > > > > > > > Whereas my theory has always been WRT the search line, that it > > > should first search the /etc/hosts file for a name match, and > > > failing that, query my router, which is running dd-wrt which > > > means its running dnsmasq. > > > > > > > Yes, but that information (among other stuff) lives in > > /etc/nsswitch.conf, not /etc/resolv.conf. > > > > Keep up at the back: why use one configuration file when a couple of > > dozen will easily do the job? > > To be fair, those two do quite different things. The one is the > configuration for the (host name) resolver, whereas the other is > a configuration for generic name services (which encompasses many > other things, like user names, protocol names... you name it). > So nsswitch is "outside" as seen by the resolver. As I suggested with '(among other stuff)'. > > Of course, one might envision one highly-integrated naming service > doing "all of that", and that was probably Sun's original vision. > But things like the DNS are complex (and important) enough that > they develop a life of their own. The perennial question of whether a piece of information involving A and B should be filed under 'A' or under 'B'... I submit that the name resolution of networked hosts has rather more in common with other network parameters than with, for example, which database might be expected to contain user account passwords. -- Joe
[toc] | [prev] | [next] | [standalone]
| From | Dan Ritter <dsr@randomstring.org> |
|---|---|
| Date | 2017-10-25 17:10 +0200 |
| Message-ID | <uEvtD-1pZ-1@gated-at.bofh.it> |
| In reply to | #188267 |
On Wed, Oct 25, 2017 at 07:35:35AM -0400, Gene Heskett wrote: > On Tuesday 24 October 2017 23:46:47 Felix Miata wrote: > > > Gene Heskett composed on 2017-10-24 22:52 (UTC-0400): > > >> On Mon, Oct 23, 2017 at 20:31:05 -0400, Gene Heskett wrote: > > >>>and made immutable. Particularly is the fact that /etc/resolv.conf > > >>> isn't a link to something else but contains: > > >>> > > >>>nameserver 192.168.XX.1 > > >>>search host dns > > >>>domain coyote.den > > > > ... > > Whereas my theory has always been WRT the search line, that it should > first search the /etc/hosts file for a name match, and failing that, > query my router, which is running dd-wrt which means its running > dnsmasq. In order to do that, you want this: in /etc/nsswitch.conf: ... hosts: files dns ... Which is the standard for Debian and basically all other Linux distros that I know about. That tells the DNS resolver to look at /etc/hosts first, and then make a DNS query if /etc/hosts does not have an answer. Note that isn't in resolv.conf, it's in nsswitch.conf. -dsr-
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2017-10-25 18:50 +0200 |
| Message-ID | <uEx2p-2cn-1@gated-at.bofh.it> |
| In reply to | #188299 |
On Wednesday 25 October 2017 11:05:28 Dan Ritter wrote: > On Wed, Oct 25, 2017 at 07:35:35AM -0400, Gene Heskett wrote: > > On Tuesday 24 October 2017 23:46:47 Felix Miata wrote: > > > Gene Heskett composed on 2017-10-24 22:52 (UTC-0400): > > > >> On Mon, Oct 23, 2017 at 20:31:05 -0400, Gene Heskett wrote: > > > >>>and made immutable. Particularly is the fact that > > > >>> /etc/resolv.conf isn't a link to something else but contains: > > > >>> > > > >>>nameserver 192.168.XX.1 > > > >>>search host dns > > > >>>domain coyote.den > > > > > > ... > > > > Whereas my theory has always been WRT the search line, that it > > should first search the /etc/hosts file for a name match, and > > failing that, query my router, which is running dd-wrt which means > > its running dnsmasq. > > In order to do that, you want this: > > in /etc/nsswitch.conf: > ... > hosts: files dns > ... > > Which is the standard for Debian and basically all other Linux > distros that I know about. > > That tells the DNS resolver to look at /etc/hosts first, and > then make a DNS query if /etc/hosts does not have an answer. > > Note that isn't in resolv.conf, it's in nsswitch.conf. > > -dsr- And mine gives more choices yet. :) hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Don Armstrong <don@debian.org> |
|---|---|
| Date | 2017-10-25 21:30 +0200 |
| Message-ID | <uEzxf-3RG-9@gated-at.bofh.it> |
| In reply to | #188267 |
On Wed, 25 Oct 2017, Gene Heskett wrote: > Whereas my theory has always been WRT the search line, that it should > first search the /etc/hosts file for a name match, and failing that, > query my router, which is running dd-wrt which means its running > dnsmasq. This is wrong, and has been wrong for quite some time. /etc/resolv.conf does not control the order of querying. /etc/nsswitch.conf does. See nsswitch.conf(5) and resolv.conf(5) for details. -- Don Armstrong https://www.donarmstrong.com There is no mechanical problem so difficult that it cannot be solved by brute strength and ignorance. -- William's Law
[toc] | [prev] | [next] | [standalone]
| From | Michael Stone <mstone@debian.org> |
|---|---|
| Date | 2017-10-25 13:40 +0200 |
| Message-ID | <uEscq-7LE-7@gated-at.bofh.it> |
| In reply to | #188259 |
On Tue, Oct 24, 2017 at 11:46:47PM -0400, Felix Miata wrote: >2-My lines 1 are always the search lines, each starting with the word "search", >followed by domain(s) to be searched, e.g. "search mylan.net coyote.den >someother.biz" [...] >4-I have no lines starting with string "domain", but as a result of this thread, >that may soon change. In general, you should not have a domain line; it has very little purpose these days, and is basically "search" that only allows one search domain. If you have both "domain" and "search" they turn each other off, so only the last one in the file does anything. Mike Stone
[toc] | [prev] | [next] | [standalone]
| From | Glenn English <ghe2001@gmail.com> |
|---|---|
| Date | 2017-10-26 17:40 +0200 |
| Message-ID | <uESqd-76Y-13@gated-at.bofh.it> |
| In reply to | #188254 |
On Wed, Oct 25, 2017 at 1:06 AM, Michael Stone <mstone@debian.org> wrote: > On Mon, Oct 23, 2017 at 08:31:05PM -0400, Gene Heskett wrote: >> >> and made immutable. Particularly is the fact that /etc/resolv.conf isn't >> a link to something else but contains: >> >> nameserver 192.168.XX.1 >> search host dns >> domain coyote.den > > > Please stop posting that, it uses incorrect syntax The 'search host dns' line? How do you set that order? I couldn't find that from a bit of surfing, and I'd like to have name lookups work in that order... And Gene, Removing all write permissions and setting immutable has stopped Comcast from trashing my resolv.conf. This week. Have you looked to see whether the changes are being done by an alien (Comcast) or from inside the host? -- Glenn English
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2017-10-26 17:50 +0200 |
| Message-ID | <uESzT-7a3-3@gated-at.bofh.it> |
| In reply to | #188347 |
On Thu, Oct 26, 2017 at 03:35:06PM +0000, Glenn English wrote: > The 'search host dns' line? How do you set that order? I couldn't find > that from a bit of surfing, and I'd like to have name lookups work in > that order... Gene's resolv.conf has this erroneous line that he has been maintaining for decades. It does not do what he thinks it does. If you want to control the order of name lookup sources, that goes in the /etc/nsswitch.conf file, as described in "man nsswitch.conf".
[toc] | [prev] | [next] | [standalone]
| From | The Wanderer <wanderer@fastmail.fm> |
|---|---|
| Date | 2017-10-26 18:00 +0200 |
| Message-ID | <uESJz-7dk-1@gated-at.bofh.it> |
| In reply to | #188347 |
[Multipart message — attachments visible in raw view] — view raw
On 2017-10-26 at 11:35, Glenn English wrote: > On Wed, Oct 25, 2017 at 1:06 AM, Michael Stone <mstone@debian.org> wrote: > >> On Mon, Oct 23, 2017 at 08:31:05PM -0400, Gene Heskett wrote: >>> >>> and made immutable. Particularly is the fact that /etc/resolv.conf isn't >>> a link to something else but contains: >>> >>> nameserver 192.168.XX.1 >>> search host dns >>> domain coyote.den >> >> Please stop posting that, it uses incorrect syntax > > The 'search host dns' line? How do you set that order? I couldn't find > that from a bit of surfing, and I'd like to have name lookups work in > that order... As was explained later on in this thread (and, I presume, would have been explained to Gene previously in other threads), you set that search order in /etc/nsswitch.conf, not in /etc/resolv.conf. 'man nsswitch.conf' documents the file, but all you should probably need to do is look at the existing file, and tweak the 'hosts' line appropriately. If what you want is "search /etc/hosts, then search DNS, then give up", the 'hosts' line you want is: hosts: files dns There are additional options that might make sense, but that's the most basic form. My own nsswitch.conf hosts entry, which IIRC is fairly bog-standard except maybe for a bit of reordering, reads: hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 which, according to my understanding, simply adds a few additional types of DNS lookup into the series before giving up. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
[toc] | [prev] | [next] | [standalone]
| From | Nicholas Geovanis <nickgeovanis@gmail.com> |
|---|---|
| Date | 2017-10-26 18:20 +0200 |
| Message-ID | <uET2W-7yY-7@gated-at.bofh.it> |
| In reply to | #188349 |
[Multipart message — attachments visible in raw view] — view raw
An interesting, accidental FYI on the subject of the resolvconf package: Just now I upgraded an Ubuntu 17.04 test machine which was fully upgraded only ten days ago. I see in the pending upgrade details that resolvconf is "No longer supported by Canonical" since the previous upgrade. On Thu, Oct 26, 2017 at 10:54 AM, The Wanderer <wanderer@fastmail.fm> wrote: > On 2017-10-26 at 11:35, Glenn English wrote: > > > On Wed, Oct 25, 2017 at 1:06 AM, Michael Stone <mstone@debian.org> > wrote: > > > >> On Mon, Oct 23, 2017 at 08:31:05PM -0400, Gene Heskett wrote: > >>> > >>> and made immutable. Particularly is the fact that /etc/resolv.conf > isn't > >>> a link to something else but contains: > >>> > >>> nameserver 192.168.XX.1 > >>> search host dns > >>> domain coyote.den > >> > >> Please stop posting that, it uses incorrect syntax > > > > The 'search host dns' line? How do you set that order? I couldn't find > > that from a bit of surfing, and I'd like to have name lookups work in > > that order... > > As was explained later on in this thread (and, I presume, would have > been explained to Gene previously in other threads), you set that search > order in /etc/nsswitch.conf, not in /etc/resolv.conf. > > 'man nsswitch.conf' documents the file, but all you should probably need > to do is look at the existing file, and tweak the 'hosts' line > appropriately. > > > If what you want is "search /etc/hosts, then search DNS, then give up", > the 'hosts' line you want is: > > hosts: files dns > > There are additional options that might make sense, but that's the most > basic form. > > > My own nsswitch.conf hosts entry, which IIRC is fairly bog-standard > except maybe for a bit of reordering, reads: > > hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 > > which, according to my understanding, simply adds a few additional types > of DNS lookup into the series before giving up. > > -- > The Wanderer > > The reasonable man adapts himself to the world; the unreasonable one > persists in trying to adapt the world to himself. Therefore all > progress depends on the unreasonable man. -- George Bernard Shaw > >
[toc] | [prev] | [next] | [standalone]
| From | Nicholas Geovanis <nickgeovanis@gmail.com> |
|---|---|
| Date | 2017-10-26 18:40 +0200 |
| Message-ID | <uETmi-7Hd-15@gated-at.bofh.it> |
| In reply to | #188350 |
[Multipart message — attachments visible in raw view] — view raw
On Thu, Oct 26, 2017 at 11:13 AM, Nicholas Geovanis <nickgeovanis@gmail.com> wrote: > An interesting, accidental FYI on the subject of the resolvconf package: > Just now I upgraded an Ubuntu 17.04 test machine which was fully upgraded > only ten days ago. I see in the pending upgrade details that resolvconf is > "No longer supported by Canonical" since the previous upgrade. > I should have mentioned that this is the upgrade to Ubuntu 17.10 incoming.
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2017-10-27 02:00 +0200 |
| Message-ID | <uF0e5-3GY-1@gated-at.bofh.it> |
| In reply to | #188350 |
On Thursday 26 October 2017 12:13:57 Nicholas Geovanis wrote: > An interesting, accidental FYI on the subject of the resolvconf > package: Just now I upgraded an Ubuntu 17.04 test machine which was > fully upgraded only ten days ago. I see in the pending upgrade details > that resolvconf is "No longer supported by Canonical" since the > previous upgrade. > Gee, I wonder why, said Gene to no one in particular ;-) > On Thu, Oct 26, 2017 at 10:54 AM, The Wanderer <wanderer@fastmail.fm> wrote: > > On 2017-10-26 at 11:35, Glenn English wrote: > > > On Wed, Oct 25, 2017 at 1:06 AM, Michael Stone <mstone@debian.org> > > > > wrote: > > >> On Mon, Oct 23, 2017 at 08:31:05PM -0400, Gene Heskett wrote: > > >>> and made immutable. Particularly is the fact that > > >>> /etc/resolv.conf > > > > isn't > > > > >>> a link to something else but contains: > > >>> > > >>> nameserver 192.168.XX.1 > > >>> search host dns > > >>> domain coyote.den > > >> > > >> Please stop posting that, it uses incorrect syntax > > > > > > The 'search host dns' line? How do you set that order? I couldn't > > > find that from a bit of surfing, and I'd like to have name lookups > > > work in that order... > > > > As was explained later on in this thread (and, I presume, would have > > been explained to Gene previously in other threads), you set that > > search order in /etc/nsswitch.conf, not in /etc/resolv.conf. > > > > 'man nsswitch.conf' documents the file, but all you should probably > > need to do is look at the existing file, and tweak the 'hosts' line > > appropriately. > > > > > > If what you want is "search /etc/hosts, then search DNS, then give > > up", the 'hosts' line you want is: > > > > hosts: files dns > > > > There are additional options that might make sense, but that's the > > most basic form. > > > > > > My own nsswitch.conf hosts entry, which IIRC is fairly bog-standard > > except maybe for a bit of reordering, reads: > > > > hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 > > > > which, according to my understanding, simply adds a few additional > > types of DNS lookup into the series before giving up. > > > > -- > > The Wanderer > > > > The reasonable man adapts himself to the world; the unreasonable one > > persists in trying to adapt the world to himself. Therefore all > > progress depends on the unreasonable man. -- George Bernard > > Shaw Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2017-10-27 02:00 +0200 |
| Message-ID | <uF0e6-3GY-3@gated-at.bofh.it> |
| In reply to | #188347 |
On Thursday 26 October 2017 11:35:06 Glenn English wrote: > On Wed, Oct 25, 2017 at 1:06 AM, Michael Stone <mstone@debian.org> wrote: > > On Mon, Oct 23, 2017 at 08:31:05PM -0400, Gene Heskett wrote: > >> and made immutable. Particularly is the fact that /etc/resolv.conf > >> isn't a link to something else but contains: > >> > >> nameserver 192.168.XX.1 > >> search host dns > >> domain coyote.den > > > > Please stop posting that, it uses incorrect syntax > > The 'search host dns' line? How do you set that order? I couldn't find > that from a bit of surfing, and I'd like to have name lookups work in > that order... > That is under the keyword 'search' in the man page, where the confusion is about what to put there stems from the rest of that stanza. It obtuse and clueless except for a later statement the says search and domain are mutually exclusive, using the last option found. As to what you put in the search line, I haven't a clue. I modified mine to: nameserver 192.168.XX.1 search coyote.den nameserver And ANAICT it made zero difference as it still Just Works(TM). Someone else has pointed out that this is actually controlled by nsswitch.conf, which contains: # /etc/nsswitch.conf # # Example configuration of GNU Name Service Switch functionality. # If you have the `glibc-doc-reference' and `info' packages installed, try: # `info libc "Name Service Switch"' for information about this file. passwd: compat group: compat shadow: compat hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 networks: files protocols: db files services: db files ethers: db files rpc: db files netgroup: nis And while I'd not call that man page language swahili, it may be slightly better than the man page for resolv.conf. The operative line above may be the "hosts:" line. I'll leave the study of that man page for those search for a solution to a problem they are having. I'll note that the debian wheezy supplied file is quite heavily modified when compared to the example file in that man page. But no clue as to what problems the modifications are intended to fix. There may be more info in the ChangeLog.gz for these two files. I know roughly where those are, but have been up to my eyeballs in a 60 yo 1kw Gates am radio transmitter the last 2 days, and out of this loop. The real secret here is that I am of a dying breed in the broadcast world, I am one of the folks who actually go on call to fix things like transmitters. Most field engineers just pick up the phone and order a new one, for anything from 10G's for a 50 watt nighttime transmitter, to a couple million $ for a modern digital tv transmitter. This one has quite extensive damage to the audio driver pcb brought on by it being on a phenolic substrate, and the OEM solder was the same stuff RCA used in their TV's circa 1953-54. Darned near pure lead with a need to be heated and diluted with more modern, 250F lower melting temp solder before it can be removed to gain access to the component lead, 1/4" of which was bent over, locking it firmly to the board even if the solder was melted. The end result of course is copper traces lifted from the board by the excessive heat and loaded with microscopic cracks. I replaced several old carbon composition resistors that were way out of tolerance, but the final "fix" was a piece of 22 gauge wire connecting the two ends of a trace carrying 500 volt on the theory that if the trace was broken someplace in the middle, it was now being fed on both sides of the break. And it worked. That faint thumping you can hear in the background, is me pecking on wood for good luck. A new circuit board has been checked on, it would have to be made, min order 3 for around $11,000. So we cobble this one up yet one more time. But I'm likely both writing swahili to most of you, and boring the whole list. So I'll STFU. > And Gene, > > Removing all write permissions and setting immutable has stopped > Comcast from trashing my resolv.conf. This week. Probably for a good long time I suspect. > Have you looked to see whether the changes are being done by an alien > (Comcast) or from inside the host? > > -- > Glenn English Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Jörg-Volker Peetz <jvpeetz@web.de> |
|---|---|
| Date | 2017-10-23 12:10 +0200 |
| Message-ID | <uDHQe-4uf-9@gated-at.bofh.it> |
| In reply to | #188193 |
Roberto C. Sánchez wrote on 10/23/17 04:12:
<snip>
> I have tried two different things. First, I added this directive to
> /etc/network/interfaces under the eth0 stanza:
>
> dns-nameservers 127.0.0.1
>
> That did not appear to have any effect because taking eth0 and eth1 down
> and then bringing them back up still results in resolv.conf pointing to
> the ISP router as its name server. Additionally, after the interfaces
> are up even if I manually change resolv.conf, something comes along
> sometime later and undoes my changes.
On testing with resolvconf the parameter in /etc/network/interfaces is
dns-nameserver 127.0.0.1
without trailing 's'.
Regards,
jvp.
[toc] | [prev] | [next] | [standalone]
| From | Stefan Monnier <monnier@iro.umontreal.ca> |
|---|---|
| Date | 2017-10-25 05:50 +0200 |
| Message-ID | <uEkRA-3e7-7@gated-at.bofh.it> |
| In reply to | #188193 |
> My /etc/resolv.conf looks like this:
> domain example.com
> search example.com.
> nameserver 127.0.0.1
Here's how I'd do it:
- install resolvconf
- move the resolv.conf config you use with bind to somewhere else, like
/etc/resolv.conf.bind
- arrange for the script which starts your `bind` server to do:
resolvconf -a lo.bind </etc/resolv.conf.bind
- furthermore arrange to run
resolvconf -d lo.bind
when bind is stopped.
`resolvconf` is designed to handle situations like these where there are
DNS configs from various places which all fight for the control of
/etc/resolv.conf. The "lo.bind" is the name corresponding more or less
to the interface over which the info is served, and `resolvconf` uses
that info to enforce some priority between the different sources
of info.
With such a setup, your host should correctly use your local `bind`
server, and if you ever stop your `bind` server it should start using
your ISP's server instead. And when you restart your `bind` server, it
will switch back to using that.
Stefan
[toc] | [prev] | [next] | [standalone]
| From | Roberto C. Sánchez <roberto@debian.org> |
|---|---|
| Date | 2017-10-25 06:10 +0200 |
| Message-ID | <uElaV-3zJ-1@gated-at.bofh.it> |
| In reply to | #188260 |
On Tue, Oct 24, 2017 at 11:44:59PM -0400, Stefan Monnier wrote: > > With such a setup, your host should correctly use your local `bind` > server, and if you ever stop your `bind` server it should start using > your ISP's server instead. And when you restart your `bind` server, it > will switch back to using that. > That is not at all what I am trying to accomplish. I simply want resolv.conf to be left alone. As I do not have resolvconf even installed, I don't think I am asking too much. Regards, -Roberto -- Roberto C. Sánchez
[toc] | [prev] | [next] | [standalone]
| From | Stefan Monnier <monnier@iro.umontreal.ca> |
|---|---|
| Date | 2017-10-25 06:50 +0200 |
| Message-ID | <uElNE-3Oz-1@gated-at.bofh.it> |
| In reply to | #188261 |
>> With such a setup, your host should correctly use your local `bind`
>> server, and if you ever stop your `bind` server it should start using
>> your ISP's server instead. And when you restart your `bind` server, it
>> will switch back to using that.
> That is not at all what I am trying to accomplish. I simply want
> resolv.conf to be left alone. As I do not have resolvconf even
> installed, I don't think I am asking too much.
Don't worry, you can ask whatever you want and I won't judge if it's too
much or too little: It's not like I (nor anyone else for that matter)
have to provide you with what you want, anyway.
I just gave you a solution to your underlying problem, which *uses* the
infrastructure rather than fighting it. I won't force you to use it, tho.
Stefan
[toc] | [prev] | [next] | [standalone]
Page 3 of 7 — ← Prev page 1 2 [3] 4 5 6 7 Next page →
Back to top | Article view | linux.debian.user
csiph-web