Enough of the "turn it off and turn it on" again answers. This is a bug.
Originally Posted by John Nagle Enough of the "turn it off and turn it on" again answers. This is a bug. You haven't even followed all the advice you received in this thread, but you're already determined it's a "bug". You're not going to get much help until the attitude is adjusted.
Originally Posted by currentshaft There's really no good reason to use your ISP's default DNS, and many reasons to avoid it. Can you reproduce this with another DNS provider? Also, use "dig" instead of nslookup to do network troubleshooting, e.g.: dig a ubuntuforums.org dig a ubuntuforums.org @1.1.1.1 +1 for all of this. During initial setup of my systems, I purge systemd-resolved and manually configure DNS to use my LAN DNS servers. For most home users, the router can be chosen. I don't have AT&T, so I don't know if their equipment will serve as a DNS or caching DNS, but it probably can. Since none of us works on the systemd-resolved code, telling us it is a bug isn't useful. Did you add your information to the existing bug report? That's how to help that team. All we can do is suggest things to get passed the issue. Nobody here works for Canonical and nobody here is being paid.
Last edited by TheFu; July 24th, 2024 at 12:12 PM.
View Tag Cloud
Ubuntu Forums Code of Conduct