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

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


The five lines immediately above are incorrectly formatted -- they should be prefixed/ indented one more level. Please configure your e-mail client to prefix/ indent the text of messages that you reply to.


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

$ 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


Thank you. Those test results should be useful for isolating and debugging the issue.


HTH, but would it help isolate the problem to temporarily put
nameserver 192.168.1.254 back in resolv.conf and retry the above?


AIUI, no.  See Greg Wooledge's reply for an explanation.


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.


On 3/30/21 7:21 PM, Dan Norton wrote:
> My desktop is a wifi server for laptop access using windows


Connecting the Debian computer to the AT&T gateway and connecting the laptop to the gateway is a simpler network (star topology) than connecting Debian to the gateway, configuring Debian as a Wi-Fi router, and connecting the laptop to Debian (router-behind-router topology).


Interactive desktop usage and network routing are two functions that are best fulfilled by two separate devices. While 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 -- ISO, tasksel, packages, Ethernet interface, Wi-Fi interface, routing, address and/or port translation, firewall, DHCP proxy/ forwarding, DNS proxy/ forwarding, etc..


David


Reply to: