HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
robertdavidgraham
robdns
C2014–2015
robertdavidgraham / robdns

robdns

A fast DNS server based on C10M principles

3Distinct people
3Mentions
0Explicit recommenders
609GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A fast DNS server based on C10M principles

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week3 dated mentions

Observed mentions: 2014-12-27 13:01:28 UTC to 2015-06-16 20:52:03 UTC. Weeks start Monday, UTC.

0122014-12-22 00:00:00 UTC to 2014-12-29 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsDec 222014-12-29 00:00:00 UTC to 2015-01-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-05 00:00:00 UTC to 2015-01-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-12 00:00:00 UTC to 2015-01-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-19 00:00:00 UTC to 2015-01-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-01-26 00:00:00 UTC to 2015-02-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-02 00:00:00 UTC to 2015-02-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-09 00:00:00 UTC to 2015-02-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-16 00:00:00 UTC to 2015-02-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-02-23 00:00:00 UTC to 2015-03-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-03-02 00:00:00 UTC to 2015-03-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-03-09 00:00:00 UTC to 2015-03-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-03-16 00:00:00 UTC to 2015-03-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 162015-03-23 00:00:00 UTC to 2015-03-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-03-30 00:00:00 UTC to 2015-04-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-04-06 00:00:00 UTC to 2015-04-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-04-13 00:00:00 UTC to 2015-04-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-04-20 00:00:00 UTC to 2015-04-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-04-27 00:00:00 UTC to 2015-05-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-05-04 00:00:00 UTC to 2015-05-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-05-11 00:00:00 UTC to 2015-05-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-05-18 00:00:00 UTC to 2015-05-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-05-25 00:00:00 UTC to 2015-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-01 00:00:00 UTC to 2015-06-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-08 00:00:00 UTC to 2015-06-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-06-15 00:00:00 UTC to 2015-06-22 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 15

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Dec 222014-12-22 00:00:00 UTC2014-12-29 00:00:00 UTC211
Dec 292014-12-29 00:00:00 UTC2015-01-05 00:00:00 UTC000
Jan 52015-01-05 00:00:00 UTC2015-01-12 00:00:00 UTC000
Jan 122015-01-12 00:00:00 UTC2015-01-19 00:00:00 UTC000
Jan 192015-01-19 00:00:00 UTC2015-01-26 00:00:00 UTC000
Jan 262015-01-26 00:00:00 UTC2015-02-02 00:00:00 UTC000
Feb 22015-02-02 00:00:00 UTC2015-02-09 00:00:00 UTC000
Feb 92015-02-09 00:00:00 UTC2015-02-16 00:00:00 UTC000
Feb 162015-02-16 00:00:00 UTC2015-02-23 00:00:00 UTC000
Feb 232015-02-23 00:00:00 UTC2015-03-02 00:00:00 UTC000
Mar 22015-03-02 00:00:00 UTC2015-03-09 00:00:00 UTC000
Mar 92015-03-09 00:00:00 UTC2015-03-16 00:00:00 UTC000
Mar 162015-03-16 00:00:00 UTC2015-03-23 00:00:00 UTC000
Mar 232015-03-23 00:00:00 UTC2015-03-30 00:00:00 UTC000
Mar 302015-03-30 00:00:00 UTC2015-04-06 00:00:00 UTC000
Apr 62015-04-06 00:00:00 UTC2015-04-13 00:00:00 UTC000
Apr 132015-04-13 00:00:00 UTC2015-04-20 00:00:00 UTC000
Apr 202015-04-20 00:00:00 UTC2015-04-27 00:00:00 UTC000
Apr 272015-04-27 00:00:00 UTC2015-05-04 00:00:00 UTC000
May 42015-05-04 00:00:00 UTC2015-05-11 00:00:00 UTC000
May 112015-05-11 00:00:00 UTC2015-05-18 00:00:00 UTC000
May 182015-05-18 00:00:00 UTC2015-05-25 00:00:00 UTC000
May 252015-05-25 00:00:00 UTC2015-06-01 00:00:00 UTC000
Jun 12015-06-01 00:00:00 UTC2015-06-08 00:00:00 UTC000
Jun 82015-06-08 00:00:00 UTC2015-06-15 00:00:00 UTC000
Jun 152015-06-15 00:00:00 UTC2015-06-22 00:00:00 UTC101

What Hacker News says

3 sources
Nice, except recvmmsg() is broken. http://man7.org/linux/man-pages/man2/recvmmsg.2.html The timeout argument does not work as intended. The timeout is checked only after the receipt of each datagram, so that if up to vlen-1 datagrams are received before the timeout expires, but then no further datagrams are received, the call will block forever. Which makes it useless for any application that wants to service data in a short time frame. The only way around it is to use a "self clocking" method. If you want to receive packets at least every 10ms, set a 10ms timeout... and then be sure to send yourself a packet every 10ms. I've done similar tests with UDP applications. It's possible to get 500K pps on a multi-core system with a test application that isn't too complex, or uses too many tricks. The problem is that the sy
Read the rest
stem spends 80% to 90% of its time in the kernel doing IO. So you have no time left to run your application. Another alternative is pcap and PF_RING, as seen here: https://github.com/robertdavidgraham/robdns That might be useful. Previous discussion on robdns: https://news.ycombinator.com/item?id=8802425
In How to receive a million packets per second
Few nitpicks found while skimming through the source. fd = socket(AF_INET6, SOCK_DGRAM, 0); if (fd <= 0) { This should be fd == -1. fd == 0 is valid. https://github.com/robertdavidgraham/robdns/blob/master/src/... https://github.com/robertdavidgraham/robdns/blob/master/src/... check errors from sendto() & recvfrom(). you don't want to loop infinitely when fd is hosed. https://github.com/robertdavidgraham/robdns/blob/master/src/... Check return value of your mallocs. https://github.com/robertdavidgraham/robdns/blob/master/src/... Check return value of fd.
In Robdns – A fast DNS server based on C10M principles

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.