Re: Temporary failure in name resolution

+ > 2024-03-06T14:58:11.724851+05:30 hostname-shaheena ntpd[35823]: DNS: > dns_check: DNS error: -3, Temporary failure in name resolution > 2024-03-06T14:58:11.724862+05:30 hostname-shaheena ntpd[35823]: DNS: > dns_take_status: None=>temp, 3 > 2024-03-06T14:58:19.572547+0

Temporary failure in name resolution

ntpd[35823]: DNS: dns_check: DNS error: -3, Temporary failure in name resolution 2024-03-06T14:58:11.724862+05:30 hostname-shaheena ntpd[35823]: DNS: dns_take_status: None=>temp, 3 2024-03-06T14:58:19.572547+05:30 hostname-shaheena ntpd[35823]: DNS: dns_probe: None, cast_flags:1, flags:20801 2024

Re: Temporary failure in name resolution

Curt writes: > Yet the reserved gTLDs from the 2018 ICANN resolution are .home, .corp, > and .mail. Does home.arpa comply with that resolution? Yes. Turns out that there were existing uses of '.home'. Also, putting it under 'arpa.' puts it under IETF control.

Re: Temporary failure in name resolution

Curt wrote: > On 2024-01-12, debian-u...@howorth.org.uk > wrote: > > Curt wrote: > >> On 2024-01-11, Max Nikulin wrote: > >> > > >> > There was a thread that "home" as the top level domain might not > >> > be really safe (somebody might register it). A reserved domain > >> > is "home.arpa"

Re: Temporary failure in name resolution

On Fri, Jan 12, 2024 at 12:33 PM wrote: > > Jeffrey Walton wrote: > > On Fri, Jan 12, 2024 at 11:08 AM Curt wrote: > > > > > > On 2024-01-12, debian-u...@howorth.org.uk > > > wrote: > > > > Curt wrote: > > > >> On 2024-01-11, Max Nikulin wrote: > > > >> > > > > >> > There was a thread that

Re: Temporary failure in name resolution

Jeffrey Walton wrote: > On Fri, Jan 12, 2024 at 11:08 AM Curt wrote: > > > > On 2024-01-12, debian-u...@howorth.org.uk > > wrote: > > > Curt wrote: > > >> On 2024-01-11, Max Nikulin wrote: > > >> > > > >> > There was a thread that "home" as the top level domain might > > >> > not be

Re: Temporary failure in name resolution

On Fri, Jan 12, 2024 at 11:08 AM Curt wrote: > > On 2024-01-12, debian-u...@howorth.org.uk wrote: > > Curt wrote: > >> On 2024-01-11, Max Nikulin wrote: > >> > > >> > There was a thread that "home" as the top level domain might not be > >> > really safe (somebody might register it). A reserved

Re: Temporary failure in name resolution

On 2024-01-12, debian-u...@howorth.org.uk wrote: > Curt wrote: >> On 2024-01-11, Max Nikulin wrote: >> > >> > There was a thread that "home" as the top level domain might not be >> > really safe (somebody might register it). A reserved domain is >> > "home.arpa" so e.g. to have "thinkpad",

Re: Temporary failure in name resolution

On Fri, Jan 12, 2024 at 11:24:53AM +, debian-u...@howorth.org.uk wrote: > Curt wrote: > > On 2024-01-11, Max Nikulin wrote: > > > > > > There was a thread that "home" as the top level domain might not be > > > really safe (somebody might register it). A reserved domain is > > > "home.arpa"

Re: Temporary failure in name resolution

Curt wrote: > On 2024-01-11, Max Nikulin wrote: > > > > There was a thread that "home" as the top level domain might not be > > really safe (somebody might register it). A reserved domain is > > "home.arpa" so e.g. to have "thinkpad", the /etc/hosts entry should > > be > > > > 127.0.1.1

Re: Temporary failure in name resolution

On 11/01/2024 10:19, Greg Wooledge wrote: On Thu, Jan 11, 2024 at 10:10:43AM +0700, Max Nikulin wrote: On 11/01/2024 03:25, Greg Wooledge wrote: On Wed, Jan 10, 2024 at 07:19:41PM +, Rodolfo Medina wrote: Greg Wooledge writes: What is the output of "grep -F $(hostname) /etc/hosts"?

Re: Temporary failure in name resolution

Am 11.01.2024 um 16:34:01 Uhr schrieb Curt: > On 2024-01-11, Max Nikulin wrote: > > > > There was a thread that "home" as the top level domain might not be > > really safe (somebody might register it). A reserved domain is > > "home.arpa" so e.g. to have "thinkpad", the /etc/hosts entry should

