Talk:Djbdns

From SixXS Wiki

Removing mention of IPv6 transport and ucspi-tcp patches

Because I--the author of these statements--am unsure of what exactly the patches do for the djbdns components. I think the ucspi-tcp patch would allow tinydns and its variants to bind to an IPv6 address, but I am not sure in this specific case. It is also unclear to me what this does for udp bindings and whether it effects outbound IPv6 transport. As I understand it no djbdns components will parse IPv6 addresses, so for example dnscache should be unable to forward queries to IPv6-based recursive servers or reach IPv6 root servers. The quoted sections I removed follow. JNN2-SIXXS 22:00, 3 July 2009 (UTC)

The djbdns tools support arbitrary record types, so although they were not programmed with IPv6 in mind they handle IPv6 name resolution without patching or upgrading. They do require a patch[1] to their ucspi-tcp component to bind to and serve requests on an IPv6 interface, however in a dual stack environment it is not necessary to have a DNS server bound to an IPv6 interface.

djbdns tools do not need patching to resolve IPv6 addresses, but they will need patching to bind to and serve those requests on an IPv6-only interface. A patch is also available to make record management simpler and analogous to its IPv4 management as opposed to using generic record formats with octal-formatted IPv6 addressing. An existing IPv4 infrastructure running djbdns may deploy IPv6 without having to patch the DNS system. If AXFR transfer is used to tranfer IPv6 addressing to other name servers then the target server must support AAAA records or arbitrary record types. (BIND notably does not support arbitrary record types, so a BIND version supporting IPv6 would be required as an AXFR target.)

* ucspi-tcp