Matthew Wilder and the IPv6 DNS route missed in testing

Matthew Wilder Had an AAAA Answer. The IPv6 Road to DNS Was Missing.

Why it matters

TELUS's employee trial caught the sort of network error that looks healthy on a checklist: DNS could answer in IPv6's language, while the route to reach it had yet to be turned on.

Sofia Ren25 October 2026Reading Time 2 minLast update: 25 October 2026

Matthew Wilder, pictured against an imagined test rack; identity grounded in ARIN’s named election photograph.

Summary

In a 2019 account published by ARIN, Matthew Wilder described TELUS testing IPv6 first in the lab and then with employees who volunteered their own services before a broader launch.
The friendly trial found a very specific gap: DNS had been set up to return AAAA records, but connectivity to the DNS routes over IPv6 had not been enabled.

A DNS server can know an IPv6 address and still be unreachable over IPv6. That was the small, maddening distinction Matthew Wilder described in his first-person account of TELUS's rollout. The team had enabled DNS to reply with AAAA records. Test sites then exposed the other half of the job: the IPv6 route to DNS was missing. The answer was dressed for the party; the road to the party had not opened.

Wilder was writing about an operator with many moving parts. TELUS had begun residential IPv6 service in 2015 and was adding wireless service gradually. The plan started with prefix sizes for different customers: /56 for home, /48 for business and /64 for mobile. The carrier also sought to enlarge its ARIN allocation from /32 to /29 so addresses could be organized around geography and routing needs. Those were the figures Wilder gave in 2019.

The build travelled outward. Peering and transit needed IPv6, then the core and edge, then shared services such as DNS, then the separate designs for fixed and mobile products. Wilder described classroom and self-directed training for people beyond the network engineers, including operations and support staff. A rollout may be announced from a boardroom, but a support desk has to explain the odd Tuesday when one service behaves differently from another.

The employee trial sat between the lab and a mass release. Participants opted in, used their own services and checked details including MTU and DNS. It caught a route that the configuration inventory alone could have missed. In Wilder's telling, that was the point of starting small: a real path was tried before the same assumption reached every subscriber. The useful test tried the route to the box itself.