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

Groups > linux.debian.user > #265774

Re: Temporary failure in name resolution

Show all headers | View raw

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

On Wed, Jan 10, 2024 at 07:19:41PM +0000, Rodolfo Medina wrote:
> Greg Wooledge <greg@wooledge.org> writes:
> 
> > On Wed, Jan 10, 2024 at 06:34:53PM +0000, Rodolfo Medina wrote:
> >> <tomas@tuxteam.de> writes:
> >> > Where/how does this error message "appear"?
> >> 
> >> As an output of the `startx' command.
> >
> > It would be lovely to see the *entire* error message, in case some part
> > of it identifies the program that produced the error.  Many messages do.
> 
> 
> /etc/resolv.conf is there again (the system created it) but the error message
> does not seem to occur any more.  Even if it occurred again, I have no way to
> fetch it, cause it appears (it used to) at login.

I think this is it (all other advice in this thread about getting
/etc/hosts in order is not bad, but I think it wasn't your problem).

"The system" as you put it is probably dhcpd (or its systemd
cousin, whatever that's called these days). When it goes to
fetch an IP address, it also gets an address or two for the
local name servers, which it puts [1] in /etc/resolv.conf

I guess for some reason there was a stale entry there which
wasn't removed when you lost connectivity.

Cheers

[1] with some indirection or two, e.g. resolvconf
-- 
t

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

Thread

Temporary failure in name resolution Rodolfo Medina <rodolfo.medina@gmail.com> - 2024-01-10 19:20 +0100
  Re: Temporary failure in name resolution <tomas@tuxteam.de> - 2024-01-10 19:30 +0100
    Re: Temporary failure in name resolution Rodolfo Medina <rodolfo.medina@gmail.com> - 2024-01-10 19:40 +0100
      Re: Temporary failure in name resolution Greg Wooledge <greg@wooledge.org> - 2024-01-10 19:50 +0100
        Re: Temporary failure in name resolution Rodolfo Medina <rodolfo.medina@gmail.com> - 2024-01-10 20:30 +0100
          Re: Temporary failure in name resolution Marco Moock <mm@dorfdsl.de> - 2024-01-10 20:30 +0100
          Re: Temporary failure in name resolution Greg Wooledge <greg@wooledge.org> - 2024-01-10 21:30 +0100
            Re: Temporary failure in name resolution Max Nikulin <manikulin@gmail.com> - 2024-01-11 04:20 +0100
              Re: Temporary failure in name resolution Greg Wooledge <greg@wooledge.org> - 2024-01-11 04:30 +0100
                Re: Temporary failure in name resolution Max Nikulin <manikulin@gmail.com> - 2024-01-12 04:10 +0100
              Re: Temporary failure in name resolution David Wright <deblis@lionunicorn.co.uk> - 2024-01-11 06:00 +0100
              Re: Temporary failure in name resolution Curt <curty@free.fr> - 2024-01-11 17:40 +0100
                Re: Temporary failure in name resolution Marco Moock <mm@dorfdsl.de> - 2024-01-11 18:10 +0100
                Re: Temporary failure in name resolution debian-user@howorth.org.uk - 2024-01-12 12:30 +0100
                Re: Temporary failure in name resolution Byung-Hee HWANG <soyeomul@doraji.xyz> - 2024-01-12 14:10 +0100
                Re: Temporary failure in name resolution Curt <curty@free.fr> - 2024-01-12 17:10 +0100
                Re: Temporary failure in name resolution Jeffrey Walton <noloader@gmail.com> - 2024-01-12 17:30 +0100
                Re: Temporary failure in name resolution Jeffrey Walton <noloader@gmail.com> - 2024-01-12 18:40 +0100
                Re: Temporary failure in name resolution debian-user@howorth.org.uk - 2024-01-12 18:40 +0100
                Re: Temporary failure in name resolution John Hasler <john@sugarbit.com> - 2024-01-12 20:50 +0100
                Re: Temporary failure in name resolution debian-user@howorth.org.uk - 2024-01-12 19:20 +0100
          Re: Temporary failure in name resolution <tomas@tuxteam.de> - 2024-01-11 06:30 +0100

csiph-web