<html><body><div style="color:#000; background-color:#fff; font-family:lucida console, sans-serif;font-size:12pt">>> Greetings. I just installed Fedora 16 (x86_64) on my home computer today.<br>>> Not an altogether pleasant experience so far, I must say.<br>>><br>>> I've got one issue in particular that's really puzzling me.<br><br>[...]<br><br>>> I.e., the "host" utility CAN resolve the name, as can the "dig"<br>>> utility (not shown in the examples), but other utilities, such as<br>>> "ping" and "ssh" cannot resolve the name.<br><br>[...]<br><br>> Check the contents of /etc/resolv.conf on the main system. It probably<br>> isn't referencing itself but whatever nameserver your ISP provides. As<br>> an example, it should probably look like:<br>> <br>> search my.lan<br>> nameserver 192.168.1.72<br>>
nameserver <isp.dns.server><br><br>Very good suggestion. In fact, my resolv.conf DID have an entry for my<br>system, but it was in reverse order. I.e., to use your example, it was:<br><br> search my.lan<br> nameserver <isp.dns.server><br> nameserver 192.168.1.72<br><br>I don't understand why the resolver didn't fall through to the second<br>nameserver, but it evidently did not. After I put the nameservers in the<br>order you suggest, everything seems to be working fine!<br><br>> Resolv.conf gets rewritten every time the net initializes, so you may<br>> want to:<br>> chattr +i /etc/resolv.conf<br>> <br>> to make it immutable. (Remember to chattr -i if you nned to edit it<br>> later.)<br><br>Another good suggestion. I had forgotten about the immutable attribute. I've<br>set it now. (It's a
safe bet that in six months or so I'll be sending a note<br>to the list, whining about how I can't edit resolv.conf ;-)<br><br>Thanks for your help.<br><br>-- Mike<br><br><span></span><div></div></div></body></html>