It reminded me of this clever hack used to store the source code of DeCSS (CSS descrambler that let you bypass the DVD DRM) in DNS records: http://decss.zoy.org/ (method 9).
"Mark Baker noticed that you could do the request to any nameserver. Which means for instance that the DeCSS source code is available from the DVDCCA's nameservers !"
Wish they would open source it. I would have preferred if they would have contributed to PowerDNS instead of reinventing the wheel.
Was PowerDNS so awful it required a compete rewrite if so fair enough.
I'm not sure about "rebooting" -- if this was just a language error -- but PowerDNS can run with a MySQL or Postgres backend with instant updates to records. i.e., no reload or other configuration re-read required.
With DB replication up and running, you can get a fairly robust domain name server pool going without the usual headaches associated with copying updates to multiple servers.
While playing these kinds of games on security sensitive services might not seem like a good idea, it lets someone take ownership of its development, and gain experience with its codebase.
I imagine the switch over to TCP is more because the response is likely to be larger than a UDP packet (which IIRC is why DNS-over-TCP exists) (looks to be the case [1]), as opposed to stopping an amplified reflection attack, but it's a nice side effect.
Nope. Normal DNS behaviour is to send the first few records over UDP and set the response truncated flag, which would still allow amplified reflection. They're intentionally sending no records at all in order to protect against this.
I remember listening to a podcast where Steve Gibson mentioned that he uses a DNS TXT record to publish the current version of SpinRite. That way the program just does a DNS look-up to see if there is a newer version available.
Thought that was a clever trick. Saves a centralised server getting hit all the time (although you then miss out of usage information I guess.)
[+] [-] simias|12 years ago|reply
"Mark Baker noticed that you could do the request to any nameserver. Which means for instance that the DeCSS source code is available from the DVDCCA's nameservers !"
Classic.
[+] [-] Fuxy|12 years ago|reply
[+] [-] jgrahamc|12 years ago|reply
"We're planning on open sourcing RRDNS, the authoritative DNS server we built, when it gets to a state where it could be used by others."
[+] [-] chrisdew|12 years ago|reply
[+] [-] jackalope|12 years ago|reply
Can someone explain? What DNS server requires a reboot (or even restart) instead of a simple reload?
[+] [-] thaumaturgy|12 years ago|reply
I'm not sure about "rebooting" -- if this was just a language error -- but PowerDNS can run with a MySQL or Postgres backend with instant updates to records. i.e., no reload or other configuration re-read required.
With DB replication up and running, you can get a fairly robust domain name server pool going without the usual headaches associated with copying updates to multiple servers.
[+] [-] ck2|12 years ago|reply
Don't really need the other stuff but from what I can see their dns performance is on par with dnsmadeeasy/dyn/ultra
[+] [-] gwu78|12 years ago|reply
[+] [-] pjbringer|12 years ago|reply
[+] [-] kevinbowman|12 years ago|reply
[1] http://serverfault.com/questions/404840/when-do-dns-queries-...
[+] [-] makomk|12 years ago|reply
[+] [-] anotherevan|12 years ago|reply
Thought that was a clever trick. Saves a centralised server getting hit all the time (although you then miss out of usage information I guess.)
[+] [-] 9ac345a5509a|12 years ago|reply
[+] [-] chris_wot|12 years ago|reply
[+] [-] hexedpackets|12 years ago|reply
After all, what's the point of running a massive service if you can't have fun with it?
[+] [-] gwu78|12 years ago|reply
1. Browsers were/are a prime location for Easter eggs.
[+] [-] hypnotist|12 years ago|reply
[+] [-] zx2c4|12 years ago|reply
http://www.nlnetlabs.nl/projects/nsd/