IPv6 BIND DNS Setup Questions

0.o · 01-15-2011, 02:04 PM

Hello,

Currently I have two IPv4 DNS servers setup that are hosting ~200 different zones and we want to setup IPv6 on these systems so we can resolve both address classes. Has anyone done this? What would the best route be to setup services on these? Should I use the same host names for both IPv4 and IPv6? If I did this the IPv6 records shouldn’t be requested unless the application / system requests AAAA records? I will update with more questions as they come to me…

knetknight · 01-16-2011, 02:59 PM

Quote:

Has anyone done this?

Hello, I've run dualstack v4/v6 DNS servers for years and this should be no problem.

Quote:

What would the best route be to setup services on these?

Do you mean you need IPv6 access in the first place? If so, I'd recommend http://tunnelbroker.net.

Quote:

Should I use the same host names for both IPv4 and IPv6?

I run all my Linux servers (not just DNS) dualstack anymore, can't think of a good reason not to.

Quote:

If I did this the IPv6 records shouldn’t be requested unless the application / system requests AAAA records?

Running dualstack won't make any difference in this regard. DNS servers will always attempt to answer whatever they are asked. It doesn't matter which stack the query comes in on, it only matters what kind of record the client asked for and whether or not the DNS server can provide the answer. If the client asks for an A record, it'll get an A record. If it asks for an AAAA record, it'll get an AAAA reply.

Hope that helps, let me know.

0.o · 01-16-2011, 05:28 PM

Quote:

Originally Posted by knetknight

Do you mean you need IPv6 access in the first place? If so, I'd recommend http://tunnelbroker.net.

This will be hooked up to a 40Gbit backbone that is running IPv6. Tunnels will not be needed.

Quote:

Originally Posted by knetknight

Running dualstack won't make any difference in this regard. DNS servers will always attempt to answer whatever they are asked. It doesn't matter which stack the query comes in on, it only matters what kind of record the client asked for and whether or not the DNS server can provide the answer. If the client asks for an A record, it'll get an A record. If it asks for an AAAA record, it'll get an AAAA reply.

Hope that helps, let me know.

This does help. I was thinking that it would work that way, just wasn't 100% sure. Thanks!

knetknight · 01-16-2011, 05:42 PM

That is awesome that you have native IPv6 connectivity. I've been using IPv6 for years but haven't yet had a provider who offered it native so I've always had to tunnel -- I'm seriously jealous. :-) (Well, one provider did offer v6 addresses, but even they were tunneling through he.net). I seriously can't believe IPv6 isn't more mainstream already, I can hardly live without it.

A couple things (that you may already know or may not apply to you) but should be considered for full functionality:
1. Of those domains, they may want to update their glue records to reflect that their Nameservers now have IPv6 addresses.
2. Consider adding AAAA records for each zones NS records so that clients who ask for a domains NS records will see that they are IPv6 accessible.

Let me know if any questions, but for the most part it's honestly pretty straight forward.

Regards