Skip to main content ↑ ↓
Topic: ERR_NAME_NOT_RESOLVED on some websites only when using wlan (Read 2510 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

ERR_NAME_NOT_RESOLVED on some websites only when using wlan

Hello everyone,

I am currently on wifi using wpa_supplicant and dhcpcd with a usb adapter, which is functioning fine on some websites such as this one once I unblock wlan in rfkill, but gives ERR_NAME_NOT_RESOLVED on most other websites. Sometimes pinging a website gives a "Network is unreachable" error and other times it works fine.

The adapter works using a driver included in the kernel. I am not using any other network managers. I am not sure if the issue is related, but trying to run openvpn gives a network is unreachable error as well.

The problem doesn't persist once I use ethernet, meaning all pings work fine and there are no ERR_NAME_NOT_RESOLVED errors.

I'd like to write what I have tried doing to fix this issue, but I honestly have no idea where to even start.

ip a output:
Code: [Select]
1: lo: <LOOPBACK,UP,LOWER_UP> 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 forever preferred_lft forever
    inet6 ::1/128 scope host proto kernel_lo
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,DYNAMIC,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 04:92:26:d8:3a:ef brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 04:42:1a:49:50:fa brd ff:ff:ff:ff:ff:ff
    inet6 fd52:5c66:4206:0:642:1aff:fe49:50fa/64 scope global dynamic mngtmpaddr proto kernel_ra
       valid_lft 6865sec preferred_lft 3265sec
    inet6 2003:c7:7f37:8400:642:1aff:fe49:50fa/64 scope global dynamic mngtmpaddr proto kernel_ra
       valid_lft 6865sec preferred_lft 1455sec
    inet6 fe80::642:1aff:fe49:50fa/64 scope link proto kernel_ll
       valid_lft forever preferred_lft forever

ip n output:
Code: [Select]
fe80::ab6:57ff:fe26:94fc dev wlan0 lladdr 08:b6:57:26:94:fc router REACHABLE
fd52:5c66:4206:0:ab6:57ff:fe26:94fc dev wlan0 lladdr 08:b6:57:26:94:fc router STALE

Re: ERR_NAME_NOT_RESOLVED on some websites only when using wlan

Reply #1 –
1. Install bind if not already there
2. Get a website that doesn't resolve with wlan0, e.g. kernel.org
3. Run dig kernel.org (should error out, note the output)
4. Run dig kernel.org @1.1.1.1

Post results.

Re: ERR_NAME_NOT_RESOLVED on some websites only when using wlan

Reply #2 –
in addition to that post
cat /etc/resolv.conf


Also, are you on a vm?

Re: ERR_NAME_NOT_RESOLVED on some websites only when using wlan

Reply #3 –
dig stackexchange.com output:
Code: [Select]
;; UDP setup with 5.9.164.112#53(5.9.164.112) for stackexchange.com failed: network unreachable.
;; no servers could be reached
;; UDP setup with 5.9.164.112#53(5.9.164.112) for stackexchange.com failed: network unreachable.
;; no servers could be reached
;; UDP setup with 5.9.164.112#53(5.9.164.112) for stackexchange.com failed: network unreachable.

; <<>> DiG 9.20.10 <<>> stackexchange.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49442
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;stackexchange.com.             IN      A

;; ANSWER SECTION:
stackexchange.com.      273     IN      A       104.18.43.226
stackexchange.com.      273     IN      A       172.64.144.30

;; Query time: 190 msec
;; SERVER: fd52:5c66:4206:0:ab6:57ff:fe26:94fc#53(fd52:5c66:4206:0:ab6:57ff:fe26:94fc) (UDP)
;; WHEN: Sat Aug 23 12:13:29 CEST 2025
;; MSG SIZE  rcvd: 78


dig stackexchange.com @1.1.1.1 output:
Code: [Select]
;; UDP setup with 1.1.1.1#53(1.1.1.1) for stackexchange.com failed: network unreachable.
;; no servers could be reached
;; UDP setup with 1.1.1.1#53(1.1.1.1) for stackexchange.com failed: network unreachable.
;; no servers could be reached
;; UDP setup with 1.1.1.1#53(1.1.1.1) for stackexchange.com failed: network unreachable.
;; no servers could be reached

cat /etc/resolv.conf output:
Code: [Select]
# Generated by dhcpcd from eth0.dhcp, eth0.dhcp6, eth0.ra
# /etc/resolv.conf.head can replace this line
domain fritz.box
nameserver 5.9.164.112
nameserver fd52:5c66:4206:0:ab6:57ff:fe26:94fc
nameserver 2003:c7:7f37:8400:ab6:57ff:fe26:94fc
# /etc/resolv.conf.tail can replace this line

Quote from: mrbrklyn – on
Also, are you on a vm?
I am not on a vm.

Re: ERR_NAME_NOT_RESOLVED on some websites only when using wlan

Reply #4 –
Quote from: user44 – on
dig stackexchange.com output:
Code: [Select]
;; UDP setup with 5.9.164.112#53(5.9.164.112) for stackexchange.com failed: network unreachable.
;; no servers could be reached
;; UDP setup with 5.9.164.112#53(5.9.164.112) for stackexchange.com failed: network unreachable.
;; no servers could be reached
;; UDP setup with 5.9.164.112#53(5.9.164.112) for stackexchange.com failed: network unreachable.

; <<>> DiG 9.20.10 <<>> stackexchange.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49442
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;stackexchange.com.             IN      A

;; ANSWER SECTION:
stackexchange.com.      273     IN      A       104.18.43.226
stackexchange.com.      273     IN      A       172.64.144.30

;; Query time: 190 msec
;; SERVER: fd52:5c66:4206:0:ab6:57ff:fe26:94fc#53(fd52:5c66:4206:0:ab6:57ff:fe26:94fc) (UDP)
;; WHEN: Sat Aug 23 12:13:29 CEST 2025
;; MSG SIZE  rcvd: 78


dig stackexchange.com @1.1.1.1 output:
Code: [Select]
;; UDP setup with 1.1.1.1#53(1.1.1.1) for stackexchange.com failed: network unreachable.
;; no servers could be reached
;; UDP setup with 1.1.1.1#53(1.1.1.1) for stackexchange.com failed: network unreachable.
;; no servers could be reached
;; UDP setup with 1.1.1.1#53(1.1.1.1) for stackexchange.com failed: network unreachable.
;; no servers could be reached

cat /etc/resolv.conf output:
Code: [Select]
# Generated by dhcpcd from eth0.dhcp, eth0.dhcp6, eth0.ra
# /etc/resolv.conf.head can replace this line
domain fritz.box
nameserver 5.9.164.112
nameserver fd52:5c66:4206:0:ab6:57ff:fe26:94fc
nameserver 2003:c7:7f37:8400:ab6:57ff:fe26:94fc
# /etc/resolv.conf.tail can replace this line

Quote from: mrbrklyn – on
Also, are you on a vm?
I am not on a vm.


What is this noise in your dig output?
Quote
;; UDP setup with 5.9.164.112#53(5.9.164.112) for stackexchange.com failed: network unreachable.
;; no servers could be reached
;; UDP setup with 5.9.164.112#53(5.9.164.112) for stackexchange.com failed: network unreachable.
;; no servers could be reached
;; UDP setup with 5.9.164.112#53(5.9.164.112) for stackexchange.com failed: network unreachable.

Ping this
flatbush:[ruben]:~$ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=55 time=38.8 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=55 time=14.4 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=55 time=14.1 ms

and this

flatbush:[ruben]:~$ ping  5.9.164.112
PING 5.9.164.112 (5.9.164.112) 56(84) bytes of data.
64 bytes from 5.9.164.112: icmp_seq=1 ttl=52 time=122 ms
64 bytes from 5.9.164.112: icmp_seq=2 ttl=52 time=118 ms
64 bytes from 5.9.164.112: icmp_seq=3 ttl=52 time=117 ms
64 bytes from 5.9.164.112: icmp_seq=4 ttl=52 time=115 ms

Is that even a name server?
flatbush:[ruben]:~$ dig -x 5.9.164.112

; <<>> DiG 9.20.11 <<>> -x 5.9.164.112
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58276
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: 56efc4c1563cae2e0100000068a9965bfda339556b1349a5 (good)
;; QUESTION SECTION:
;112.164.9.5.in-addr.arpa.      IN      PTR

;; ANSWER SECTION:
112.164.9.5.in-addr.arpa. 86400 IN      PTR     dns3.digitalcourage.de.

;; Query time: 1563 msec
;; SERVER: 10.0.0.37#53(10.0.0.37) (UDP)
;; WHEN: Sat Aug 23 06:22:16 EDT 2025
;; MSG SIZE  rcvd: 117


Code: [Select]
flatbush:[ruben]:~$ dig  @5.9.164.112 mrbrklyn.com
;; communications error to 5.9.164.112#53: timed out
;; communications error to 5.9.164.112#53: timed out
;; communications error to 5.9.164.112#53: timed out

; <<>> DiG 9.20.11 <<>> @5.9.164.112 mrbrklyn.com
; (1 server found)
;; global options: +cmd
;; no servers could be reached

Where is your dhcpd server and who set up the name service.  This network looks totally wasted.

Re: ERR_NAME_NOT_RESOLVED on some websites only when using wlan

Reply #5 –
BTW

Code: [Select]
flatbush:[ruben]:~$ whois fritz.box
Domain Name: FRITZ.BOX                                                                                                                                  
Registry Domain ID: D426926400-CNIC                                                                                                                     
Registrar WHOIS Server: whois.namesilo.com                                                                                                              
Registrar URL: https://www.namesilo.com                                                                                                                 
Updated Date: 2025-01-13T11:58:28.0Z                                                                                                                    
Creation Date: 2024-01-22T23:06:20.0Z                                                                                                                   
Registry Expiry Date: 2026-01-22T23:59:59.0Z                                                                                                            
Registrar: NameSilo, LLC                                                                                                                                
Registrar IANA ID: 1479                                                                                                                                 
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProh                                                                        ibited
Registrant Organization: Web3 Privacy LLC
Registrant State/Province: CA
Registrant Country: US
Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: NS1.3DNS.BOX
Name Server: NS2.3DNS.BOX
DNSSEC: unsigned
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.6024928198
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2025-08-23T10:26:47.0Z <<<

For more information on Whois status codes, please visit https://icann.org/epp


Note the assigned Name Servers
Name Server: NS1.3DNS.BOX
Name Server: NS2.3DNS.BOX

Re: ERR_NAME_NOT_RESOLVED on some websites only when using wlan

Reply #6 –
flatbush:[ruben]:~$ dig NS1.3DNS.BOX

; <<>> DiG 9.20.11 <<>> NS1.3DNS.BOX
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38577
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: 160eb679ba4d00cc0100000068a9981e016a8583c144a08f (good)
;; QUESTION SECTION:
;NS1.3DNS.BOX.                  IN      A

;; ANSWER SECTION:
NS1.3DNS.BOX.           3600    IN      A       20.228.226.240

;; Query time: 146 msec
;; SERVER: 10.0.0.37#53(10.0.0.37) (UDP)
;; WHEN: Sat Aug 23 06:29:47 EDT 2025
;; MSG SIZE  rcvd: 85



***20.228.226.240*** that is the assigned DNS for the domain in your /etc/resolve.conf

Re: ERR_NAME_NOT_RESOLVED on some websites only when using wlan

Reply #7 –
BTW - everything here is messed up and unless you are the sysadmin - it is beyond your control to fix.

flatbush:[ruben]:~$ dig +trace FRITZ.BOX  

; <<>> DiG 9.20.11 <<>> +trace FRITZ.BOX                                                                                                               
;; global options: +cmd                                                                                                                                
.                       448559  IN      NS      a.root-servers.net.                
.                       448559  IN      NS      i.root-servers.net.                
.                       448559  IN      NS      j.root-servers.net.                
.                       448559  IN      NS      k.root-servers.net.                
.                       448559  IN      NS      b.root-servers.net.                
.                       448559  IN      NS      e.root-servers.net.                
.                       448559  IN      NS      g.root-servers.net.                
.                       448559  IN      NS      f.root-servers.net.                
.                       448559  IN      NS      d.root-servers.net.                
.                       448559  IN      NS      m.root-servers.net.                
.                       448559  IN      NS      l.root-servers.net.                
.                       448559  IN      NS      c.root-servers.net.                
.                       448559  IN      NS      h.root-servers.net.                
.                       448559  IN      RRSIG   NS 8 0 518400 20250904050000 202    50822040000 46441 . EbIq9qUrfPSS7Bpun5vzC6iruR0z0iweN8cS9OV9fcrFbHfYxia1sqkt L69                                                                        1Ui4fZ3yc2xKzdY36M8dBvPNDA8dhktFUUIOCjCEQibLqdoWowG01 AJH2NIIpg682PveyVemglOT2vD                                                                        AszOYi668izKiNIfhXbRzuGaX+YPck rOJ2ClWR7NgKBFs9bJID0TBZ5kiPmsiptYv20NJghPOzUPpIF                                                                        dpDWUw8 aEHu44+8RRUplPxpn/NCDNPfX43auKSmgZUmXQdTPRw6+4FG2mTtA3lD UguLYYMTuimCDic                                                                        fbng5SnYLyBVlgeVXNZffzqDys9w8Y7tLpfI8C/mJ W5ns0w==                                                                                                     
;; Received 1125 bytes from 10.0.0.37#53(10.0.0.37) in 3 ms
BOX.                    172800  IN      NS      a.nic.BOX.                                     
BOX.                    172800  IN      NS      b.nic.BOX.                                     
BOX.                    172800  IN      NS      c.nic.BOX.                                     
BOX.                    172800  IN      NS      d.nic.BOX.                                     
BOX.                    86400   IN      DS      62294 8 2 29A911BDBF1FC105D593EA                39A619BF1E89CB1BFE73FF70FB7E80B75A B9A7A8B8                                                                                                            
BOX.                    86400   IN      DS      63242 8 2 F63250257503CCE60195E7                1C2E346A2D8BDE06DCBD666B9EE4F860D7 5988702D                                                                                                            
BOX.                    86400   IN      RRSIG   DS 8 1 86400 20250905050000 2025                0823040000 46441 . c5CofVvzsMy+6IOYhaHrihZXOyBGCn67DD+BPq9Xq50ZoNbls/aNRzDi 4fDj                                                                        LStPAJegHOS3W75kfj8HoGzIaNMRQXpPLTFySowJCo7FNUPgbtGH +Eoq0kIcpN3VzVTLmTLOaBz6p/q                                                                        FTjyy/+FdIZ1eUpggVnvDJw4XULZP mx+wSn6Roa4fHGv6nsNF+AiFzWTZmj85G2fMvAekJ5Cv5baJui                                                                        TCyWEd eDmZ+LuG8hFdY0WowvDCwuqr2q55MPqb5aYhRHBJIMwGhrHCZBCgbHbv iZ8VOJ+xQpJx5G5k                                                                        CAKZw526uWoidD5Dfr1X26DHnC5gvlTrkTrv1QfZ 3619GA==                                                                                                      
;; Received 665 bytes from 193.0.14.129#53(k.root-servers.net) in 80 ms

;; UDP setup with 2a04:2b00:13cc::1:139#53(2a04:2b00:13cc::1:139) for FRITZ.BOX failed: network unreachable.
;; no servers could be reached
;; UDP setup with 2a04:2b00:13cc::1:139#53(2a04:2b00:13cc::1:139) for FRITZ.BOX failed: network unreachable.
;; no servers could be reached
;; UDP setup with 2a04:2b00:13cc::1:139#53(2a04:2b00:13cc::1:139) for FRITZ.BOX failed: network unreachable.
;; UDP setup with 2a04:2b00:13cc::1:139#53(2a04:2b00:13cc::1:139) for FRITZ.BOX failed: network unreachable.
FRITZ.BOX.              3600    IN      NS      ns1.3dns.BOX.
FRITZ.BOX.              3600    IN      NS      ns2.3dns.BOX.
m1k4m0pmes14htvf726hslvqbfohl3i2.BOX. 900 IN NSEC3 1 1 0 - OV2J9819PPF66UJFCBMB3
3GI392HJ1O7 NS SOA RRSIG DNSKEY NSEC3PARAM
44kend9dtc8m5troibn8vggq7dqjvtnp.BOX. 900 IN NSEC3 1 1 0 - B623IUVBO22CPACISKLGTASTV26S7VHR NS DS RRSIG
m1k4m0pmes14htvf726hslvqbfohl3i2.BOX. 900 IN RRSIG NSEC3 8 2 900 20250912212212 20250813195212 23355 box. UyDaf67evGJq0gOWewMpPNZC4QiZyZ0DvvgSCTQ/bT8tq0JZuCOuFLQa PwId+t++nyEUAuSWZECX1WFvoyAAGnxvAjQdSOr6vzuUHG2vbxDmxups lvb8370J0YUEqXkGHhLsOBQfQNJ3nNhuUMhTK/OcSh7QT9j0IyHeGIYn L+o=
m1k4m0pmes14htvf726hslvqbfohl3i2.BOX. 900 IN RRSIG NSEC3 8 2 900 20250912212212 20250813195212 25033 box. e1XUuozNKqxPhZ91KuMACXJZocpGWHXzgpXYpx7O8zz6e3tfBwTgnYU0 CvpE/MWypKWM88VaHrY2Y3iOZzS6K/EJFnrcPhyvwqHkO/QrglvTovDf J2QewEuI1Kq8tE2sU2e+SN3xga9mO/WDawyUJTDt14St0H3BNzrnpdkC Uhk=
44kend9dtc8m5troibn8vggq7dqjvtnp.BOX. 900 IN RRSIG NSEC3 8 2 900 20250912212212 20250813195212 23355 box. Ba8d7GMCvn6VKfiJEzDe3NFgI4FXm9sXoCSu1sUFN7AWCy1EGTUryhVh yu0cA8mlDOVL/2ezZRnwFAsenE7ntdpeD+bo1+CV6pWTuEA61Z3m34yD QJK4QmMbuWfNJ4NGXQGBmsgCc22EyD4uvoWFXjCNwbHOdFkKcQMqsSMt LcY=
44kend9dtc8m5troibn8vggq7dqjvtnp.BOX. 900 IN RRSIG NSEC3 8 2 900 20250912212212 20250813195212 25033 box. S2e/65B3NkEG7z8pOjqY5uCbJqCQdFOymibDpkSqzJALO5ocBcc9RTiT 1xmoepSQsWvqzm7VgGpW2Tgsd/iMcfuDoWq87hkSg13cN+wpT9ptmKIB Njxp9Kom4Mtq8xaequvvpHmlnyLECz/h0AcnF3mogIj20MeMCU1w71Wy aAY=
;; Received 950 bytes from 185.24.64.139#53(b.nic.BOX) in 23 ms

;; communications error to 20.231.95.96#53: timed out
;; communications error to 20.228.226.240#53: timed ou


Note the Nameservers are broken..

I just ran it again and it is now working - but service is spotty at best
Code: [Select]
3dns.box.               3600    IN      NS      ns2.3dns.box.
3dns.box.               3600    IN      NS      ns1.3dns.box.
m1k4m0pmes14htvf726hslvqbfohl3i2.box. 900 IN NSEC3 1 1 0 - OV2J9819PPF66UJFCBMB33GI392HJ1O7 NS SOA RRSIG DNSKEY NSEC3PARAM
m1k4m0pmes14htvf726hslvqbfohl3i2.box. 900 IN RRSIG NSEC3 8 2 900 20250912212212 20250813195212 23355 box. UyDaf67evGJq0gOWewMpPNZC4QiZyZ0DvvgSCTQ/bT8tq0JZuCOuFLQa PwId+t++nyEUAuSWZECX1WFvoyAAGnxvAjQdSOr6vzuUHG2vbxDmxups lvb8370J0YUEqXkGHhLsOBQfQNJ3nNhuUMhTK/OcSh7QT9j0IyHeGIYn L+o=
m1k4m0pmes14htvf726hslvqbfohl3i2.box. 900 IN RRSIG NSEC3 8 2 900 20250912212212 20250813195212 25033 box. e1XUuozNKqxPhZ91KuMACXJZocpGWHXzgpXYpx7O8zz6e3tfBwTgnYU0 CvpE/MWypKWM88VaHrY2Y3iOZzS6K/EJFnrcPhyvwqHkO/QrglvTovDf J2QewEuI1Kq8tE2sU2e+SN3xga9mO/WDawyUJTDt14St0H3BNzrnpdkC Uhk=
b623iuvbo22cpacisklgtastv26s7vhr.box. 900 IN NSEC3 1 1 0 - M1K4M0PMES14HTVF726HSLVQBFOHL3I2 NS DS RRSIG
b623iuvbo22cpacisklgtastv26s7vhr.box. 900 IN RRSIG NSEC3 8 2 900 20250912231017 20250813214017 23355 box. mdMcdNzkmH4ZUUXZZEaZWYxMiRP7C/EwauvmaBgG3wG5fIEovizgKTRx YNsQfZ8RJcMOjUf91nskzVfW0VKoCwZnQqxTskfsCoKqFGXX4P2ud+9N Naxv50XJaQ5hnySJ0ZjGyicIKnYcrd/3Hnpw7NNQSwNNY+2d8NModvrS /b4=
b623iuvbo22cpacisklgtastv26s7vhr.box. 900 IN RRSIG NSEC3 8 2 900 20250912231017 20250813214017 25033 box. AtNzsK9p0BN7ePQbmSfW2ejygQa/1BrjruH77N65pD0Vxy7zIGQA+4hM nX+z/kMkwKLqpAglXBHGxQo7Zihz8PtMr/MKl7Xza+cQ1YeO7S+zbPrq bxih3H7pOnUou1iTec1sJyfQwfvI1OIpzu10M3xZl0CWDz2ZlfuXvWYT jc8=
;; Received 956 bytes from 212.18.248.139#53(c.nic.BOX) in 23 ms

NS1.3DNS.BOX.           3600    IN      A       20.228.226.240
3DNS.BOX.               3600    IN      NS      ns1.3dns.box.
3DNS.BOX.               3600    IN      NS      ns2.3dns.box.
;; Received 137 bytes from 20.231.95.96#53(ns2.3dns.box) in 50 ms

Re: ERR_NAME_NOT_RESOLVED on some websites only when using wlan

Reply #8 –
Yeah that is NOT a DNS server, at least not facing the outside

Code: [Select]
flatbush:[ruben]:~$ sudo nmap  5.9.164.112
[sudo] password for ruben: 
Starting Nmap 7.97 ( https://nmap.org ) at 2025-08-23 06:51 -0400
Nmap scan report for dns3.digitalcourage.de (5.9.164.112)
Host is up (0.11s latency).
Not shown: 997 filtered tcp ports (no-response)
PORT    STATE SERVICE
22/tcp  open  ssh
80/tcp  open  http
443/tcp open  https

Nmap done: 1 IP address (1 host up) scanned in 7.89 seconds

Re: ERR_NAME_NOT_RESOLVED on some websites only when using wlan

Reply #9 –
BTW - that is a webserver => https://digitalcourage.de/en

Quote
Digitalcourage works for a liveable world in the digital age.

Since 1987, Digitalcourage (named FoeBuD until November 2012) advocates for fundamental rights, privacy and protecting personal data. We are a group of people from a variety of backgrounds who explore technology and politics with a critical mindset, and who want to shape both with a focus on human dignity.

The revolution will have to be postponed until the network is fixed.

Re: ERR_NAME_NOT_RESOLVED on some websites only when using wlan

Reply #10 –
You're creating more noise than signal. Please keep it short and concise, @mrbrklyn.

Quote from: user44 – on
dig stackexchange.com output:
Code: [Select]
;; UDP setup with 5.9.164.112#53(5.9.164.112) for stackexchange.com failed: network unreachable.
dig stackexchange.com @1.1.1.1 output:
Code: [Select]
;; UDP setup with 1.1.1.1#53(1.1.1.1) for stackexchange.com failed: network unreachable.
This is on wlan0, right? Try a direct ping 1.1.1.1 as @mrbrklyn suggested, it may be your fritzbox blocking things.

Re: ERR_NAME_NOT_RESOLVED on some websites only when using wlan

Reply #11 –
Quote
This is on wlan0, right?
Yes, it is.

Quote
Try a direct ping 1.1.1.1 as @mrbrklyn suggested,
This is the output:

Code: [Select]
ping: connect: Network is unreachable

Re: ERR_NAME_NOT_RESOLVED on some websites only when using wlan

Reply #12 –
Is it your install or is it your router ?
Try some livecds. If you can by wifi access the problem websites it's your install, If not it's your router.

Re: ERR_NAME_NOT_RESOLVED on some websites only when using wlan

Reply #13 –
Quote from: user44 – on
Quote
This is on wlan0, right?
Yes, it is.

Quote
Try a direct ping 1.1.1.1 as @mrbrklyn suggested,
This is the output:

Code: [Select]
ping: connect: Network is unreachable


Good we are making progress.  You have no working default gateway along with a broken DNS server and settings.  Are you supposed to access the work through a VPN or something?