The question:
> We recently upgraded from v2.0b to v3.2 on an Alpha 2000/300. Most
> everything went fine (forgot about the TIA host license file, forgot
> about the BOOTP stuff, etc. :^) but we're having an odd problem ...
... and details of DNS woes ...
I got a response from Knut Helleboe (Knut.Hellebo_at_nho.hydro.com) which
didn't answer the problem directly (we weren't running routed on this
box) but inspired me to look for other should-not-be-running daemons.
The answer:
It would appear that we went through the bindsetup and designated that
this machine should be a BIND server - not client. Further, we managed
to declare it as a primary server and neglected to tell it about any of
the legitimate DNS servers we're using. I'm not sure how it was able
to recognize some of our systems now, but after switching it back to a
BIND client setup - it's much better. (Bad named, bad bad!!)
The moral:
Next time (when we upgrade our other Alpha next month) we'll make sure
to keep a closer eye on the configuration ... and not assume problems
are related to the rapid progression of 3.2->3.2a->3.2b->3.2c (we are
using 3.2 and should order the latest media again).
Thanks for the tip, Knut! :^)
andrew. (brennan_at_hal.hahnemann.edu)
Received on Thu Aug 03 1995 - 02:25:54 NZST