[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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&T gateway."

$ host -v -t A www.debian.org 192.168.1.254
Trying "www.debian.org"
;; connection timed out; no servers could be reached

That's to be expected I guess since nameserver 192.168.1.254 is no
longer in resolv.conf.

$ host -v -t A www.debian.org
Trying "www.debian.org"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46537
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.debian.org.			IN	A

;; ANSWER SECTION:
www.debian.org.		260	IN	A	149.20.4.15
www.debian.org.		260	IN	A	128.31.0.62

Received 64 bytes from 1.1.1.1#53 in 30 ms
 
HTH, but would it help isolate the problem to temporarily put
nameserver 192.168.1.254 back in resolv.conf and retry the above?

BTW, I just saw your earlier (revised?) post about using Windows on the
laptop. Yikes! If you don't mind, I'd like to skip that. Besides, my
local network is much simpler since there is only one ethernet
connection. Sorry if I misled you.

 - Dan


Reply to: