Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Thank you!

The DNS flag day 2019 was very successful event and the Internet community worked together and fixed problems which were causing delays and other problems for Internet users worldwide. We would like to thank to all operators who cooperated and helped to make Internet a better place.

Summary of the past and future DNS flag days can be found e.g. in

What's next?

Next round of DNS flag day is being planned right now, with focus on operational and security problems in DNS caused by Internet Protocol fragmentation.

Please subscribe to mailing list dns-announce or follow dnsflagday Twitter to receive notification when more information becomes available.

DNS Flag Day 2020

The DNS community has been discussing persistent interoperability and performance issues with the DNS system on industry mailing lists and at conferences such as DNS-OARC 30 panel discussion (video, slides).

The proposed plan for the DNS flag day 2020 was announced at RIPE78 by Petr Špaček, CZ.NIC and Ondřej Surý, ISC (video, slides). This time, we will focus on the problems with IP fragmentation of DNS packets.

Please see for more information.

Who's behind DNS flag day?

The DNS flag day effort is community driven by DNS software and service providers, and supported by The DNS Operations, Analysis, and Research Center (DNS-OARC) which most in the community are members of.

If you have technical questions around DNS flag day you can join the DNS-operations mailing list and ask them there.

Get in touch

For press & media inquiries please use media (at) and please put “DNS Flag Day" in the email subject line.

Want to build this locally?

In Gemfile, put:

source ''
gem 'github-pages', group: :jekyll_plugins

Then, to build (and keep building after every edit, run:

docker run --rm -v "$PWD:/srv/jekyll" -v "$PWD/vendor/bundle:/usr/local/bundle" -it jekyll/jekyll jekyll build --watch

Then, in _site/, run:

python3 -mhttp.server