-
16th January 2005, 06:15 PM
#1
DNS Broken as Result of Latest UP2DATE
As a result of my latest (January 14, 2005) update of FC3 system using UP2DATE, my DNS now fails to resolve host addresses using the DNS servers. Has anyone else experienced the same problem and, more importantly, come up with a solution?
The update included a new Kernal and several othe RPM's, so I'm not sure which was responsible for my problem.
The condition first manifest itself when I tried to run UP2DATE the next day (January 15th) and found that UP2DATE hung on the "Progress Dialog" screen trying to connect to the "headers.info" server.
I soon discovered that none of my TCP/IP applications and utilities could resolve host addresses unless I made a manual entry in the hosts file.
Any ideas?
-
16th January 2005, 11:12 PM
#2
Not sure if you meant running a server or just connecting to the net, etc.
After the latest update, I too had the same problem. I could ping my router and other XP machines on the local side. My machines could also ping my FC3 box.
I went so far as to reinstall FC3, with no luck this time!
It ended up being that my eth0 was set to NOT allow any user to activate/deactivate.
I simply checked the appropriate box, let the networkmanager start at boot and RESTART THE PC.
Now doing my updates from the clean install as we speak.....
-
16th January 2005, 11:14 PM
#3
can you post your zone file? and /etc/resolv.conf
-
16th January 2005, 11:18 PM
#4
What is the "zone" file?
Does resolv.conf change on its own (ie. It would be different if I took my laptop to another network)?
-
16th January 2005, 11:28 PM
#5
oh i'm talking about server
-
23rd January 2005, 09:27 AM
#6
Hello:
I updated NetworkManager using APT and Synaptic and I lost the network , after some time I noticed that just I couldn't reach my ISP DNS servers despite I saw them in the system-config-network so I uninstalled NetworkManager and edited /etc/resolv.conf
I ignored the warning:
"; generated by NetworkManager, do not edit!"
"; Use a local caching nameserver controlled by NetworkManager blah, blah, blah"
and changed "nameserver 127.0.0.1" to my real ISP DNS server ip, restarted the network and evething is fine again.
I hope this can help
Last edited by quazart; 23rd January 2005 at 09:34 AM.
-
6th February 2005, 05:31 AM
#7
I also had the same issue after an up2date. I just deselected "allow all users to enable and disable the device" - saved. Then I selected it again and saved once more. All is well again.
Not sure why, but I am guessing some config file was screwed somewhere.
Thanks to KCNY for the tip.
Similar Threads
-
By GODhack in forum Using Fedora
Replies: 12
Last Post: 12th September 2009, 11:26 AM
-
By soxfan in forum Using Fedora
Replies: 7
Last Post: 19th December 2008, 09:10 PM
-
By michaelchan in forum Servers & Networking
Replies: 0
Last Post: 24th October 2005, 07:34 PM
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
[[template footer(Guest)]]