APNIC Pty Ltd.

09/17/2026 | Press release | Distributed by Public on 09/16/2026 18:03

[Podcast] ‘Just say no’ isn’t as simple as you think


A policeman directs traffic on the corner of Queen and William Street, Brisbane, during very inclement weather, 19 December 1954. Adapted from the original on the Queensland Police website.

In this episode of PING, APNIC Chief Scientist Geoff Huston and I continue a discussion about the repeat queries Geoff sees on the APNIC Labs experiment. Over time, this number has changed, as DNS protocol usage has changed. We now have DNS records that didn't exist when the problem was first seen, and therefore have multiple queries about multiple things.

Geoff has been exploring two aspects of DNS. Firstly, he examines how different ways of answering 'no' affect query volume, as well as the amount of work required by authoritative servers, intermediate resolvers, and clients. The results are sometimes surprising, with different ways of saying no, including not responding at all, leading to very different outcomes.

Secondly, he explores the impact that alternative DNS transport protocols could have on query repetition and overall query load, which may in part be a consequence of User Datagram Protocol (UDP) and its behaviour. Many have argued that the overhead of maintaining connection state for TCP and similar protocols made them unsuitable for DNS at scale. However, as the volume of unnecessary repeated queries continues to grow, it is possible that, end-to-end, maintaining protocol state may actually require less work than repeatedly handling the same queries.

Read more about the problems of saying no on the APNIC Blog:

You can stream and subscribe to PING via the following channels:

If you're interested in sharing your insights or research, please get in touch - we're always looking for great stories from the community. Please let us know what you think of the podcast and the APNIC Blog so we can keep improving.

The views expressed by the authors of this blog are their own and do not necessarily reflect the views of APNIC. Please note a Code of Conduct applies to this blog.

APNIC Pty Ltd. published this content on September 17, 2026, and is solely responsible for the information contained herein. Distributed via Public Technologies (PUBT), unedited and unaltered, on September 17, 2026 at 00:03 UTC. If you believe the information included in the content is inaccurate or outdated and requires editing or removal, please contact us at [email protected]