In article <[log in to unmask]>, Jim Wowchuk <[log in to unmask]>
says:
 
>[snip...]
>This is an either/or situation.  If you enable RESLVCNF then HP networking
>will no longer look in the HOSTS file.  If RESLVCNF does not exist (is not
>enabled) then HP networking will look in the HOSTS file (if it exists).
>
>Some months ago I had discussions with some of the networking lab people,
>suggesting that it would be useful to enable a name search to use *both*,
>perhaps in a user-defined sequence - much like can be done with WRQ's RNS.
>I've seen problems on particularly large DNS sites, where getting a new DNS
>entry established can take days, if not weeks.  If the System Manager could
>simply add it to their HOSTS file, they could be working in minutes.
>
>HP's answer? "That would be an enhancement request, and would need to go
>through the normal channels and protocols for evaluation, resource
>allocation and scheduling!".  I think that's a "No.".
>
 
There are security related issues to. We do not necessarily want to
advertise all our system names on DNS where curious teenagers up late
at night can see them. However, we want to be able to see them
internally, so we make a HOSTS file for us locally and put everything
else in DNS. Until DNS can make an "internal/external" distinction,
this is the only way to get this working.
 
The MPE guys need to talk to the HP-UX guys. The ability to resolve
names through multiple mechanisms is now
available in HP-UX 10.0 and in fact is available through patches for
9.0.  Now normally I wouldn't mention the "U" word in this group, but
here's an example of how MPE users should pressure HP to provide the
same basic functionality on both platforms. It's not like it's a huge
project either.
 
 
 
mark