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

​Services Changes

Following a critical PHP security advisory affecting installations worldwide, we temporarily restricted public access to some of our backend services while carrying out necessary upgrades. Access has now been restored, and the affected services are operating normally. The Vodia PBX itself does not use PHP and was not directly affected. We explain what happened, the changes to legacy licensing and TLS support, and why customers running older PBX versions should contact us for upgrade guidance.

October 22, 2026
Announcement

How to submit a support ticket in the Vodia Help Center

Submitting a support ticket with the right information helps our team understand your issue and reduces follow-up questions. This step-by-step guide walks you through the Vodia Help Center, from describing the problem and attaching diagnostic files to setting the business impact and providing your PBX details. You’ll also learn which call details and timestamps to include, alongside practical tips to keep troubleshooting focused and help our support team investigate your issue more efficiently.

October 21, 2026
Announcement

Make the Switch: The Vodia PBX Migration Tool

Switching phone systems doesn’t have to mean rebuilding everything from scratch. The Vodia PBX migration tool imports key configuration data from backups, including extensions, ring groups, queues, desk phones, and basic auto-attendant settings. Built into the Vodia Admin Portal, it guides administrators through the import process and reduces repetitive manual work, whether you’re moving 10 extensions or 1,000. Explore what transfers, what needs manual setup, and how the built-in tool reduces repetitive work when moving to Vodia.

October 15, 2026