In <[log in to unmask]> [log in to unmask] writes:
Warning; this is a long one...
> In a meeting today, the following questions came up about Domain Name Services
> and I thought I would post to see if anyone could help:
>
> How does one set up the HP3000 for Domain Name Services (DNS) so that a
> non-HP machine (E.g., IBM MVS) on the same network can find the HP3000
> via the node name?
This is not a simple question, in that there are a few subtleties here that
need to be expanded upon.
#1 HP3000s can have a "node name" defined in NMMGR, but this is often not
the same as a what Internet-folks think of as a domain name. The MPE node
name can only have three parts (name,domain,organization); Internet node
names can (and often do) have more levels. If, for instance, your organiz-
ation is a community college in California (where there seem to be alot of
3000s) your Internet node name is likely something like;
hp9xx.ourcollege.cc.ca.us
#2 HP3000 node names can be looked up by other 3000s (or 9000s) on the same
lan using a protocol called "probe". It serves some of the same purpose
that DNS does (i.e. it allows a system to get the machine address for a
given node name) - which is the most common use for DNS as well, but DNS
can supply many other pieces of information.
Some PC networking stacks (like RNS) will do "PROBE"s to look up hostnames
of HP3000s or HP9000s. Most non-HP networking platforms however, don't know
how to do a probe, so they either need to have hardcoded entries in a host
table or need to use DNS to lookup machines. [lookup machine= take a system
name and look up the numeric IP address of that machine]
#3 For another system to "lookup" host information about a 3000 using DNS
doesn't have anything to do with the 3000 itself. HP3000s cannot be DNS
servers [there was mention of compiling the DNS software on a 3000, but
it has been attempted and does not work - it needs support/effort from HP
and though I've been asking about that for over a year, it doesn't seem to
be forthcoming].
Therefore, you need to setup DNS on another system somewhere; the software
is available for every Unix variant (including Linux, the freeware Unix,
which we use in our office as our DNS server); you can also get DNS packages
for NT systems (and some others). If you don't have one of these (or don't
want to use one of these, I can put you in touch with someone that has done
a "partial" DNS server implementation for the 3000. If the only thing you
need is DNS responses to what can be looked up via a PROBE, then that
partial implementation will work for you. On the other hand, if you really
do need full "real" DNS, you have to run it on something other than a
3000... [*It really irks me to have to tell people that too, as I've had
to do that MANY times, and the effort required to get real DNS working on
the 3000 isn't that substantial, but it requires fixes/low-level access
which would seem to require HP people with internals access/knowledge*]
So... the short answer to your question above is "set up a DNS server on
another system".
> Does the HOST file on the non-HP machine need to have the node name/IP
> address cross reference or does there have to be a name resolver on the
> non-HP machine that is configured to look to the HP3000 as a name
> server?
Per your stated purpose above, you don't need to do anything on the 3000.
Your 3000 can however, also use DNS to lookup names of other systems. This
is the "resolver" function of DNS (as opposed to the server). To set this
up, you simply edit RSLVSAMP.NET.SYS, change the IP address to the IP address
of a DNS "server" (with multiple lines if you have access to more than one)
and change the domain name line. Then keep the file as RESLVCNF.NET.SYS, and
presto-change-o, your 3000 can lookup machine addresses (DNS "A" records).
You don't even need to stop/restart your network.
> In addition, does the non-HP machine need to be included in the HOST
> file on the HP3000 in order for processes on the HP3000 to be able to
> find the non-HP machine using the node name?
Enable the DNS resolver (as I described above). And show up at SIGNETWORKING
in ANAHEIM to try and put some more priority behind the DNS server port to
the 3000! :-)
If you have any questions, e-mail or give me a call. We deal with DNS issues
on 3000s every day (since our e-mail system also uses DNS on the 3000).
-Chris Bartram
______________________/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_
Chris Bartram Sales (US): 800 Net-Mail Fax:+1 703 451-3720
______ +1 703 569-9189 E-Mail: [log in to unmask]
/__ | \__________ Sales (Europe):+44(1480)414131 Fax:+44(1480)414134
/ / | / ________ Sales (Pacific Rim):+61 3 489 8216 (same for fax)
| /_ |< ______ Tech Support:+1 703 569-9189 Fax:+1 703 451-3720
\ __)| \ ___ E-mail: [log in to unmask] Personal(me): [log in to unmask]
\______/Associates, 6901 Old Keene Mill Rd Suite 205 Springfield VA 22150
_________________Inc._/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_
Gopher: gopher.3k.com Anon-FTP: ftp.3k.com WWW: http://www.3k.com/
|
