On Sat, 2011-01-01 at 12:59 -0600, Robert G. (Doc) Savage wrote: > On Sat, 2011-01-01 at 16:51 +0000, Dick Holland wrote: > > Doc, here's /etc/nsswitch.conf: > > > > # > > # /etc/nsswitch.conf > > # > > # An example Name Service Switch config file. This file should be > > # sorted with the most-used services at the beginning. > > # > > # The entry '[NOTFOUND=return]' means that the search for an > > # entry should stop if the search in the previous entry turned > > # up nothing. Note that if the search failed due to some other reason > > # (like no NIS server responding) then the search continues with the > > # next entry. > > # > > # Valid entries include: > > # > > # nisplus Use NIS+ (NIS version 3) > > # nis Use NIS (NIS version 2), also called YP > > # dns Use DNS (Domain Name Service) > > # files Use the local files > > # db Use the local database (.db) files > > # compat Use NIS on compat mode > > # hesiod Use Hesiod for user lookups > > # [NOTFOUND=return] Stop searching if not found so far > > # > > > > # To use db, put the "db" in front of "files" for entries you want to be > > # looked up first in the databases > > # > > # Example: > > #passwd: db files nisplus nis > > #shadow: db files nisplus nis > > #group: db files nisplus nis > > > > passwd: files > > shadow: files > > group: files > > > > #hosts: db files nisplus nis dns > > hosts: files dns > > This is your resolution order -- local files (/etc/hosts) first, then > DNS. This is the default setting, so it's probably not your problem. > > > > > # Example - obey only what nisplus tells us... > > #services: nisplus [NOTFOUND=return] files > > #networks: nisplus [NOTFOUND=return] files > > #protocols: nisplus [NOTFOUND=return] files > > #rpc: nisplus [NOTFOUND=return] files > > #ethers: nisplus [NOTFOUND=return] files > > #netmasks: nisplus [NOTFOUND=return] files > > > > bootparams: nisplus [NOTFOUND=return] files > > > > ethers: files > > netmasks: files > > networks: files > > protocols: files > > rpc: files > > services: files > > > > netgroup: nisplus > > > > publickey: nisplus > > > > automount: files nisplus > > aliases: files nisplus > > > > ------------------------------------------------------------------ > > > > > > Thanks for your amazingly quick response! > > I'm kinda amazed I was up at that hour on New Year's Day! :-) > > >From /etc/resolv.conf in your first message I see your DNS search order > is: > > nameserver 192.168.181.254 > nameserver 194.168.4.100 > nameserver 194.117.134.19 > > and your /etc/hosts contains: > > 192.168.181.122 cobalt.xegetix.com cobalt # Added by NetworkManager > > >From this I'd say you're running a local DNS service on your local > gateway router. Was that your intent? If not, reconfigure NetworkManager > to remove that entry (and regain access to that third external DNS > server). > Yes, that's correct. I use a local DNS server as I've other boxes on the LAN with static IP addresses. I have tried removing the local DNS server and using all three of the ISP's DNS servers; the results, unfortunately, were exactly the same. So I'm completely stumped. It must be something I'm doing wrong - it seems to me to be improbable that F14 does this out of the box for others without getting fixed pretty quickly! BTW, the box uses a pretty standard Gigabyte motherboard with an onboard Realtek gigabit ethernet port, so I'm sure it's not the hardware's fault. The fingers all point to me, don't they? -- Dick Holland -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
