Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(ASCEND) bind-8.1.1 upgrade
I'm in the process of upgrading deprecated bind-4.x.crusty to 8.1.1.
Due to previous
engineering efforts beyond my control some time ago in a land far, far
away, the radius
server was placed on the same machine as the primary DNS. Upon
switching on bind-8.1.1,
the radius database begain to complain (incorrect NAS port... etc.) and
remote access
server (a Max 4000 HP) stopped taking calls/refused to behave in a
normal fashion. I
assume that all of this has to do with something I missed when warming
over/correcting
the broken DNS config (I know, if it's not broken, don't fix it (unless
it's a security
problem)). That's why I SIGINTed both the original config, bind-4, and
the new config,
bind-8, to compair the databases. I couldn't find any differences that
would explain
behavior I observed. I did note that the named.config says something
about enabling
port 53. I'm going to have to do a go-around for this evening, but I'll
be back in to
do the change over to 8.1.1 at 3am some other day. I'de like to come
back in knowing
that everything will work with the Ascend (core) equipment. Any help,
thoughts, anecdotes
or healthy ribbing would be appreciated.
Thanks in advance...
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>