Re: Temporary failure in name resolution

On 2024-01-11, Max Nikulin wrote: > > There was a thread that "home" as the top level domain might not be > really safe (somebody might register it). A reserved domain is > "home.arpa" so e.g. to have "thinkpad", the /etc/hosts entry should be > > 127.0.1.1 thinkpad.home.arpa thinkpad >

Re: Temporary failure in name resolution

On Wed, Jan 10, 2024 at 07:19:41PM +, Rodolfo Medina wrote: > Greg Wooledge writes: > > > On Wed, Jan 10, 2024 at 06:34:53PM +, Rodolfo Medina wrote: > >> writes: > >> > Where/how does this error message "appear"? > >> > >> As an output of the `startx' command. > > > > It would be

Re: Temporary failure in name resolution

On Thu 11 Jan 2024 at 10:10:43 (+0700), Max Nikulin wrote: > There was a thread that "home" as the top level domain might not be > really safe (somebody might register it). A reserved domain is > "home.arpa" so e.g. to have "thinkpad", the /etc/hosts entry should be > > 127.0.1.1

Re: Temporary failure in name resolution

On Thu, Jan 11, 2024 at 10:10:43AM +0700, Max Nikulin wrote: > On 11/01/2024 03:25, Greg Wooledge wrote: > > On Wed, Jan 10, 2024 at 07:19:41PM +, Rodolfo Medina wrote: > > > Greg Wooledge writes: > > > > What is the output of the "hostname" command? > > > > > > It's: `thinkpad'. > > > > >

Re: Temporary failure in name resolution

On 11/01/2024 03:25, Greg Wooledge wrote: On Wed, Jan 10, 2024 at 07:19:41PM +, Rodolfo Medina wrote: Greg Wooledge writes: What is the output of the "hostname" command? It's: `thinkpad'. What is the output of "grep -F $(hostname) /etc/hosts"? 127.0.1.1

Re: Temporary failure in name resolution

On Wed, Jan 10, 2024 at 07:19:41PM +, Rodolfo Medina wrote: > Greg Wooledge writes: > > What is the output of the "hostname" command? > > It's: `thinkpad'. > > > What is the output of "grep -F $(hostname) /etc/hosts"? > > It's: > > 127.0.1.1 caterina-thinkpad.home

Re: Temporary failure in name resolution

Am 10.01.2024 um 19:19:41 Uhr schrieb Rodolfo Medina: > > What is the output of "grep -F $(hostname) /etc/hosts"? > > It's: > > 127.0.1.1 caterina-thinkpad.home caterina-thinkpad Add ::1 localhost localhost.localdomain ip6-localhost ip6-loopback 127.0.0.1 localhost

Re: Temporary failure in name resolution

Greg Wooledge writes: > On Wed, Jan 10, 2024 at 06:34:53PM +, Rodolfo Medina wrote: >> 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

Re: Temporary failure in name resolution

On Wed, Jan 10, 2024 at 06:34:53PM +, Rodolfo Medina wrote: > 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

Re: Temporary failure in name resolution

writes: > On Wed, Jan 10, 2024 at 06:13:55PM +, Rodolfo Medina wrote: >> Debian 12 on Thinkpad T450s. >> >> The error message `Temporary failure in name resolution' appears whenever I >> log into X with `startx' at prompt after boot, but it *only* occurs if t

Re: Temporary failure in name resolution

On Wed, Jan 10, 2024 at 06:13:55PM +, Rodolfo Medina wrote: > Debian 12 on Thinkpad T450s. > > The error message `Temporary failure in name resolution' appears whenever I > log > into X with `startx' at prompt after boot, but it *only* occurs if the PC is > *not* con

Temporary failure in name resolution

Debian 12 on Thinkpad T450s. The error message `Temporary failure in name resolution' appears whenever I log into X with `startx' at prompt after boot, but it *only* occurs if the PC is *not* connected to internet; otherwise it does not appear; nevertheless, it annoys me and I wish to get rid

Re: Temporary failure in name resolution error when I try to ping Debian 12 / DomU running on top of the Devuan 5 host os / Dom0

