Most of the time, the behavior you observe is not the behavior of the nameserver, but of the couple {nameserver, stupid middebox in front of it}. That's why we see strange brokenness while all the nameserver software is free and good.
-
-
-
How common is it? Do you have any figures? Or do you know of servers serving popular zones exhibiting this behavior?
- 4 more replies
New conversation -
-
-
Yes exactly. Since even Akamai does respond, that has to be pretty rare.
-
When Route 53 launched, we blackholed queries like this and didn't respond. The reason was intentional: if there were ever a disastrous misconfiguration that meant the servers were "missing" zones that they should have, we wanted to avoid poisoning resolvers.
- 1 more reply
New conversation -
-
-
tinydns still seems to behave like that (at least it does for yp[.]to). Crap.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
#DNS fun of the evening: ask the http://live.com nameservers about anynameyouwant.something#MicrosoftControlsTheRoot -
Yikes.
End of conversation
New conversation -
-
-
@PowerDNS_Bert will be heartbroken!Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Yes, but the SOA is fun.
-
MS DNS servers didn‘t change over the years, it seems.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.