Arch Linux

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,346

DNS Failures on one Particular Network

I am at a loss as to how to diagnose this, so I am open to suggestions.

My laptop is currently configured to use NetworkManager using systemd-resolvd to provide network name resolution service.

/etc/resolv.conf is soft linked to /run/systemd/resolve/stub-resolv.conf
There are no *.conf.d directories in /etc/sysytemd
There are no customizations in /etc/systemd/resolved.conf (everything except [Resolve] are commented out)

Things work perfectly at home on my Asus router running Merlin firmware on a Spectrum provided cable modem.
Thing work perfectly when using my Android phone as a wireless hotspot or USB tether.
Things work at almost every hotel or guest WiFi I have evert tried to use (some issues with captive portals -- unrelated to this problem)

But, when I visit my mom's home, I cannot get any DNS resolution.  She, unfortunately, has Frontier FIOS for her phone/internet/television. 
NetworkManager connects and I get a local IP address.
I can ping 1.1.1.1 and 8.8.8.8.  Attempts to look up archlinux.org, google.com, ewaller.net (or any other domain) result in something to the effect of "domain not found".  Sorry I don't have the actual error message -- I am home now and she lives about 200km from here.  At her home, resolvectl reports the DNS server as being the address of the Frontier provided router.  The fallback servers include 1.1.1.1 8.8.8.8.  I don't recall the others.

Booting Windows 10 on the same machine works perfectly.  My Android phone on her network works perfectly.  Her MacBook works perfectly on her network, as does her iPhone.

I am going back down there next weekend.  I would sure like to have some magic arrows in my quiver before I head back.

Edit:  Two things I may try next week.  One, boot from the install media and see what happens.  Two, use openvpn to try to connect to my home router -- of course, I will need to to that by IP address

Last edited by ewaller (2019-04-07 23:16:12)

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

schard

Forum Moderator

From: Hannover

Registered: 2016-05-06

Posts: 2,163

Website

Re: DNS Failures on one Particular Network

Systemd-resolved recently changed to enforce DNSSEC by defaulting to

#DNSSEC=allow-downgrade

in /etc/systemd/resolved.conf.
However, at my company we also encountered that some ISPs probably do not correctly implement the DNSSEC downgrade protocol.
Changing

#DNSSEC=allow-downgrade

to

DNSSEC=no

quick-fixed the issue on the respective systems.

Last edited by schard (2019-04-08 08:59:36)

---

Inofficial first vice president of the Rust Evangelism Strike Force

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,346

Re: DNS Failures on one Particular Network

Thanks Schard.  I will do some research on that this week and will give it a shot next weekend.

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Slithery

Administrator

From: Norfolk, UK

Registered: 2013-12-01

Posts: 5,776

Re: DNS Failures on one Particular Network

...

I concur. I've had to do this the last few times that I've installed Arch using my current connection (Plusnet UK).

Browser(s) haven't had any problems, but pacman has timed out until I've made this edit. Using systemd-{resolve,network}d.

---

No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles