[1633] in Kerberos
rlogin problem is name server problem
daemon@ATHENA.MIT.EDU (Jamey Maze)
Fri Nov 8 12:40:31 1991
Date: 8 Nov 91 16:37:21 GMT
From: jnm@ornl.gov (Jamey Maze)
To: kerberos@shelby.Stanford.EDU
I posted a question last week about having a problem with being able to rlogin to a particular host. The error I got was:
Hostname did not resolve to an address, so Kerberos authentication failed
Several of you kindly pointed me to the problem. As it turned out, the problem
was in a secondary BIND name server that I'd setup on a DECstation 5000 named
sws9 (ULTRIX 4.2). I am not able to rlogin to any host where I configure the
/etc/resolv.conf file to point to sws9. If I point the host to one of our other
name servers, it works fine. (Our other name servers are running a "named" built
from the Berkely distribution, not sure what version...)
The confusing thing to me is that the sws9 name server seems to work fine for
everything else. From nslookup, I can't see anything wrong and applications like
telnet, ftp, etc. seem to not be bothered at all.
The reason I still want to get this name server running is because DEC has
already integrated Hesiod into the BIND they provide with ULTRIX. I'd really like
to get a Hesiod server running, and since I'm not a BIND expert, I'd really
rather not have to start with the Berkeley distribution.
Would anyone have an idea as to what about this name service might be tripping up
these Kerberized "r" utilities, yet not bothering other applications?
Your help is appreciated...
--
Jamey Maze | Computing & Telecommunications Division
Oak Ridge National Lab | Advanced Technology Group
P.O. Box 2008, MS-6238 | Internet: jnm@ornl.gov
Oak Ridge, TN 37831-6238 | 615/574-6355, FAX 615/574-9646
"Years ago my mother said to me, 'In this world, Elwood, you must
be oh so smart or oh so pleasant.' For years I was smart. I
recommend pleasant." - Elwood P. Dowd, "Harvey"
