DNS server in Go - Big NTP Pool upgrade

This seems like a great time to prod more folks into joining the pool. If you have a static IP and a stable machine please consider becoming part of the pool:<p><a href="http://www.pool.ntp.org/en/join.html" rel="nofollow">http://www.pool.ntp.org/en/join.html</a><p>My firewall at home is part of the pool. You can configure how much traffic you can handle in the manage servers interface. With any decent cable connection you can set the speed to 768Kbit and never notice the traffic (ntp is just tiny udp datagrams).<p>While we are at it lets go through /etc/ntp.conf and remove any references to stratum one servers. With a recent version of ntp you can replace all of your server lines with:<p><pre><code> pool 0.CC.pool.ntp.org iburst pool 1.CC.pool.ntp.org iburst pool 2.CC.pool.ntp.org iburst pool 3.CC.pool.ntp.org iburst </code></pre> Where CC is your country code {us,ca,de,mx,fr,etc}. I decided to err on the side of caution and give an example that will work with any reasonably recent version of ntp. With the most recent stable release the following one line will suffice:<p><pre><code> pool CC.pool.ntp.org iburst </code></pre> That one line will work for Mountain Lion, debian/unstable and the most recent ubuntu release and ntp will automatically poll more servers as needed.<p>More info on using the pool can be found here:<p><a href="http://www.pool.ntp.org/en/use.html" rel="nofollow">http://www.pool.ntp.org/en/use.html</a>

Miek Gieben's [1] DNS library [2] is truly excellent. I use it at Port 6379 for an authoritative DNS server, looking up Redis instances [3]. I too have found Go surprisingly productive and enjoyable to code, and our servers seem very stable so far.<p>[1] <a href="http://www.miek.nl/" rel="nofollow">http://www.miek.nl/</a><p>[2] <a href="https://github.com/miekg/dns" rel="nofollow">https://github.com/miekg/dns</a><p>[3] <a href="https://port6379.com/blog/2012/09/03/using-dns-to-find-instances" rel="nofollow">https://port6379.com/blog/2012/09/03/using-dns-to-find-insta...</a>

&#62; Since mid-September, twenty of the name servers have been running the new software and except for a bit of trouble on i386 (32-bit) and low-memory systems, it's been running very smoothly.<p>So is <a href="http://code.google.com/p/go/issues/detail?id=909" rel="nofollow">http://code.google.com/p/go/issues/detail?id=909</a> a real-world problem?

How can this even exist without generics, template meta-programming or a turing complete type system? I doubt that they know what they're doing.

For people searching for performance benchmarks like me, here are the numbers I dug around from the post ( <a href="http://geo.bitnames.com" rel="nofollow">http://geo.bitnames.com</a>)<p><i>If you need less than 200 DNS lookups per second per DNS server the Perl version is fine and might be a little easier to setup. The Go version is much faster (in prodution we've seen it do 5-6000 requests a second on commodity hardware and even virtual servers). </i><p>Is 6000 rps a high number for a DNS server? Let me do a back of the envelope calculation: one simple dns request (assuming udp here) response msg size is 100bytes, 6000rps x 100bytes /1024/1024 x 8 = 4.69mbps. Even we consider the request msg size is equal to that of response msg, the throughput is still 9.38mbps, far from saturating the network pipe. It sounds to me there is still space for improvement.

I'm in love with Go. The more I use it the more i fall in love with it.

Source code linked by the OP: <a href="https://github.com/abh/geodns/" rel="nofollow">https://github.com/abh/geodns/</a>

pretty neat. hopefully this will get some tractions.<p>thanks for sharing.