Back to Blog
Editorial

IPv6 and Why Email Didn't Work Anymore

Published on:

February 22, 2013

snom ONE has supported IPv6 since the early days of PBXnsip, and while we're still waiting for service providers to fully embrace IPv6, there are more practical issues to address. One of the challenges is the handling of DNS records for IPv4 and IPv6 (A and AAAA). As more services add AAAA records, the problem arises when clients without IPv6 connectivity still receive those records, which leads to connection issues. A recent example was Gmail, where the snom ONE email client stopped working. The solution was to prioritize IPv4 records first, though this workaround isn't a permanent fix, as IPv4 will eventually become obsolete.

Christian Stredicke

So everything we buy these days should be ready for IPv6. Even in the old pbxsnip days, snom ONE supported IPv6. Nothing new here.

While we are all waiting for the happy day when our service providers finally give out publicly routable prefixes so all out phones in the LAN don’t need NAT any more, we need to deal with some more down-to-earth problems. One of the problems is DNS uses records for IPv4 and some others for IPv6 (A and AAAA).

While practically all services in the net offer IPv4 DNS addresses, there are more and more providers who also add AAAA records. The problem is a DNS server operates independently from the underlying internet version. In other words, you get AAAA records even when the DNS server is running on IPv4. The practical problem is a client is running in the LAN without any IPv6 connectivity to the outside world also gets those AAAA records; when it then tries to connect to the service, it eventually times.

That is exactly what happened with Gmail. Google added IPv6 records for the Gmail service some time ago, and suddenly the snom ONE email client didn't work anymore if your PBX didn't have IPv6 connectivity.

The way we fixed the problem is the PBX now looks at the IPv4 records first. I didn't say "solve the problem” because this isn't a proper solution. The day IPv4 will become unavailable to the PBX, this fix won't work anymore. I guess we have a few more years to properly solve that problem. For now we can live with the workaround, and hopefully snom ONE users will not notice anything.

Latest Articles

View All
Announcement

Vodia in 2025: Reflections and What’s Next

Vodia’s 2025 marked a year of pragmatic AI adoption, unprecedented platform robustness, and laying the foundation for the next phase of the PBX. With version 69 reaching exceptional stability, focus has shifted to version 70, which introduces a redesigned admin interface and major architectural improvements in scalability, resilience, and flexibility. Alongside steady expansion of integrations and partner tooling, the roadmap for 2026 emphasizes refined user experiences, modernized apps, and continued investment in reliability over hype.

December 23, 2025
Tech

Should You Upgrade Your Vodia PBX? A Practical Guide

Delaying PBX upgrades may feel safe in the short term, but real-world dependencies like security standards, app compatibility, and vendor APIs eventually force reactive upgrades at the worst possible time. Staying reasonably current with Vodia PBX versions, rather than clinging to outdated releases or jumping on every new preview, helps maintain security, compatibility, and performance while avoiding emergency upgrades, especially as newer features and OS requirements become unavoidable.

December 19, 2025
Announcement

New York City Department of Education Will Move Its Telephony to the Cloud

The New York City Department of Education has issued a Request for Expression of Interest signaling its intent to modernize district-wide communications by moving away from legacy landline PBX systems. Serving 1.1 million students across 1,800 schools, the proposed transition to a cloud-based VoIP platform focuses on resiliency, scalability, multilingual capabilities, hybrid deployment options, and integration with Microsoft Teams for more than 150,000 staff members.

December 16, 2025