@tschaefer RFC7050 #DNS64 prefix discovery support is not forseen as this will be deprecated in the near future.

Extending the Vector Packet Processing Engine

I've been building core networking components to leverage VPP more fully as a branch router. Here is an overview of that work.

https://enigmatick.social/objects?uuid=b5cfe32e-e1ba-40da-80a1-e6f5bcfb6149

Enigmatick

An diesem langen Wochenende habe ich mal wieder mir Zeit genommen, um etwas an meinem Heimnetz herumzuspielen und den #RaspberryPi mal wieder anzuwerfen. #IPv6mostly war diesmal mein Testgebiet. Mit CoreDNS, Tayga und KEA DHCP-Server hat das ganze dann irgendwann doch recht gut funktioniert. Ich war ΓΌberrascht wie stark an einem die KI (hier Gemini) weiterhelfen und ein Tutorial fΓΌr ein doch spezielles Thema erstellen konnte. Nach etwas gebastel hat es dann doch funktioniert. #DNS64 #NAT64

@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.