Detecting resolvers at .nz
This is a follow-up post to summarise the work of resolver detection presented at DNS-OARC 29. We built a classifier that can tell, with certain probability, »
Within the Technical Research team, we have developed many data workflows in a variety of projects. These workflows normally need to run on a schedule, contain »
This is a follow-up post to summarise the work of resolver detection presented at DNS-OARC 29. We built a classifier that can tell, with certain probability, »
As the DNS operator of .nz, we manage 4 of the 7 .nz nameservers ourselves and we've been collecting their DNS traffic. The other 3 are »
My previous post "Source Address Classification - Feature Engineering" introduced the background of the source address classification problem and a critical part of the »
Problem background As we operate the authoritative name servers for the .nz ccTLD (Country Code Top Level Domain), we observe more than 500k unique source addresses »
As we run the .nz ccTLD (Country Code Top Level Domain) authoritative nameservers, we receive lots of DNS queries and answer each query with a DNS »
The Domain Name System is a distributed database with a hierarchical structure. A complete DNS resolution is a time-consuming process composed of iterations of network communications »
As part of our role as .nz registry, we manage 4 out of 7 of the .nz authoritative name servers. We receive hundreds of millions of »