@harald @chrysn
They only miss a CLAT, and need a DNS64 server.

#chromeos #dns64 #ipv6mostly

One of the annoyances with #NAT64 is that when some site publishes an #IPv6 AAAA record, but their IPv6 server is down and the IPv4 server is up, there's no "happy eyeballs" fallback to IPv4. Because the AAAA record exists, #DNS64 doesn't provide a mapping to IPv4.

It can be worked around by manually adding an /etc/hosts entry for the broken site.

Today's broken site is www.fsf.org. Hey @fsf - your IPv6 server is refusing connections 😉

@quad9dns Is there a chance to provide a DNS64 resolver service? Currently, the only big ones are Google and Cloudflare. Neither are palatable. #DNS64
Great, the website of the airport of Zürich doesn't work on #ipv6 even though www.flughafen-zuerich.ch resolves to an ipv6 address (via a couple of CNAMEs). That's the worst type of #ipv6 fail, because it also breaks #dns64 and #nat64 on my ipv6 only network.

Installed our new router box yesterday and switched our LAN from dual-stack to #IPv6 only with #DNS64 + #NAT64

Did quite a lot of this one-handed, as Alonso fell asleep on my arm. 🐶💤

Redesigning my home network. How can I tell #unbound to only do #dns64 for some source IPs (like access-control or a view)?

I got asked if I could create a #howto for creating a (public) #NAT64 service - just like I did recently for #BoxyBSD. With #DNS64 and #NAT64 you can also reach resource in the legacy internet (#IPv4) on #IPv6 only systems.

While this is based on #unbound and #tayga, there’s also a solution by using the #OpenBSD's native way which is also running on the other gateway. I’ll share a second how to how to do this in OpenBSD and pf.

https://gyptazy.com/howto-create-a-public-dns64-nat64-gateway/

HowTo: Create a (public) DNS64 & NAT64 Gateway • gyptazy.com - The DevOps geek

As part of my BoxyBSD project, which is designed to operate on IPv6 only network connectivity, I recently implemented and provided DNS64 and NAT64 gateway support to bridge the gap between IPv6 and the legacy IPv4 world. This solution ensures that users can easily access important resources, like GitHub, which - even in 2025 -

gyptazy.com - The DevOps geek • DevOps, coding, cloud and open source in a geeky way.

@mfierst @alexhaydock @nixCraft

Oh absolutly.
You do the dns64 nat64 setup once per datacenter.
The dual stack you have to do on each and every subnet. And with each there is uniqe firewall policies for that customer. Routing, possible vpn setups. Dns records are special since your internal network is rfc1918 dualstack you get dns views again.
When doing a greenfield network, the only thing you have to do to get ipv4 outgoing for a #ipv6 network is to use the #dns64 nameserver address!

No NAT November: My Month Without IPv4

Link📌 Summary: 本文探討了作者在11月的「無NAT十一月」挑戰中,關閉IPv4並僅使用IPv6的經歷。雖然在這段期間發現了許多挑戰和問題,特別是對於一些設備和應用程式的支持不佳,但作者認可轉向「IPv6-大多數」的概念,這樣可以同時利用IPv6和必要時仍然允許IPv4的路徑。最終,雖然作者的經驗顯示完全關閉IPv4還不成熟,但提議在未來的網路部署中考慮「IPv6-大多數」的方式,這將有助於平滑過渡。

🎯 Key Points:
- 作者接受了「無NAT十一月」的挑戰,評估僅依賴IPv6的可行性。
- 關閉IPv4時遇到許多技術問題,包括桌面操作系統與移動設備的支持情況。
- 一些嵌入式設備如Nintendo Switch未能在IPv6-only環境下正常工作。
- 討論了NAT64和DNS64等過渡技術,這些技術能幫助處理僅支持IPv4的服務。
- 最終建議推行「IPv6-大多數」的策略,以便在未來完全可行的情況下逐步淘汰IPv4。

🔖 Keywords: #IPv6 #NAT64 #DNS64 #無NAT #網路轉型

https://blog.infected.systems/posts/2024-12-01-no-nat-november/

This blog contains some interesting tidbits. Time permitting I'll definitely have a look at maybe going ipv6-mostly.

Why? Because learning ;)

#ipv6 #nat64 #dns64

No NAT November: My Month Without IPv4