for my dual stack nameserver to be reachable from all networks I need to configure one DNAT rule for every subnet I run, including WAN (currently seven).

For #IPv6 I only need ONE rule because I don't have to masquerade.
So who again said IPv6 has no advantages over #lPv4

The same way #cznic has set a end date for #lPv4 I think we need a global end date so we can finally mark IPv6 migration to Done .
https://konecipv4.cz/en/
#IPv6
Homepage - Konec IPv4

Having #dualstack #lPv4 and #IPv6 seems cumbersome most of the time.
Sometimes though it comes in very hand when you would disconnect yourself by chaning network configuration.
In that case you can just switch v4 while you're connecting via v6 without loosing connectivity.

One of the lesser known truths of #IPv6. It can actually be much easier to memorize the numbers than #lPv4 .
Opposed to wrinting 10.10.129.1/24 into your documentation it suffices to write

2000::1/64

as your static prefix is already well known to you.
I actually don't feel sorry for people that cannot remember their very own prefix like:

2a00:12d:4f::/48

as I don't think those people belong in information technology.
And then there's #DNS

Surveillance cameras or #IPcameras often lack #IPv6 support.
The only devices that I know of that are being advertised as v6 ready are those from #hikvision. I bought a cheaper one from the HWC series that actually is also #lPv4 only but the more expensive ones seem to have v6 support. I would love to get my hands on them. #frigate #homeassistant
A good indicator for not having setup a legacy IP default gateway is when your #Ansible playbook cannot retrieve from #github. #IPv6 #lPv4
#IPv6 #ULA isn't a bad idea. Since providers hardly ship static prefixes I even believe that it should be deployed in mostly every network. It may coexist to static or dynamic prefixes.
It makes you independent of what IP addresses you get from your provider. You can route between sites.
When I listened to this talk for me it felt like there is no real use case for it, but it is. Stop using A records whatsoever. #lPv4 is dead.
https://packetpushers.net/podcast/ipv6-buzz-107-ipv6-unique-local-addresses-at-ietf-114/
IPv6 Buzz 107: IPv6 Unique Local Addresses (ULA) At IETF 114 - Packet Pushers

In this IPv6 Buzz podcast episode Ed, Scott, and Tom--with tongues firmly in cheek---discuss some of the ways to avoid or put off IPv6 adoption until you can retire.

Why is #nocsocial #lPv4 only anyway? #IPv6
After tinkering around with #IPv6 on mikrotik I need to mention:
- no traceroute for v6
- remote syslog is #lPv4 only
- an interface with an /64 address in default will advertise the prefix
- ntp client also seems to be v4 only, at least a 2. pool only gets v4 addresses