Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
My understanding is the resolv.conf file is for connecting local clients to the internal DNS stub resolver of systemd-resolved.
If you type resolvectl status you will see your external DNS
That address/port is probably 127.0.0.1:53 or similar.
53 is the default port for non-encrypted DNS lookups, 127.0.0.1 is an internal (local) IP address.
I’m sure that you misread it. “Universally,” the local gateway address (“your router”) is 127.0.0.1, and it provides DNS services as well as DHCP. Jeremy is undoubtedly right.
— Edit: “Never mind. The right answer is just below.
Last edited by sundialsvcs; 01-23-2024 at 05:23 PM.
My understanding is the resolv.conf file is for connecting local clients to the internal DNS stub resolver of systemd-resolved.
If you type resolvectl status you will see your external DNS
Cheers, this is it
Current Scopes: DNS
DefaultRoute setting: yes
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 149.112.112.112
DNS Servers: 192.168.1.1
9.9.9.9
149.112.112.112
DNS Domain: ~.
lan
Or at least part of it, I know I set the dns to 9.9.9.9 as an experiment a while ago, but I can't recall how I made it permanent.
127.0.0.1 is the local loopback adapter that exists on just about every networked enabled device. This allows you to run a network service without needing a physical network adapter. cups typically runs only on localhost by default as well as most database servers like mysql and postgresql. The local loopback network is 127.0.0.0/8 which has valid addresses from 127.0.0.1 - 127.255.255.254
The first line in your /etc/resolv.conf file probably is something like:
Quote:
# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
As posted systemd-resolved is a stub resolver and as posted does listen on 127.0.0.53. Mint automatically installs and configures systemd-resolved. It is called a local DNS stub listener and I believe one of its features is a DNS cache as well as name resolution for LAN networks without a DNS. The stub resolver forwards requests to your router (192.168.1.1) which forwards requests to your ISP DNS 149.112.112.112
You might of added the 9.9.9.9 DNS address in Network Manager.
127.0.0.1 is the local loopback adapter that exists on just about every networked enabled device. This allows you to run a network service without needing a physical network adapter. cups typically runs only on localhost by default as well as most database servers like mysql and postgresql. The local loopback network is 127.0.0.0/8 which has valid addresses from 127.0.0.1 - 127.255.255.254
The first line in your /etc/resolv.conf file probably is something like:
As posted systemd-resolved is a stub resolver and as posted does listen on 127.0.0.53. Mint automatically installs and configures systemd-resolved. It is called a local DNS stub listener and I believe one of its features is a DNS cache as well as name resolution for LAN networks without a DNS. The stub resolver forwards requests to your router (192.168.1.1) which forwards requests to your ISP DNS 149.112.112.112
You might of added the 9.9.9.9 DNS address in Network Manager.
Absolutely correct, my memory is just getting so bad, I must make more comprehensive notes
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
My DNS - 127.0.0.53