id_lft forever preferred_lft forever >inet6 ::1/128 scope host noprefixroute > valid_lft forever preferred_lft forever > > 2: sit0@NONE: mtu 1480 qdisc noop state DOWN group default qlen > 1000 >link/sit 0.0.0.0 brd 0.0.0.0 > > 3: enX0: mtu 1500 qdisc > pfifo_fast state UP group default > qlen 1000 >link/ether 00:16:3e:12:34:56 brd ff:ff:ff:ff:ff:ff >inet 192.168.1.10/24 brd 192.168.1.255 scope global enX0 > valid_lft forever preferred_lft forever >inet6 fe80::216:3eff:fe12:3456/64 scope link > valid_lft forever preferred_lft forever > > root@bookworm:~# ping google.it > ping: google.it: Temporary failure in name resolution > > > Where can be the error ? thanks. > > -- > Mario.

Re: Temporary failure in name resolution error when I try to ping Debian 12 / DomU running on top of the Devuan 5 host os / Dom0

os (Debian 12) >> >> >> /etc/network/interfaces : >> >> source /etc/network/interfaces.d/* >> iface enX0 inet static >> address 192.168.1.10/24 >> gateway 192.168.1.7 >> >> /etc/resolv.conf : >> >> options edns0 trust-ad >&

Re: Temporary failure in name resolution error when I try to ping Debian 12 / DomU running on top of the Devuan 5 host os / Dom0

worm:~# ping google.it <http://google.it> ping: google.it <http://google.it>: Temporary failure in name resolution In the client try the command dig @8.8.8.8 lists.debian.org mx This will tell if your network config allows your client to access the 8.8.8.8 DNS server. What is the co

Re: Temporary failure in name resolution error when I try to ping Debian 12 / DomU running on top of the Devuan 5 host os / Dom0

up > default qlen 1000 >link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever >inet6 ::1/128 scope host noprefixroute > valid_lft forever preferred_lft forever > > 2: sit0@NONE: mtu 1480 qdisc noop state DOWN group default qlen > 1000 >link/sit 0.0.0.0 brd 0.0.0.0 > > 3: enX0: mtu 1500 qdisc > pfifo_fast state UP group default > qlen 1000 >link/ether 00:16:3e:12:34:56 brd ff:ff:ff:ff:ff:ff >inet 192.168.1.10/24 brd 192.168.1.255 scope global enX0 > valid_lft forever preferred_lft forever >inet6 fe80::216:3eff:fe12:3456/64 scope link > valid_lft forever preferred_lft forever > > root@bookworm:~# ping google.it > ping: google.it: Temporary failure in name resolution > > > Where can be the error ? thanks. > > -- > Mario. > -- Mario.

Temporary failure in name resolution error when I try to ping Debian 12 / DomU running on top of the Devuan 5 host os / Dom0

forever inet6 fe80::216:3eff:fe12:3456/64 scope link valid_lft forever preferred_lft forever root@bookworm:~# ping google.it ping: google.it: Temporary failure in name resolution Where can be the error ? thanks. -- Mario.

Re: multiple systemd-nspawn container name resolution

is as followed: ip r 169.254.0.0/16 dev ve-test3 proto kernel scope link src 169.254.144.44 169.254.0.0/16 dev ve-test2 proto kernel scope link src 169.254.38.46 169.254.0.0/16 dev ve-test proto kernel scope link src 169.254.80.104 So I only can ping test3. The same problem is with name resolution

multiple systemd-nspawn container name resolution

-test3 proto kernel scope link src 169.254.144.44 169.254.0.0/16 dev ve-test2 proto kernel scope link src 169.254.38.46 169.254.0.0/16 dev ve-test proto kernel scope link src 169.254.80.104 So I only can ping test3. The same problem is with name resolution. best regards

Re: Temporary failure in name resolution

>> That I can believe (and isn't a bad option, IMO), >> but the discussion was about broken DNS proxies/servers. > Well, I assume that's your term for the modem/router being leased > by the OP from att, and similar. Not really. It was my attempt at reproducing the approximate description of some

Re: Temporary failure in name resolution

On Mon 05 Apr 2021 at 09:33:25 (-0400), Stefan Monnier wrote: > >>> A notable class of exceptions is that of OpenWrt powered devices: > >>> OpenWrt comes with dnsmasq configured out of the box, and thus provides > >>> caching. > >> "Back in the days" (at the beginning of OpenWRT), most home

Re: Temporary failure in name resolution

>>> A notable class of exceptions is that of OpenWrt powered devices: >>> OpenWrt comes with dnsmasq configured out of the box, and thus provides >>> caching. >> "Back in the days" (at the beginning of OpenWRT), most home routers used >> `dnsmasq`, AFAIK. So I'd expect today's devices to use

Re: Temporary failure in name resolution

the 10.9 upgrade. No one else is reporting this exact problem so I believe that the problem and the upgrade were coincidental and nothing needs to change in 10.9 to correct "Temporary failure in name resolution." Thanks, Alexander. - Dan Don't mention it. I just want correct you, the f

Re: Temporary failure in name resolution

On 05.04.2021 07:47, Stefan Monnier wrote: A notable class of exceptions is that of OpenWrt powered devices: OpenWrt comes with dnsmasq configured out of the box, and thus provides caching. "Back in the days" (at the beginning of OpenWRT), most home routers used `dnsmasq`, AFAIK. So I'd expect

Re: Temporary failure in name resolution

; modem. That would explain "attlocal.net" lines. Do you have > administrative access to your DSL modem's configuration web interface? > Or is it a leased device that was configured by your ISP and you don't > have the option to configure it? It is a leased device. I have spen

Re: Temporary failure in name resolution

> A notable class of exceptions is that of OpenWrt powered devices: > OpenWrt comes with dnsmasq configured out of the box, and thus provides > caching. "Back in the days" (at the beginning of OpenWRT), most home routers used `dnsmasq`, AFAIK. So I'd expect today's devices to use `dnsmasq` or

Re: Temporary failure in name resolution

On Sat, 3 Apr 2021 02:15:55 +0500 "Alexander V. Makartsev" wrote: ... > Most of SOHO class routers\modems don't offer fully-fledged DNS server > and domain name caching features. > They act as relays, simply redirecting DNS requests to the nearest > configured domain name server. A notable

Re: Temporary failure in name resolution

ile one device can do both, complexity and risk are greater in one device than their sums with two devices. It is possible that your name resolution issues are due to some misconfiguration of Debian in its networking role. Please document how you have installed and configured Debian -- IS

Re: Temporary failure in name resolution

On 03.04.2021 21:59, Dan Norton wrote: Isn't there a tidier way besides making resolv.conf immutable, resulting in lots of /etc/resolv.conf.dhclient-new.* files? Maybe stopping dhclient from overwriting resolv.conf[1]? - Dan

Re: Temporary failure in name resolution

On Sat, Apr 03, 2021 at 12:59:04PM -0400, Dan Norton wrote: > Isn't there a tidier way besides making resolv.conf immutable, > resulting in lots of /etc/resolv.conf.dhclient-new.* files? Maybe > stopping dhclient from overwriting resolv.conf[1]? > > - Dan > >

Re: Temporary failure in name resolution

Greg Wooledge on Fri, 2 Apr 2021 23:24:43 -0400 wrote: "On Fri, Apr 02, 2021 at 10:48:09PM -0400, Dan Norton wrote: > # cat /etc/resolv.conf > domain attlocal.net > search attlocal.net > nameserver 1.1.1.1 > nameserver 1.0.0.1 > ...and this works very well. I like it because it cuts out more > of

Re: Temporary failure in name resolution

On Sat, Apr 03, 2021 at 12:05:54PM -0400, Dan Norton wrote: > On 3/31/21 1:33 PM, David Christensen wrote: > > "$ host -v -t A www.debian.org 192.168.1.254 > > > Dan -- did you run the above test? This may help isolate if the problem > is Debian 10 or your AT gateway." > > $ host -v -t A

Re: Temporary failure in name resolution

On 3/31/21 1:33 PM, David Christensen wrote: "$ host -v -t A www.debian.org 192.168.1.254 Dan -- did you run the above test? This may help isolate if the problem is Debian 10 or your AT gateway." $ host -v -t A www.debian.org 192.168.1.254 Trying "www.debian.org" ;; connection timed out; no

Re: Temporary failure in name resolution

On Sat, 3 Apr 2021 10:21:08 +0200 wrote: > On Sat, Apr 03, 2021 at 08:57:20AM +0100, Joe wrote: > > [...] > > > think even then that most of them had oriental firmware, and my > > opinion of even Japanese code is that it isn't wonderful. Hardware > > great, > > Given the generally

Re: Temporary failure in name resolution

On Sat, Apr 03, 2021 at 08:57:20AM +0100, Joe wrote: [...] > think even then that most of them had oriental firmware, and my opinion > of even Japanese code is that it isn't wonderful. Hardware great, Given the generally pitiful state of the software trade all over the place, the

Re: Temporary failure in name resolution

On Fri, 2 Apr 2021 20:14:41 -0400 Greg Wooledge wrote: > > Home router DNS services tend to be mediocre at best, and usually they > simply forward your requests to your ISP's nameservers, and *those* > tend to be problematic at times too (depending on the ISP). That's > two layers of

Re: Temporary failure in name resolution

On 3/31/21 1:33 PM, David Christensen wrote: $ host -v -t A www.debian.org 192.168.1.254 Dan -- did you run the above test? This may help isolate if the problem is Debian 10 or your AT gateway. David

Re: Temporary failure in name resolution

On Fri, Apr 02, 2021 at 10:48:09PM -0400, Dan Norton wrote: > # cat /etc/resolv.conf > domain attlocal.net > search attlocal.net > nameserver 1.1.1.1 > nameserver 1.0.0.1 > ...and this works very well. I like it because it cuts out more > of google's monitoring of my browsing (I use Brave browser

Re: Temporary failure in name resolution

Alexander V. Makartsev on Sat, 3 Apr 2021 01:17:59 +0500 wrote: "On 02.04.2021 22:56, Dan Norton wrote: Alexander V. Makartsev wrote Wed, 31 Mar 2021 10:16:08 +0500: "Is "192.168.1.254" an IP address of your DSL modem? If you don't need to resolve hostnames from you local network, like

Re: Temporary failure in name resolution

On Fri, Apr 02, 2021 at 05:36:51PM -0400, rhkra...@gmail.com wrote: > On Friday, April 02, 2021 04:35:58 PM Greg Wooledge wrote: > > >2) would the caching feature be bypassed if your computer used the > > >public > > > > > > DNS name servers (e.g., 8.8.8.8, 8.8.4.4, and 1.1.1.1)? (Or if

Re: Temporary failure in name resolution

On Friday, April 02, 2021 05:15:55 PM Alexander V. Makartsev wrote: > On 03.04.2021 01:15, rhkra...@gmail.com wrote: > > Sort of building on this question, and just trying to educate myself, if > > the > > > > DSL modem had a caching nameserver: > > 1) would your computer need to specify the

Re: Temporary failure in name resolution

On Friday, April 02, 2021 04:35:58 PM Greg Wooledge wrote: > On Fri, Apr 02, 2021 at 04:15:07PM -0400, rhkra...@gmail.com wrote: > > Sort of building on this question, and just trying to educate myself, if > > the > > > > DSL modem had a caching nameserver: > >1) would your computer need to

Re: Temporary failure in name resolution

On 03.04.2021 01:15, rhkra...@gmail.com wrote: Sort of building on this question, and just trying to educate myself, if the DSL modem had a caching nameserver: 1) would your computer need to specify the IP of that modem (presumably) 192.168.1.254 to take advantage of the caching? Most of

Re: Temporary failure in name resolution

On Fri, Apr 02, 2021 at 04:15:07PM -0400, rhkra...@gmail.com wrote: > Sort of building on this question, and just trying to educate myself, if the > DSL modem had a caching nameserver: > >1) would your computer need to specify the IP of that modem (presumably) > 192.168.1.254 to take

Re: Temporary failure in name resolution

On 02.04.2021 22:56, Dan Norton wrote: Alexander V. Makartsev wrote Wed, 31 Mar 2021 10:16:08 +0500: "Is "192.168.1.254" an IP address of your DSL modem? If you don't need to resolve hostnames from you local network, like "somepc1.attlocal.net" and only want to access the Internet, you can

Re: Temporary failure in name resolution

On Friday, April 02, 2021 01:56:19 PM Dan Norton wrote: > Alexander V. Makartsev wrote Wed, 31 Mar 2021 10:16:08 +0500: > > "Is "192.168.1.254" an IP address of your DSL modem? > If you don't need to resolve hostnames from you local network, like > "somepc1.attlocal.net" and only want to access

Re: Temporary failure in name resolution

Alexander V. Makartsev wrote Wed, 31 Mar 2021 10:16:08 +0500: "Is "192.168.1.254" an IP address of your DSL modem? If you don't need to resolve hostnames from you local network, like "somepc1.attlocal.net" and only want to access the Internet, you can configure one or more of the public DNS

Re: Temporary failure in name resolution

don't know, except that having nameserver 1.1.1.1 and 1.0.0.1 in /etc/resolv.conf as Felix suggested results in successful name resolution. My setup is an AT BGW210 modem connected by ethernet cable to a desktop which serves wifi for printing and ISP access to my wife's Windows laptop. Before I tri

Re: Temporary failure in name resolution

On Thu, Apr 01, 2021 at 11:50:56AM -0500, David Wright wrote: > > domain attlocal.net > > search attlocal.net > > I don't recall your answering Alexander's question: what benefit are > you getting from those two lines? Do you have a number of machines > at home that are being placed in that

Re: Temporary failure in name resolution

ble > root@deb4:~# ping google.com > ping: google.com: Temporary failure in name resolution > root@deb4:~# cat /etc/resolv.conf > domain attlocal.net > search attlocal.net > nameserver 192.168.1.254 > ## showing that /etc/resolv.conf has been clobbered Normally, I would say that yo

Re: Temporary failure in name resolution

On 3/31/21 3:28 PM, Dan Norton wrote: David Christensen wrote on Wed, 31 Mar 2021 13:49:56 -0700: I would do 'apt-get update' and 'apt-get upgrade' ('autoremove', 'clean', etc.). Once apt-get(8) is done, I would revert the changes to /etc/resolv.conf and see if name resolution breaks or remains

Re: Temporary failure in name resolution

David Christensen wrote on Wed, 31 Mar 2021 13:49:56 -0700: I would do 'apt-get update' and 'apt-get upgrade' ('autoremove', 'clean', etc.). Once apt-get(8) is done, I would revert the changes to /etc/resolv.conf and see if name resolution breaks or remains working. (I would test by renaming /etc

Re: Temporary failure in name resolution

On 3/31/21 1:58 PM, Greg Wooledge wrote: On Wed, Mar 31, 2021 at 01:43:23PM -0700, David Christensen wrote: Is there technical documentation that explains how name resolution works in Linux 4.19.0-16-amd64 and/or Debian 10? (e.g. design and implementation, userland tools, etc..) It's

Re: Temporary failure in name resolution

On Wed, Mar 31, 2021 at 01:43:23PM -0700, David Christensen wrote: > Is there technical documentation that explains how name resolution works in > Linux 4.19.0-16-amd64 and/or Debian 10? (e.g. design and implementation, > userland tools, etc..) It's not the kernel. At all. The stan

Re: Temporary failure in name resolution

192.168.1.254 All is well again. Thanks again and thanks to everyone who responded. Okay. I would do 'apt-get update' and 'apt-get upgrade' ('autoremove', 'clean', etc.). Once apt-get(8) is done, I would revert the changes to /etc/resolv.conf and see if name resolution breaks or remains

Re: Temporary failure in name resolution

chattr +i /etc/resolv.conf That's *one* of the methods listed on the wiki. Just be aware that it can leave a whole bunch of /etc/resolv.conf.dhclient-new.* files sitting around, and be prepared to remove them. (I use a weekly crontab job.) Is there technical documentation that explains how name

Re: Temporary failure in name resolution

ngs that I'm aware of. Okay. This problem makes me post from a Windows laptop and transfer terminal output via thumb drive to the laptop. Not pretty. Sneakernet works. :-) > This laptop is the only other computer but it runs Windows. Is that testing name resolution with another co

Re: Temporary failure in name resolution

Thank you, Felix. This post is coming from Debian with names resolved: #1 SMP Debian 4.19.181-1 (2021-03-19) Also resolv.conf is un-messed with: $ cat /etc/resolv.conf domain attlocal.net search attlocal.net nameserver 1.1.1.1 nameserver 1.0.0.1 nameserver 192.168.1.254 All is well again. Thanks

Re: Temporary failure in name resolution

On Wed, Mar 31, 2021 at 01:26:32PM -0400, Felix Miata wrote: > Dan Norton composed on 2021-03-31 12:46 (UTC-0400): > > > # cd /etc > > # cat resolv.conf > > domain attlocal.net > > search attlocal.net > > nameserver 192.168.1.254 > > [something removes additional nameserver lines that I add]

Re: Temporary failure in name resolution

Dan Norton composed on 2021-03-31 12:46 (UTC-0400): > # cd /etc > # cat resolv.conf > domain attlocal.net > search attlocal.net > nameserver 192.168.1.254 > [something removes additional nameserver lines that I add] > I

Re: Temporary failure in name resolution

amd64 1:3.18.1+15buster Temporary failure resolving 'qgis.org' [this continues to Err:19 then more] Have not changed any of the gateway settings that I'm aware of. This laptop is the only other computer but it runs Windows. Is that testing name resolution with another computer? # ifconfig eno1

Re: Temporary failure in name resolution

I am experiencing a potential related issue, (Subject: DNS problems on Raspberry Pi 400 (Debian 10.9)" on this list) can you please install dnsutils (sudo apt-get install dnsutils) and try to use dig to get an ip from a domain and send us your output? Because if i try to use host it returns

Re: Temporary failure in name resolution

On 3/31/2021 4:21 AM, Dan Norton wrote: After the 10.9 upgrade, name resolution is not working for me. Does anyone else see this? My desktop is a wifi server for laptop access using windows. That works OK but the server, attached by ethernet to the DSL modem does not get names resolved since

Re: Temporary failure in name resolution

On 3/30/21 7:21 PM, Dan Norton wrote: After the 10.9 upgrade, name resolution is not working for me. Does anyone else see this? My desktop is a wifi server for laptop access using windows. That works OK but the server, attached by ethernet to the DSL modem does not get names resolved since

Re: Temporary failure in name resolution

On 31.03.2021 07:21, Dan Norton wrote: After the 10.9 upgrade, name resolution is not working for me. Does anyone else see this? My desktop is a wifi server for laptop access using windows. That works OK but the server, attached by ethernet to the DSL modem does not get names resolved since

Temporary failure in name resolution

After the 10.9 upgrade, name resolution is not working for me. Does anyone else see this? My desktop is a wifi server for laptop access using windows. That works OK but the server, attached by ethernet to the DSL modem does not get names resolved since the upgrade. The resolvconf program

Re: intermittent name resolution failures

On Fri, Dec 28, 2018 at 2:37 PM Florian Weimer wrote: > > * kamaraju kusumanchi: > > > I see a lot of differences between trial_6.txt and trial_4.txt. Does > > that mean anything or is this variation expected? > > The first hop should be the same in all cases and reachable (no > stars). It looks

Re: intermittent name resolution failures

* kamaraju kusumanchi: > On Fri, Dec 28, 2018 at 3:51 AM wrote: >> >> Whenever your DNS fails try a "traceroute 8.8.8.8". Compare its results >> to what you get when you do it at times where your DNS works. Perhaps >> this sheds some light on it. > > That is tough to capture because the problem

Re: intermittent name resolution failures

On Fri, Dec 28, 2018 at 3:51 AM wrote: > > Whenever your DNS fails try a "traceroute 8.8.8.8". Compare its results > to what you get when you do it at times where your DNS works. Perhaps > this sheds some light on it. That is tough to capture because the problem is intermittent. When I retry it

Re: intermittent name resolution failures

On Fri, Dec 28, 2018 at 11:57:35AM +0100, Pascal Hambourg wrote: > Le 28/12/2018 à 09:51, to...@tuxteam.de a écrit : > >On Thu, Dec 27, 2018 at 11:41:48PM -0500, kamaraju kusumanchi wrote: > >>How to debug intermittent name resolution failures on a Debian Stretch > >>

Re: intermittent name resolution failures

Le 28/12/2018 à 09:51, to...@tuxteam.de a écrit : On Thu, Dec 27, 2018 at 11:41:48PM -0500, kamaraju kusumanchi wrote: How to debug intermittent name resolution failures on a Debian Stretch machine? I take your DNS server is 8.8.8.8 And 8.8.4.4, as can be seen in /etc/resolv.conf. My top

Re: intermittent name resolution failures

On Thu, Dec 27, 2018 at 11:41:48PM -0500, kamaraju kusumanchi wrote: > How to debug intermittent name resolution failures on a Debian Stretch > machine? [...] > ;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 11 ms I take your DNS server is 8.8.8.8 (kids, do we have to hand off

intermittent name resolution failures

How to debug intermittent name resolution failures on a Debian Stretch machine? When it does not work: % dig +trace github.com ; <<>> DiG 9.10.3-P4-Debian <<>> +trace github.com ;; global options: +cmd ;; connection timed out; no servers could be reached When it works

Re: stretch and DNS name resolution service for other devices on a LAN

On Fri 02 Mar 2018 at 23:56:02 (+0100), Pascal Hambourg wrote: > Le 28/02/2018 à 21:13, David Wright a écrit : > >>># > >>># /etc/interfaces.d/directcable for west 2018-02-25 > >>> > >>>auto eth0 > >>>iface eth0 inet static > >>> address 192.168.2.15/24 > >> > >>Fine. You could also add

Re: stretch and DNS name resolution service for other devices on a LAN

Le 28/02/2018 à 21:13, David Wright a écrit : # # /etc/interfaces.d/directcable for west 2018-02-25 auto eth0 iface eth0 inet static address 192.168.2.15/24 Fine. You could also add "allow-hotplug eth0" in case eth0 would be discovered late. OK. Tried that here. The ip a is before

Re: stretch and DNS name resolution service for other devices on a LAN

On Wed 28 Feb 2018 at 19:42:27 (+0100), Pascal Hambourg wrote: > Le 28/02/2018 à 18:14, David Wright a écrit : > > > >$ cat /etc/network/interfaces /etc/network/interfaces.d/directcable > ># This file describes the network interfaces available on your system > ># and how to activate them. For more

Re: stretch and DNS name resolution service for other devices on a LAN

Le 28/02/2018 à 18:14, David Wright a écrit : $ cat /etc/network/interfaces /etc/network/interfaces.d/directcable # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The

Re: stretch and DNS name resolution service for other devices on a LAN

On Tue 27 Feb 2018 at 20:59:17 (+0100), Pascal Hambourg wrote: > Le 25/02/2018 à 18:35, David Wright a écrit : > >On Sat 24 Feb 2018 at 09:49:27 (+0100), Pascal Hambourg wrote: > > > On disadvantage is that these addresses are not globally unique (the > link local prefix exists on all

Re: stretch and DNS name resolution service for other devices on a LAN

Le 25/02/2018 à 18:35, David Wright a écrit : On Sat 24 Feb 2018 at 09:49:27 (+0100), Pascal Hambourg wrote: On disadvantage is that these addresses are not globally unique (the link local prefix exists on all interfaces) and must be appended with an interface name. Not an issue here. The

Re: stretch and DNS name resolution service for other devices on a LAN

On Sat 24 Feb 2018 at 09:49:27 (+0100), Pascal Hambourg wrote: > Le 22/02/2018 à 22:57, David Wright a écrit : > >On Tue 23 Jan 2018 at 20:56:31 (+0100), Pascal Hambourg wrote: > >>Le 23/01/2018 à 18:08, David Wright a écrit : > >>> > >>>[My Laptop] --- wireless connection IPv4 --- [Router] ---

Re: stretch and DNS name resolution service for other devices on a LAN

On 2018-02-24, Pascal Hambourg wrote: > > Anyway, we have a saying here which roughly translates to : "you cannot > force an unthirsty donkey to drink". I looked it up (because neither me nor hubby--de vieille souche--recognized it right off). On ne saurait faire boire

Re: stretch and DNS name resolution service for other devices on a LAN

Le 22/02/2018 à 22:57, David Wright a écrit : On Tue 23 Jan 2018 at 20:56:31 (+0100), Pascal Hambourg wrote: Le 23/01/2018 à 18:08, David Wright a écrit : [My Laptop] --- wireless connection IPv4 --- [Router] --- Internet Modem | / | | CAT5

Re: stretch and DNS name resolution service for other devices on a LAN

On Tue 23 Jan 2018 at 20:56:31 (+0100), Pascal Hambourg wrote: > Le 23/01/2018 à 18:08, David Wright a écrit : > > > >[My Laptop] --- wireless connection IPv4 --- [Router] --- Internet Modem > > | / | > > | CAT5 cable IPv6/

Re: stretch and DNS name resolution service for other devices on a LAN

I didn't read all the answers (only half of those). But I have the same problem and I now think it has nothing to do with named, bind (4 8 or 9). During Stretch installation with netinst, Network-manager configured once for all /etc/hostname and /etc/resolv.conf. As I have only one routable

Re: stretch and DNS name resolution service for other devices on a LAN

Le 23/01/2018 à 18:08, David Wright a écrit : [My Laptop] --- wireless connection IPv4 --- [Router] --- Internet Modem | / | | CAT5 cable IPv6/ | | / | wireless/wired [My

Re: stretch and DNS name resolution service for other devices on a LAN

On Tue 23 Jan 2018 at 16:06:01 (-), Andy Hawkins wrote: > Hi, > > In article <20180123144327.GA6815@alum>, >David Wright wrote: > > This would all be a step in the wrong direction here. Point (2) was > > that using IPv6 over CAT5 avoids swamping the

Re: stretch and DNS name resolution service for other devices on a LAN

Hi, In article <20180123144327.GA6815@alum>, David Wright wrote: > This would all be a step in the wrong direction here. Point (2) was > that using IPv6 over CAT5 avoids swamping the router. (Of course, > that's already been snipped out of the thread.) If the

Re: stretch and DNS name resolution service for other devices on a LAN

On Tue 23 Jan 2018 at 13:41:31 (+), Joe wrote: > On Tue, 23 Jan 2018 11:12:41 + (UTC) > Curt wrote: > > > On 2018-01-23, Andy Hawkins wrote: > > > Hi, > > > In article <20180122185135.GA12212@alum>, > > >David

  1   2   3   >