Re: Temporary failure in name resolution

Shaheena Kazi wrote: > Package: ntpsec > > Hello, we were using Bullseye and have upgraded to Bookworm. > With Bookworm, we have ntpsec. > The package is installed successfully and the service looks good. > But the syslog is filled with below messages: > >

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 the >> PC is *not* connected to

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* connected to internet;

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

On Sun, Nov 19, 2023 at 10:54:08PM +0100, Mario Marietto wrote: > Hello. > > I'm trying to configure Debian 12 / DomU on my (Arm32) Chromebook because I > want to use the Internet and I want its IP address to be seen from > "outside" of my LAN. > > This is the tutorial that I'm following : >

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

It does not care anymore. The instructions on the website are working. It's me that I totally forgot to add the IP on the VIF statement of the debian.cfg file. As soon as I added it and I changed $main_ip with $ip on the vip-route-local,the network started working like a charm. To work the

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

On 20/11/23 05:54, Mario Marietto wrote: root@bookworm:~# ifup enX0 root@bookworm:~# ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group 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

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

Errata corrige : nano debian.cfg : kernel = '/Dati/xen/kernels/zImage-6.1.61-stb-xen-cbe+' memory = '768' name = 'Debian-bookworm' vcpus = '1' disk = [ '/Dati/xen/debian.img,,xvda,w' ] vif = [ 'type=vif,mac=00:16:3e:12:34:56,script=vif-route-*local*' ] extra = 'console=hvc0 root=/dev/xvda rw

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

On 05.04.2021 07:40, Dan Norton wrote: [1]https://wiki.debian.org/resolv.conf#Modifying_.2Fetc.2Fdhcp.2Fdhclient.conf After the AT tech does his thing tomorrow, I plan to add supersede domain-name-servers 1.1.1.1,1.0.0.1; to resolv.conf. Until then I want things to be unchanged from the

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

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,

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

On 4/3/21 9:05 AM, 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." The five lines immediately above are incorrectly

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

David Wright wrote on Thu, 1 Apr 2021 11:50:56 -0500: "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 domain, whose names you resolve with att's help?" I don't know,

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

On Wed 31 Mar 2021 at 18:28:52 (-0400), 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

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

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 not the

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 standard name

Re: Temporary failure in name resolution

On 3/31/21 11:58 AM, Dan Norton wrote: 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

Re: Temporary failure in name resolution

On 3/31/21 10:37 AM, Greg Wooledge wrote: As of right now, we have at least two people posting to debian-user about DNS failures involving what appears to be their home router's forwarding DNS service, and Debian 10.9. Switching the nameserver lines in resolv.conf to something *other than* the

Re: Temporary failure in name resolution

I have reorganized the content below to improve comprehension. On 3/31/21 9:46 AM, Dan Norton wrote: Thanks to all who responded. > Thanks for your detailed help. Let me know if I can dig out more. YW. We are making progress. See below. Have not changed any of the gateway settings that

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

Thanks to all who responded. This problem makes me post from a Windows laptop and transfer terminal output via thumb drive to the laptop. Not pretty. To David: Yes, I have done a cold reboot since upgrading. # apt update 0% [Connecting to deb.debian.org] [Connecting to qgis.org] [Connecting to

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

Re: Temporary failure in name resolution (PPPoE)

On Sunday 06 Nov 2005 17:14, Masatran (Rajasekaran Deepak) wrote: I am using PPPoE to connect to the internet. For a few minutes after booting the computer and running pppoe-start, I get this error: $ ssh research.iiit.ac.in ssh: research.iiit.ac.in: Temporary failure in name resolution How