Re: IPv6 readiness and tinydns.
Colm MacCárthaigh <[email protected]> Tue, 2 Nov 2010 12:45:23 -0700
| Newsgroups | gmane.network.djbdns |
|---|---|
| Message-ID | <[email protected]> |
--0016367fb1496c571d0494172afb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Even when you do this, without modification TinyDNS does not append AAAA records to the additional section (as per RFC3596 section 3) for MX, NS or SRV targets (although A records suffer from this too for SRV). Another thing to keep in mind if you plan to use stock TinyDNS to serve AAA= A records is that their order will not be randomised in rrsets containing mor= e than one AAAA record. This shouldn't matter - but in practice some resolver= s don't randomise their processing. 2010/11/2 Maciej =C5=BBenczykowski <[email protected]> > Strictly speaking, you don't ever need IPv6 addresses in MX or NS records= . > They don't actually reference any IP, they reference a hostname, with > an optional ip. > This results in a MX/NS record being generated (mapping domain to > hostname), and optionally an A record to map that hostname to an IP. > > As such if you're like me and never pass in an IP in the MX or NS > record, then you're already good to go. > > Basically split your MX/NS records into MX/NS records and A records, > and then add AAAA records. Or even without splitting just add AAAA > records. > > [ie. all you are losing is not particularly useful syntactic sugar] > > On Tue, Nov 2, 2010 at 08:34, Russell Sutherland > <[email protected]> wrote: > > I am attempting to prepare our infrastructure here to be IPv6 ready. > > Part of that is DNS. For several years we have used the fefe.de patch t= o > > serve up AAAA records for several sub-domains. In the documentation it > > states explicitly that: > > > > .... tinydns-edit won't accept IPv6 addresses for NS or MX records y= et > > > > So my short question is, can one use a patched version of tinydns to > fulling > > support an IPv6 environment? > > > > <snip> > > On 2008-01-12 Russ Nelson wrote: > > > > "When Google has an AAAA record, we can talk about adding IPv6 > support." > > > > I think we are ready to start talking: > > > > http://www.google.com/intl/en/ipv6/faq.html > > </snip> > > > > -- > > Russell Sutherand I+TS > > e: [email protected] > > t: +1.416.978.0470 > > f: +1.416.978.6620 > > m: +1.416.803.0080 > > > > > --=20 Colm --0016367fb1496c571d0494172afb Content-Type: text/html; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable <div><br></div><div><br></div>Even when you do this, without modification T= inyDNS does not append AAAA records to the additional section (as per RFC35= 96 section 3) for MX, NS or SRV targets (although A records suffer from thi= s too for SRV).=A0<div> <br></div><div>Another thing to keep in mind if you plan to use stock TinyD= NS to serve AAAA records is that their order will not be randomised in rrse= ts containing more than one AAAA record. This shouldn't matter - but in= practice some resolvers don't randomise their processing.=A0<br> <br><div class=3D"gmail_quote">2010/11/2 Maciej =AFenczykowski <span dir=3D= "ltr"><<a href=3D"mailto:[email protected]">[email protected]<= /a>></span><br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .= 8ex;border-left:1px #ccc solid;padding-left:1ex;"> Strictly speaking, you don't ever need IPv6 addresses in MX or NS recor= ds.<br> They don't actually reference any IP, they reference a hostname, with<b= r> an optional ip.<br> This results in a MX/NS record being generated (mapping domain to<br> hostname), and optionally an A record to map that hostname to an IP.<br> <br> As such if you're like me and never pass in an IP in the MX or NS<br> record, then you're already good to go.<br> <br> Basically split your MX/NS records into MX/NS records and A records,<br> and then add AAAA records. =A0Or even without splitting just add AAAA<br> records.<br> <br> [ie. all you are losing is not particularly useful syntactic sugar]<br> <div><div></div><div class=3D"h5"><br> On Tue, Nov 2, 2010 at 08:34, Russell Sutherland<br> <<a href=3D"mailto:[email protected]">russell.sutherland@ut= oronto.ca</a>> wrote:<br> > I am attempting to prepare our infrastructure here to be IPv6 ready.<b= r> > Part of that is DNS. For several years we have used the <a href=3D"htt= p://fefe.de" target=3D"_blank">fefe.de</a> patch to<br> > serve up AAAA records for several sub-domains. In the documentation it= <br> > states explicitly that:<br> ><br> > =A0 =A0.... tinydns-edit won't accept IPv6 addresses for NS or MX = records yet<br> ><br> > So my short question is, can one use a patched version of tinydns to f= ulling<br> > support an IPv6 environment?<br> ><br> > <snip><br> > On 2008-01-12 Russ Nelson wrote:<br> ><br> > =A0 "When Google has an AAAA record, we can talk about adding IPv= 6 support."<br> ><br> > I think we are ready to start talking:<br> ><br> > =A0 <a href=3D"http://www.google.com/intl/en/ipv6/faq.html" target=3D"= _blank">http://www.google.com/intl/en/ipv6/faq.html</a><br> > </snip><br> ><br> > --<br> > Russell Sutherand =A0I+TS<br> > e: <a href=3D"mailto:[email protected]">russell.sutherlan= [email protected]</a><br> > t: +1.416.978.0470<br> > f: +1.416.978.6620<br> > m: +1.416.803.0080<br> ><br> ><br> </div></div></blockquote></div><br><br clear=3D"all"><br>-- <br>Colm<br> </div> --0016367fb1496c571d0494172afb--