Nameserver Selection - Bind, PowerDNS or NSD

I am hoping to speed up my server. I am currently hosting my DNS and using Bind. It took me quite a while to correctly tweak all the DNS/Zone files so that I have no errors. I have a couple of questions:

1) If I switch from Bind to PowerDNS or NSD will it create new zone files, or somehow alter my current ones? My hope is that it will use the exiting ones, but I really have no idea what switching away from Bind would change.

2) As long as I have a resolver set up it looks like I can use PowerDNS or NSD, is one considered better for performance than the other?

3) Any other things I need to consider before switching?

 

Are there mandatory settings in pdns.conf that I need to change? It looks like the default file.

Also, the service seems to be running, but when I restart the DNS server now I see this:

Waiting for “pdns” to restart ………waiting for “pdns” to initialize ………finished.

Service Status
pdns (/usr/sbin/pdns_server --daemon) is running as named with PID 26129 (systemd+/proc check method).

Startup Log
Nov 07 10:31:32 server1.domain.com pdns[26129]: binding UDP socket to '0.0.0.0:53': Permission denied
Nov 07 10:31:32 server1.domain.com pdns[26129]: binding UDP socket to '0.0.0.0:53': Permission denied
Nov 07 10:31:32 server1.domain.com pdns[26129]: binding UDP socket to '0.0.0.0:53': Permission denied
Nov 07 10:31:32 server1.domain.com pdns[26129]: Unable to reuse port, falling back to original bind
Nov 07 10:31:32 server1.domain.com pdns[26129]: Unable to reuse port, falling back to original bind
Nov 07 10:31:32 server1.domain.com pdns[26129]: Unable to reuse port, falling back to original bind
Nov 07 10:31:32 server1.domain.com pdns[26129]: binding UDP socket to '0.0.0.0:53': Permission denied
Nov 07 10:31:32 server1.domain.com pdns[26129]: Unable to reuse port, falling back to original bind
Nov 07 10:31:32 server1.domain.com pdns[26129]: binding UDP socket to '0.0.0.0:53': Permission denied
Nov 07 10:31:32 server1.domain.com pdns[26129]: Unable to reuse port, falling back to original bind

Log Messages
Nov 7 10:31:32 server1 pdns[26129]: Unable to reuse port, falling back to original bind
Nov 7 10:31:32 server1 pdns[26129]: binding UDP socket to '0.0.0.0:53': Permission denied
Nov 7 10:31:32 server1 pdns[26129]: Unable to reuse port, falling back to original bind
Nov 7 10:31:32 server1 pdns[26129]: binding UDP socket to '0.0.0.0:53': Permission denied
Nov 7 10:31:32 server1 pdns[26129]: Unable to reuse port, falling back to original bind

 

# netstat -lnp | grep :53

Code:

tcp        0      0 0.0.0.0:53              0.0.0.0:*               LISTEN      8553/pdns_server
tcp6       0      0 :::53                   :::*                    LISTEN      8553/pdns_server
udp        0      0 0.0.0.0:53              0.0.0.0:*                           8553/pdns_server
udp6       0      0 :::53                   :::*                                8553/pdns_server

I see the errors whenever I restart the DNS Server. This link:
github.com/PowerDNS/pdns/issues/4180
pdns_server always logging "Unable to bind UDP socket..." · Issue #4180 · PowerDNS/pdns

indicates it may be normal, but I'm just not sure. It says:

"service pdns monitor starts a foregrounded pdns_server, and before that you already start a backgrounded pdns_server using systemctl start pdns. Only one instance can run at one time..."

 

After a server restart, this issue went away.

I guess the main question I still have is can I improve performance by editing the conf file for PowerDNS? I went through their site in detail and made changes to the conf as they recommended, but it actually seemed to greatly slow things down.