On Feb 14, 2013, at 11:46 AM, Mailinglists wrote:
> I'm looking to migrate all of the zone data from one installation of Bind to
> another...hardware move. One machine is very old but running a pretty modern
> version of Bind 9.6-ESV-R8. The other server is running Bind 9.8.2 and is in
> use, so I'm merging existing zone data with new data, although none of the
> zones will overlap.
>
> The problem I see is that the actual zone files, the way they are structured,
> are in an old format. Bind 9.6 must still understand them, but I don't think
> they are structured the "proper" way. I was hopeful there was an export /
> import procedure whereby that process would sanitize the zone info and log
> any errors for manual fixing.
>
> Either this process is dead simple and so nobody documents it or it is all
> but impossible so nobody documents it...I'm not sure. But an hour of web
> searches hasn't turned up much, just lots of info about migrating to or from
> a Windows based DNS to BIND.
named-compilezone is your friend here.
I use this 3 line script to sanitize inputs when I'm migrating customers from
their old platform to our appliances:
#!/bin/bash
mv $2{,.orig}
named-compilezone -i none -k ignore -o $2 $1 $2.orig
Chris Buxton
BlueCat Networks
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
