January 16, 2017 posted by Taylor R Campbell
[Update, 2017-01-16 20:48 UTC: All issues have been resolved and
NetBSD.org should be functioning normally now.]
As some of you may have noticed, the netbsd.org DNS records are broken
Two independent incidents caused this to happen:
UC Berkeley stopped providing secondary DNS service for netbsd.org
at adns1.berkeley.edu and adns2.berkeley.edu on a few hours
notice, before we had time to update the NS delegations in the
[Update, 2017-01-16 20:48 UTC: The Berkeley network
administrators have graciously restored service until we can
update our NS delegations. Thanks, Berkeley—for doing this
on a US holiday, no less!]
The network hosting our primary nameserver ns.netbsd.de went offline
at around 14:00 UTC for reasons unknown.
[Update, 2017-01-16 20:48 UTC: The network and ns.netbsd.de are
We have sent a request to our registrar to update the delegations to
make ns.netbsd.org primary and ns.netbsd.de secondary.
We asked them to expedite the process, but owing to the weekend, when
the humans who process these requests are off work, it may take
another day for that to take effect, and another day after that for
the cached TTLs on the old NS delegations to Berkeley's nameservers
As a provisional stop gap, if you need access to the netbsd.org zone
and you can prime your DNS cache with manually entered records, you
can prime it with the following records to restore service at your
netbsd.org. 86400 IN NS ns.netbsd.org.
netbsd.org. 86400 IN NS ns.netbsd.de.
ns.netbsd.org. 86400 IN A 220.127.116.11
ns.netbsd.org. 86400 IN AAAA 2001:470:a085:999::53
(Presumably if you are reading this you have some DNS records in the
netbsd.org zone cached, but they will eventually expire and you may
need some others.)