Strange issue with name resolution systemd-resolved.service - Network Name Resolution

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

 



Currently in Nevada accessing 4 of my computers back in Guam.
Has been working fine, until earlier today.

VNC into the machines using same name of router, but different 
ports mapped to machines.

Generally login to each one, and then next with no problem.
But today, got error messages that couldn't resolve names. 
then tried dig on name and got similar timeout problem with it.

Tried restarting service, and that would work for a while, but then 
it would give error again.

IP is a dyndns.org address, so it can change, but very seldom.
Added the address to /etc/hosts and then problem went away 
completely.  Connections made with no problem. Works, unless IP 
changes. 

Don't know if something was changed with service recently, or if 
their is some way to have it have a backup if the 127.0.0.53 isn't 
working? Just says timedout? 

Any options to optimize things to prevent this? Have also seen a 
similare issue running dnf updates. Sometimes it reports that it 
can't resolve names of repos? 

Note: Cox is ISP where I'm located, so don't know. The speed is 
good, getting 175+M down, and about 11M up. 

Long ago use to use multiple name servers including 8.8.8.8, but 
then at somepoint it changed to the 127.0.0.53 thing.

Thanks.

+------------------------------------------------------------+
 Michael D. Setzer II - Computer Science Instructor (Retired)     
 mailto:mikes@xxxxxxxx                            
 mailto:msetzerii@xxxxxxxxx
 mailto:msetzerii@xxxxxxx
 Guam - Where America's Day Begins                        
 G4L Disk Imaging Project maintainer 
 http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+


--
_______________________________________________
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