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


Groups > linux.debian.user > #201792

Re: resolv.conf (was i386 version for chrome)

From Reco <recoverym4n@enotuniq.net>
Newsgroups linux.debian.user
Subject Re: resolv.conf (was i386 version for chrome)
Date 2018-10-28 14:50 +0100
Message-ID <wNTC2-6se-5@gated-at.bofh.it> (permalink)
References (4 earlier) <wNPf4-40u-19@gated-at.bofh.it> <wNRTz-5oE-1@gated-at.bofh.it> <wNSFX-5U3-9@gated-at.bofh.it> <wNT8Z-6iC-3@gated-at.bofh.it> <wNT8Z-6iC-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


	Hi.

On Sun, Oct 28, 2018 at 04:17:17PM +0300, Reco wrote:
> 	Hi.
> 
> On Sun, Oct 28, 2018 at 02:13:30PM +0100, Pierre Frenkiel wrote:
> > On Sun, 28 Oct 2018, Reco wrote:
> > 
> > > strace getent hosts bad.solutions
> > 
> >   thanks for your answer, but the output is rather obscure for a non-guru user,
> >   except a lot of "no such file or directory"
> >   In particular, I don't see how to explain the difference of behaviour on
> >   my 2 computers.
> 
> Not pretending to be a guru, but can you post the results somewhere?

I don't repost those two strace outputs, archives will be better without
them.

The result is somewhat unexpected (to me at least):

Judging from multiple:

stat("/etc/resolv.conf", 0x7ffbffffae40) = -1 ENOENT 

The host's resolver is configured for conventional DNS resolution.

/etc/resolv.conf is not present, so resolver tries to find DNS at
127.0.0.1 udp:53:

connect(3, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("127.0.0.1")}, 16) = 0

Which it does (zero return code), and sends DNS query there:

sendto(3, "\307N\1\0\0\1\0\0\0\0\0\0\3bad\tsolutions\0\0\34\0\1", 31, MSG_NOSIGNAL, NULL, 0) = 31

And something that's listening udp:53 on your laptop replies:

recvfrom(3, "\307N\201\200\0\1\0\0\0\1\0\0\3bad\tsolutions\0\0\34\0\1\300"..., 1024, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("127.0.0.1")}, [28->16]) = 91


The fact that libc's resolver have a hardcoded fallback to localhost in
the absense of resolv.conf was not known to me until now, but it's
documented at resolv.conf(5):

If  this  file  does  not exist, only the name server on the local
machine will be queried


So, answering your original question, you have working name resolution
because you have a caching nameserver on your laptop. My money's on
dnsmasq.

Reco

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

