Hi,
maybe some of our users might help us out with this? We could probably
go into lengths, so assuming you already have a Knot DNS configured
and zones in place (bootstrapped or copied-in), you could:
1. start Knot DNS side by side with the PowerDNS but on a different
port (say 53535)
2. create a firewall rule to redirect all the incoming traffic to the
port 53 to the 53535
3. shut down the PowerDNS instance, edit the Knot DNS configuration to
listen on both 53535 and 53 (reload doesn't interrupt the service)
4. remove the firewall rule
5. now you're running Knot DNS without any interruption in service
Good practice is to start out on a single/few less important nodes and
see how it goes.
We don't have any scripts or 1:1 conversion tools for configuration
import from other servers, so you probably have to figure that out,
but presuming it's a slave server it should be straightforward if you
peek in the documentation
https://github.com/CZNIC-Labs/knot/blob/master/doc/configuration.rst
Kind Regards,
Marek
On 4 January 2015 at 02:55, Ret Law <retlaw144(a)yahoo.com> wrote:
How would one go about converting from PowerDNS to
KnotDNS on an active
realtime AnyCast DNS network with maximum seamless efficiency or minimal
temporary disruption of services to existing DNS users?
_______________________________________________
knot-dns-users mailing list
knot-dns-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users