----------
From:   Alan AMBERS[SMTP:[log in to unmask]]
Sent:   Tuesday, May 14, 1996 10:52 PM
To:     Multiple recipients of list HP3000-L
Subject:        Re: Probe vs DNS ...was NMMGR NSDIR vs. HOSTS.NET.SYS
 
Some time on Tuesday, Jeff said  [boy, I wish my mailer would do this]
 
> Unless HP has tweaked some things, probe protocol is the front-line
query
> made when establishing a connection (in most cases, not sure about new
BSD
> things).  There was some discussion awhile back about the order of the
name
> resolution queries between probe, HOSTS.NET, NSDIR, and DNS but I =
don't
> recall that it was ever answered 100%.
>
> Bottom line -- if your machines are initiating lots of connections =
with
> (an)other 3000(s) you might improve the connection time by leaving =
probe
      ^^^^^
 
I was not specific enough on my original post.  I am refering to PCs
connecting to HP3000, NOT HP3000 to HP3000.
 
/alan
[log in to unmask]
 
Alan,
 
Probe is front-line if using a termulator such as Reflection, =
etc...although Reflection Net Series is configurable to resolve via =
Probe, DNS and Hosts file - in the order you specify...
 
We use, of course, probe as the first line...but we also run DNS on an =
NT server=20
<plug>
using Metainfo's DNS service (http://www.metainfo.com for a 30-day full =
functioning free trial version - $450 to buy)
</plug>
and a HOSTS file on the PC...  We resolve the order of Probe, HOSTS, DNS =
(to keep the DNS lookup activity on the server down)...this seems to =
work for us and our customers...
 
As for DNS for the 3000 - it's not there (yet?).  As a matter of fact, =
our 3000 is configured to to resolve via the NT DNS service as well, if =
not found on the 3000's HOSTS file!  It too, works well...(we FTP all =
over the place, it seems, and comes in handy :)
 
Joe Geiser