From: Jonathan Williams (jonathw@shubertorg.com)
Date: Fri May 09 2003 - 12:18:36 EDT
Hi. We currently use one of our Alphas (running 5.1a) as an internal DNS
server--at one time it was our only DNS server. Recently (well, about 2 years
ago anyway) we added a bunch of NT DNS machines that most everything in the
company uses for their DNS servers. Only a few machines use the original Alpha
for DNS. So I was thinking of switching everything over to the NT machines, and
do away with DNS running on the Alpha.
Currently none of our Tru64 Alpha boxes use the NT DNS. So I just wanted to
make sure it would work OK before making any big decisions. So I took my little
AlphaStation 200 named Tommy (running 5.1a patchkit 3), and pointed it at the NT
DNS server. Of course everything works just fine, except for one odd thing:
When I FTP to this workstation from any other machine, it immediately says
"Connected to tommy", but then there is a long delay (about a minute I'd say)
before I get the login prompt (long enough for Big Brother to consider the FTP
service to be DOWN). If I point this machine back to the Alpha DNS server,
there is no delay at all. I've seen this sort of behavior with Telnet in the
past, and that turned out to be because the reverse lookup on the DNS wasn't
working. As soon as we fixed the reverse lookup, the delay went away. So that
was the first thing I checked in the ftp situation, and I can nslookup little
Tommy both forwards and backwards no problem.
Other than FTP, everything seems to be working OK. Telnet is fine, even sftp2
works just fine. Has anyone seen this sort of odd delay before? Any help would
be greatly appreciated.
Jonathan Williams
Unix Systems Administrator
The Shubert Organization, Inc.
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:18 EDT