Migration of Bind from 4.x to 8.2.2p5

[Barry Margolin]

In article <003d01bfb114$f870af60$6a699ec0 at india.tek.com>,
Mallik Prasad <mallik at india.tek.com> wrote:
>Hi,
>
>I am looking forward to migrate from Bind 4.x to Bind 8.2.2p5 on Solaris
>2.6.
>
>Could anybody share their experience of migration/upgradation with me, what
>are the catches, what are the things need to watch out for.
>
>The process of migrating if anybody has any documentation, will be very
>helpful.

Use named-bootconf to convert the named.boot file to named.conf format.

The common gotchas are:

BIND 8.2.2 strictly enforces the "no CNAME and other data" rule, whereas
previous releases just warned.

BIND 4.9.5 and up default to "check-names primary fail", so names with
underscores will be rejected.  You can change the check-names option to
relax this if necessary.

BIND 8.2.2 requires you to set the default TTL using the $TTL directive,
rather than using the MinTTL field in the SOA record (but if there's no
$TTL directive it will fall back to the old behavior and log a warning).

BIND 8 uses a dynamic source port for recursive queries, rather than port
53.  If your firewall doesn't allow random high UDP ports back into the
nameserver, you either have to change the firewall configuration or use the
"query-source" option (I believe the named.conf that the above script
creates has this as a commented-out line -- just uncomment it).

-- 
Barry Margolin, barmar at genuity.net
Genuity, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.