i386 version for chrome Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-27 10:30 +0200
  Re: i386 version for chrome Andrew Wood <andrewjameswood@ymail.com> - 2018-10-27 10:40 +0200
    Re: i386 version for chrome Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-27 12:40 +0200
      Re: i386 version for chrome Roberto C. Sánchez <roberto@debian.org> - 2018-10-27 13:10 +0200
        Re: i386 version for chrome Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-27 13:30 +0200
          Re: i386 version for chrome Curt <curty@free.fr> - 2018-10-27 14:10 +0200
            Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-27 15:10 +0200
              Re: i386 version for chrome Curt <curty@free.fr> - 2018-10-27 16:10 +0200
                Re: i386 version for chrome Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-27 17:00 +0200
                Re: i386 version for chrome Curt <curty@free.fr> - 2018-10-27 18:00 +0200
                Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-27 17:00 +0200
                Re: i386 version for chrome Steve McIntyre <steve@einval.com> - 2018-10-27 17:20 +0200
                Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-27 19:20 +0200
                Re: i386 version for chrome Steve McIntyre <steve@einval.com> - 2018-10-27 20:30 +0200
                Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-27 23:30 +0200
                Re: i386 version for chrome Brian <ad44@cityscape.co.uk> - 2018-10-28 00:50 +0200
                Re: i386 version for chrome David <bouncingcats@gmail.com> - 2018-10-28 00:30 +0200
                Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 01:00 +0200
                Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 01:00 +0200
                Re: i386 version for chrome David <bouncingcats@gmail.com> - 2018-10-28 23:00 +0100
                Re: i386 version for chrome Curt <curty@free.fr> - 2018-10-28 10:10 +0100
                Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 12:00 +0100
                Re: i386 version for chrome Curt <curty@free.fr> - 2018-10-29 12:00 +0100
                resolv.conf (was i386 version for chrome) Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-28 13:00 +0100
                Re: resolv.conf (was i386 version for chrome) Reco <recoverym4n@enotuniq.net> - 2018-10-28 13:50 +0100
                Re: resolv.conf (was i386 version for chrome) Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-28 14:20 +0100
                Re: resolv.conf (was i386 version for chrome) Reco <recoverym4n@enotuniq.net> - 2018-10-28 14:20 +0100
                Re: resolv.conf (was i386 version for chrome) Reco <recoverym4n@enotuniq.net> - 2018-10-28 14:50 +0100
                Re: resolv.conf (was i386 version for chrome) Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-28 16:40 +0100
                Re: i386 version for chrome Steve McIntyre <steve@einval.com> - 2018-10-28 01:00 +0200
                Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-28 16:00 +0100
                Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 17:20 +0100
                Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-29 11:30 +0100
                Re: i386 version for chrome Reco <recoverym4n@enotuniq.net> - 2018-10-27 20:40 +0200
                Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-27 23:40 +0200
                Re: i386 version for chrome Reco <recoverym4n@enotuniq.net> - 2018-10-28 08:00 +0100
                Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 11:10 +0100
                Re: i386 version for chrome Reco <recoverym4n@enotuniq.net> - 2018-10-28 11:40 +0100
                Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 12:10 +0100
                Re: i386 version for chrome Reco <recoverym4n@enotuniq.net> - 2018-10-28 13:50 +0100
                Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 17:10 +0100
                Re: i386 version for chrome Reco <recoverym4n@enotuniq.net> - 2018-10-28 17:30 +0100
                Re: i386 version for chrome The Wanderer <wanderer@fastmail.fm> - 2018-10-28 18:00 +0100
                Re: i386 version for chrome john doe <johndoe65534@mail.com> - 2018-10-28 18:10 +0100
                Re: i386 version for chrome Reco <recoverym4n@enotuniq.net> - 2018-10-28 18:20 +0100
                Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-29 12:20 +0100
                Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-29 13:30 +0100
                Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-29 13:40 +0100
                Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-29 14:00 +0100
                Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-29 15:50 +0100
                Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-29 15:50 +0100
                Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-29 16:10 +0100
                Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-29 21:20 +0100
                Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-29 21:20 +0100
                Re: i386 version for chrome John Hasler <jhasler@newsguy.com> - 2018-10-29 21:30 +0100
                Re: i386 version for chrome Brian <ad44@cityscape.co.uk> - 2018-10-29 21:40 +0100
                Re: i386 version for chrome Brian <ad44@cityscape.co.uk> - 2018-10-29 21:50 +0100
                Re: i386 version for chrome Brian <ad44@cityscape.co.uk> - 2018-10-28 20:00 +0100
                Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 20:10 +0100
                Re: i386 version for chrome Brian <ad44@cityscape.co.uk> - 2018-10-28 20:30 +0100
                Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-29 00:40 +0100
                Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-29 12:20 +0100
                Re: i386 version for chrome Thomas D Dial <tdial@acm.org> - 2018-10-28 04:10 +0100
                Re: i386 version for chrome Michael Stone <mstone@debian.org> - 2018-10-28 15:50 +0100
                Re: i386 version for chrome Matthew Crews <mailinglists@mattcrews.com> - 2018-10-27 17:10 +0200
                Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-27 17:40 +0200
                Re: i386 version for chrome Matthew Crews <mailinglists@mattcrews.com> - 2018-10-27 22:00 +0200
                Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-10-28 00:10 +0200
                Re: i386 version for chrome David Wright <deblis@lionunicorn.co.uk> - 2018-11-03 04:10 +0100
                Re: i386 version for chrome Gene Heskett <gheskett@shentel.net> - 2018-11-03 04:40 +0100
          Re: i386 version for chrome tony <lists@vanderhoff.org> - 2018-10-27 15:10 +0200
  Re: i386 version for chrome Matthew Crews <mailinglists@mattcrews.com> - 2018-10-27 13:50 +0200
    Re: i386 version for chrome Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2018-10-27 14:50 +0200

csiph-web