thos@gargoyle.uchicago.edu (Tom Barron) (08/10/88)
----------
I just set up a 4000 with TCP/IP 3.1 on top of SR 9.7 4000. I also put up
DOMAIN IX TCP/IP 3.1 on top of Domain IX 9.5. The Domain IX TCP/IP works
as expected but I have a problem resolving host names with the Domain TCP/IP
product. I called 1-800-2APOLLO about the problem: the fellow who dealt
with the call ended up sending mail to the development people to check
on it. While I await a reply from Apollo I thought I'd check the net ....
I just ftp'ed in a fresh copy of hosts.txt from SRI-NIC.ARPA (using the
Domain-IX product, for reasons that will become clear shortly), put it in
/sys/tcp/hostmap, and ran makehost.sh without any errors. When I issue
host sri-nic.arpa
(or the corresponding command for any other host beyond our campus network)
I get
host: bad host: host not found
The corresponding telnet and ftp commands yield, respectively,
telnet: Unknown host specifier: "sri-nic-arpa"
Unknown host name: 'sri-nic.arpa'
The corresponding commands for the short nickname forms of local campus
hosts work fine, e.g.
telnet gargoyle
but using the fully qualified, official name fails. Specifically,
host gargoyle.uchicago.edu
yields
host: bad host: network not found.
while telnet and ftp yield the same sort of message as before.
Incidentally,
host 26.0.0.73
yields the hostcap entry for sri-nic.arpa just fine.
The problem appears to have something to do with the use Domain TCP/IP makes
of the network entries in the host tables. The command
host gargoyle.u-chicago
works and the NIC tables list net 128.135 as u-chicago. I can't get any
corresponding nonlocal commands, e.g. :-}
host sri-nic.arpanet
host sri-nic.milnet
to work.
Does anyone know what's going on here?
- Tom Barron
thos@gargoyle.uchicago.edu