Hi,
Is the inclusion of NAT64 and DNS64 support in the Roadmap for RouterOS v5?
I think this would be a great help for ISPs wishing to do a rapid deployment of pure IPv6 without breaking access to IPv4 resources.
dns in RouterOS supports IPv6 address resolving, if you set IPv6 addresses
IPv6 does not have NAT as it is in IPv4
NAT64? you mean, kind of 4-to-6 tunnel, so that IPv4 users can access IPv6 resources?..
if yes - then joining the question, although I’m not familiar with ipv6 yet… =)
NAT64 is for scenarioes where you do not allocate a v4 address to the customer, and instead use a gateway to fetch v4 resources on the internet that is then translated back into v6.
The two are different. 6to4 tunnels the original packet, NAT64 is AFT (address family translation).
NAT64 is a method of giving IPv6 only clients access to IPv4 resources.
http://tools.ietf.org/html/draft-bagnulo-behave-nat64-00
There are a few opensource implementations of this, and I’ve tested http://ecdysis.viagenie.ca/ on a linux gateway, and it works fine.
Its only really useful with DNS64, which is an A record to AAAA “translator” for DNS queries from IPv6 clients.
well, there should be no problem with RouterOS resolving AAAA records.
Yes, I know that RouterOS works with IPv6 accessing IPv6 resources, and IPv4 accessing IPv4 resources, and dual-stack.
But DNS64 is a helper for NAT64.
NAT64 essentially takes IPv6 requests for IPv4 resources, and maps the IPv4 resources into IPv6 space. Then DNS64 assists in this process by taking A records, and coverting them to AAAA responses in the “mapped” IPv6 space.
This allows Pure IPv6 clients access to IPv4 resources.
Sorry to inform, but apparently there are issues with RouterOS resolving AAAA records:
http://forum.mikrotik.com/t/ping-invalid-value-for-argument-address/37935/7
we are need it NAT64 ,
http://blog.go6.net/?p=210
waiting for NAT64 on Mikrotik
NAT64 and DNS64 is something thats going to be needed on a large scale when the last v4 ranges are handed out, Currently the only applications floating around are not production ready.
We do really need a way of running pure v6 inside our entire network and only touching v4 on the edge for net connection, RIR’s are tightening up their policies on handing out v4 whilst handing out v6 space like its candy. Today if we had to deploy a pure v6 network we couldnt, Basic things like v6 PPPoE are only just coming into a BETA release that wont be stable for a while, We would have to use v4 space and 6to4 tunnels to provide v6 connections which ties up v4 space
NAT64 is in use via Cisco with T-Mobiles mobile v6 trials and is fast becoming the primary transition method, MT’s going to have to polish it’s v6 stack quite a bit and perhaps even backport some of the critical v6 features like v6 PPPoE and Dhcp6 back to 4.x
mikrotik team , when your ROS support NAT64 ???
Were you seriously expecting a road map in two days over a weekend? Shouting the same thing over and over isn’t going to achieve anything.
hha haa haa 
i know that …
Well, since I do think that eventually we will completely run out of IPv4 Resources and will have to go IPv6 only,
any means to let IPv6-only users access the rest of the internet would be very much appreciated 
so yes, please implement NAT64 and DNS64
+1 for NAT64 support!
go go go … NAT64
NAT64 YES!!! A full native IPv6 network accessing IPv4 resources via NAT64 on Mikrotik ROS is all we need nowdays!!!