DNS64 “works” if you ignore what it breaks. MAP-T does NAT46 to the NAT64 and doesn’t have the side effects of DNS64. Why people insist that DNS64 is a “good" way to direct traffic to the NAT 64 I don’t understand. MAP-T directs the traffic to the NAT64 without the side effects. DNS64 was only ever a stop gap mechanism with lots of know side effects. Mark
On 21 Dec 2017, at 10:01 am, Ca By <cb.list6@gmail.com> wrote:
On Wed, Dec 20, 2017 at 5:54 PM Mark Andrews <marka@isc.org> wrote: As someone who has written a DNS64 implementation - DO NOT USE DNS64. DNS64 breaks stuff.
Use MAP-T. For those of you using DNS64 on the cellar side MAP-T can use the NAT64 you already have.
Mark
That’s just your opinion, man. Works for me and my 70 million customers.
Anything that is broken by DNS64 can be properly fixed by eliminating the need for it — by deploying ipv6. DNS64 only appears when the far end resource is single stacked (!)
We won’t be held hostage by folks who refuse to deploy ipv6, those days are over
Happy holidays!
On 21 Dec 2017, at 9:33 am, Jens Link <lists@quux.de> wrote:
Ca By <cb.list6@gmail.com> writes:
Free open source nat64
And the DNS64 part can be done with powerdns (recursor), unbound, bind, ... All OpenSource
Jens -- ---------------------------------------------------------------------------- | Foelderichstr. 40 | 13595 Berlin, Germany | +49-151-18721264 | | http://blog.quux.de | jabber: jenslink@quux.de | --------------- | ----------------------------------------------------------------------------
-- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org
-- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org