We do have a lot of CMS DNS usage. We run our Linux DNS which gets loads/updates from our Desktop servers which control dhcp etc. We need the VM Namesrv for reliability over the desktop servers. So, if I don't have to rebuild the 'HOSTS' file each night, all the better.
Thanks for that new bit of info, (probably should have RTFM a bit better, as I just now did) Richard Feldman Senior IT Architect Kelly, Douglas / Westfair Foods Ltd. Ph:(403)291-6339 Fax:(403)291-6585 -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Monday, July 17, 2006 9:13 AM To: [email protected] Subject: Re: VM/TCPIP question On Monday, 07/17/2006 at 08:57 CST, "Richard Feldman (WFF)" <[EMAIL PROTECTED]> wrote: > Does this mean that if you are using a DNS, in our case a > Namesrv as a secondary caching DNS, that you don't require the 'HOSTS' > set of files? Correct. The hosts files are used according to the DOMAINLOOKUP specification in TCPIP DATA. The default is to look in the hosts files only if not found in the DNS. If you want to *override* a DNS entry, then you need to code "DOMAINLOOKUP FILES" so that the hosts files are searched before the DNS. I should also say that unless you have very heavy usage of DNS, there's no point in running a caching name server on VM. Just let the requests flow out to the network. Linux can have its own DNS cache (man dnscache) and so won't benefit from a central cache. The VM caching-only name server was designed for non-caching DNS clients such as CMS. Alan Altmark z/VM Development IBM Endicott
