Re: caching name server and 127.0.0.53

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

 



On 10/27/24 15:23, ToddAndMargo via users wrote:
Hi All,

Fedora 39

I am running a caching named server (named-chroot).  It
is listening on 127.0.0.1.  The WAN IP address comes from
the DHCP on my DSL modem.

Problem: the accursed systemd-resolved changes
/etc/resolv.conf

from
     nameserver 127.0.0.1
     search .

to
     nameserver 127.0.0.53
     options edns0 trust-ad
     search .

Meaning no DNS resolution until I vi resolv.conf
every time I boot up, which is what my web searches
tell me to do.

<editorial comment> AAAAAAAHHHHHH!!!!!! </editorial comment>

How do I tell systemd-resolved to stop this annoying behavior.

-T

"options edns0 trust-ad" seems like a good thing

.


Figured it out.

My web search show this being a complete pain-in-the-neck
(not my actual words) for a lot of folks.

And to add insult to injury, systemd-resolved is required
for various other packages to upgrade.

Thank you all for all the help and tips so far
cleaning up my install.

-T


This is my work around which survives a reboot:

<resolv.conf.127.0.0.53.problem.txt>

resolv.conf: 127.0.0.53 issue

reference: https://www.youtube.com/watch?v=zzFbFEOgtY0


1) stop systemd-resolved
     # systemctl stop systemd-resolved.service

2) make sure it is stopped with
     # systemctl stop systemd-resolved.service

3) create your own seed resolv.conf file.  Note that
   the _xx is arbitrary.  You just have to remember
   what you called it.

      # vi /etc/resolv.conf_rn
      namespace 127.0.0.1

4) erase or rename resolv.conf
      # rm /etc/resolv.conf

5) create a symbolic link to your seed
      # ln -s /etc/resolv.conf_rn /etc/resolv.conf

6) start systemd-resolved
     # systemctl start systemd-resolved.service

7) check resolv.conf
     # cat /etc/resolv.conf

</resolv.conf.127.0.0.53.problem.txt>
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux