We have used DNS for name resolution for all our TCP/IP services, including
ftp and Reflection VT-MGR, for some time, and it does work splendidly.  All
that was required on our (HP3000) side, was to correctly set up
RESLVCNF.NET.SYS.  Now we just need to depend upon the DNS name servers
somewhere out in the ether cloud.  :-)
A sample of our setup (addresses changed to protect my job):

#
#domain local-domain.hp.com
#search local-domain.hp.com other-domain.hp.com hp.com
#nameserver 192.1.1.1
#nameserver 192.1.2.1
#
domain my_domain.com
nameserver   999.999.999.999       <<----  primary nameserver
nameserver   888.888.888.888       <<----  secondary nameserver


Lee Gunter          [log in to unmask]




From: [log in to unmask] on 06/30/98 05:12 PM

Please respond to [log in to unmask]


To:   [log in to unmask]
cc:    (bcc: Lee Gunter/BCBSO/TBG)
Subject:  Re: name resolving




(Duane after Donna after Duane)

<magna deletia>
I believe your solution is to setup the RESLVCNF.NET.SYS file following
the instructions internal to this file and then voila! you are
golden/cooking with gas/good to go/in like flint/made in the shade
or whatever phrase you use to indicate a working situation.
BTW, the file does NOT exist on your 3k system as RESLVCNF.NET.SYS. It
comes as RSLVSAMP.NET.SYS. This also can cause some confusion.