KPN introduces broadband and mobile DNSSEC validation
Introduction follows successful Telfort rollout in December
Introduction follows successful Telfort rollout in December
From the start of this month, Dutch telecoms giant KPN has enabled DNSSEC validation for broadband and mobile customers. In other words, the firm's DNS resolvers now check the digital signatures of signed domain names to make sure they are valid and block any invalid DNS referrals. Verification prevents hackers redirecting internet users to fake websites in order to con them out of money, access codes, personal data and other valuable information.
"KPN is already doing a lot in the field of security and privacy," says Product Manager Roeland Mighawry, "but more can still be done in the consumer market." He believes that the company's infrastructure, services and packages all offer opportunities. "We looked at DNSSEC a while back, but decided to wait, because of the complexity of our internal infrastructure. Security awareness has increased considerably since then, however. And government bodies are getting much more involved."
KPN enabled DNSSEC validation at its Telfort subsidiary back in December 2019. "Telfort's infrastructure is very similar to KPN's," continues Mighawry. "But the company has a smaller user base, so we implemented DNSSEC there first."
Fortunately, there was no discernible upturn in users seeking helpdesk support. Validation errors, where validating resolver users can't reach a domain because of a mistake in its DNSSEC configuration, are nowadays unusual. "A while ago, there was a problem with a high-traffic government domain. We dealt with that by disabling validation for that particular domain for a couple of hours. We had to dig around a bit to discover the cause of the issue, but everything was fixed inside two hours." According to Mighawry, the analysis of DNSSEC issues is quite straightforward nowadays. In contrast to most Dutch access providers, KPN's subsidiary XS4ALL, where Mighawry used to work, has been doing DNSSEC validation for some years. "XS4ALL generally caters for a more tech-savvy clientele, so it doesn't usually take long to get to the bottom of the issue on the phone, and then you contact the relevant domain's operator." SIDN also works to minimise validation errors by scanning all the domain names in the .nl zone to check the validity of DNSSEC records on a daily basis. On the back of that policy, the number of validation errors has been negligible for several years. One frustration that Mighawry has come across is that DNSSEC tools sometimes give inconsistent results for a domain name. Internet.nl may report findings that don't tally with DNSViz, while PowerDNS Recursor (used by KPN) says something different again.
Mighawry advises any company looking to roll out DNSSEC to make sure everyone at the front of the organisation understands the technology properly. "If your people don't know their stuff, they're going to get tied up in lengthy conversations with customers. There's plenty of information about DNSSEC on line, but it can be quite dense and you won't find it all in one convenient place." "We've added material about how DNSSEC works and how to recognise DNSSEC-related problems to our knowledge base and processes." So the workflows and phone scripts for KPN's helpdesks are all geared up to resolving issues quickly. "We're also going to make information available to customers on line." Enabling DNSSEC validation dovetails with a general internet upgrade that KPN is implementing soon. The company intends to make another important security and privacy-related announcement later in the year. KPN's decision to embrace validation is an important development within the internet tech community. "It's great news," says Marco Davids, Research Engineer at SIDN Labs. "At a stroke, DNSSEC validation will be enabled for 30 to 40 per cent of internet users in the Netherlands [1, 2]."