Thanks to all who responded, problem solved, thanks to Ray's sound advice.
Apologies for breach of netiquette.
Kind regards
Tony
> I added the linux-newbie list back to this exchange; it is
> courteous to keep
> requests for help on lists, not change them to requests for
> private advice.
>
> The "right" way depends on the details of your setup. The Linux host needs
> to have a way to resolve hostnames. The two standard ones (as
> listed in the
> nsswitch.conf line) are:
>
> 1. "files": this means check the contents of /etc/hosts
> 2. "dns": this means use the nameserver(s) listed in
> /etc/resolv.conf
>
> Which is right for you (or what mix of the two, perhaps) depends on the
> details of your setup. One common solution that works nicely for
> small LANs is:
>
> A. in /etc/hosts, list all the IP addresses in use on the LAN and
> associate a hostname with each one. This handles on-LAN resolution.
>
> B. in /etc/resolv.conf, list the nameserver addresses provided by
> your ISP. This handles all off-LAN resolution.
>
> The other basic option is to run BIND (named) on the Linux host
> itself. You
> give named a local config file for the on-LAN hosts and, for
> off-LAN stuff,
> tell it either to use the ISP's nameservers as forwarders or to start
> directly with the root nameservers.
>
> Which of these options (or vraiants of either) is best for you depends too
> much on the fine details of your setup for me to offer an intelligent
> opinion. How the other machines on the LAN do name resolution also matters
> to what is best for the Linux host.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
