Original Question Attached.
Thanks for all the answers guys.
Effectively the anser was 'depends what you want', 'there is no normal'.
nsswitch.conf for host may be;
files, nis, dns - for speed if it's local, speed and accuracy in a nis
domain which may be part of a 10000 node site thus having many nis
domains acting like little networks with separate admins, and dns for
the outside nis bit (in this scenario there would be necessary
duplication). Of course dns is necessary at the very least so the 'net
can find out who you external facing machines are.
Duplicates - see above.
Some people used no nis so everything was in one place - I can't see
this being quick in a very large site.
Others said dns,nis,files - not really sure why.
No concrete answers then, there's more than one way to skin the UNIX
Thanks all for your help.
-- Stephen Johnston Phone: +49 89 32006324 UNIX Sysadmin Fax : +49 89 32006380 European Southern Observatory Karl-Schwarzschild-Strasse 2 D-85748 Garching bei Muenchen Linux: Room 201
attached mail follows:
According to Hal Stern's NFS and NIS, NIS can try to resolv and on
failure ask DNS for the requesting client. Alternativle NIS can return
and the client can ask DNS.
What is the correct order for _most_ of the services as configured in
/etc/nsswitch.conf is it local,NIS,DNS ?
Is there any reason to have duplicated information in DNS and NIS?
What's normal to have in either then?
TIA, I'll summarise.
-- Stephen Johnston Phone: +49 89 32006324 Linux/UNIX Sysadmin Fax : +49 89 32006380 European Southern Observatory Karl-Schwarzschild-Strasse 2 D-85748 Garching bei Muenchen
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:23 CDT