Community guidelines
Be specific and constructive. No vendor spam — promoting your own product belongs in a listing. Anyone can read; posting needs a free account.
We are opening a small office and somebody suggested making the client VLAN IPv6 only with NAT64 and DNS64. I like the idea of not carrying dual stack forever, but I also do not want to discover that the finance app or a random VPN client only speaks IPv4. Has anyone done this for normal users rather than a lab?
We tried it on a guest and developer network first. Browsing and SaaS were mostly fine. The trouble was software with literal IPv4 addresses, a couple of security agents and one VPN product. NAT64 can't help when an application refuses to ask DNS. I wouldn't make the first test the finance floor.
Dual stack is still less surprising for an office, but IPv6 only is a good way to expose hidden dependencies. Put volunteers on it for a month and log every fallback request. The other gotcha is help desk tooling. Some remote support and discovery tools assume RFC1918 everywhere.
Makes sense. I can get a developer VLAN approved and keep the printers elsewhere. Did you use 464XLAT for apps that wanted an IPv4 socket, or did you just treat those as blockers?
We used 464XLAT on managed mobile devices, not on the desktop network. For laptops we treated hard IPv4 dependencies as a finding and pushed the vendor. That made the pilot useful even though we didn't go fully IPv6 only. Six months later the exception list was much shorter.