HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
socketry
rubydns
Ruby2020–2020
socketry / rubydns

rubydns

A DSL for building fun, high-performance DNS servers.

2Distinct people
2Mentions
0Explicit recommenders
727GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A DSL for building fun, high-performance DNS servers.

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, 1:49:46 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 week2 dated mentions

Observed mentions: 2020-02-12 18:23:51 UTC to 2020-04-08 06:38:28 UTC. Weeks start Monday, UTC.

012020-02-10 00:00:00 UTC to 2020-02-17 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 102020-02-17 00:00:00 UTC to 2020-02-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-02-24 00:00:00 UTC to 2020-03-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-03-02 00:00:00 UTC to 2020-03-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-03-09 00:00:00 UTC to 2020-03-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 92020-03-16 00:00:00 UTC to 2020-03-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-03-23 00:00:00 UTC to 2020-03-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-03-30 00:00:00 UTC to 2020-04-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-04-06 00:00:00 UTC to 2020-04-13 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 6

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
Feb 102020-02-10 00:00:00 UTC2020-02-17 00:00:00 UTC101
Feb 172020-02-17 00:00:00 UTC2020-02-24 00:00:00 UTC000
Feb 242020-02-24 00:00:00 UTC2020-03-02 00:00:00 UTC000
Mar 22020-03-02 00:00:00 UTC2020-03-09 00:00:00 UTC000
Mar 92020-03-09 00:00:00 UTC2020-03-16 00:00:00 UTC000
Mar 162020-03-16 00:00:00 UTC2020-03-23 00:00:00 UTC000
Mar 232020-03-23 00:00:00 UTC2020-03-30 00:00:00 UTC000
Mar 302020-03-30 00:00:00 UTC2020-04-06 00:00:00 UTC000
Apr 62020-04-06 00:00:00 UTC2020-04-13 00:00:00 UTC101

What Hacker News says

2 sources
I haven't looked at DNS in depth in a very very long time. My recollection is that it is a pretty simple protocol. Is that still the case? If it is, I wonder if it would be reasonable to build a small stand-alone DNS server specifically to use with Let's Encrypt for this. You run this on your own server, and it only handles the domains that you need to satisfy Let's Encrypt. Point the _acme-challenge record there with a CNAME on your "real" DNS server, and whenever you are getting or renewing a Let's Encrypt certificate, bring up the small stand-alone server. When the certificate issues or is renewed, shut down the small stand-alone server. Some Googling of the form "simple DNS server $LANG" for various programming languages $LANG turns up a few that could provide nice starting points. Perl: on meta::cpan there is Net::DNS::Nameserver, me
Read the rest
ant to provide a local nameserver for testing local client resolvers, but would probably be adaptable. Python: [1] under 50 lines and using no imports other than "socket". It's very minimal, but shows dealing with the protocol. [2] [3] [4] are all using something called "dnslib". [2] is nearly 150 lines, but it is more complicated than we need. It's even using multithreading. Same for [3]. [4] is much similar, and much smaller (comparable to using Net::DNS::Nameserver in Perl). Another library for simple DNS in Python is pydnserver [5]. PHP: I didn't find anything simple. All I found was much more full featured and many more lines of code than we need. Go: [6]. Bash: [7]. I'm not sure what disturbs me more. That someone made this, or that I searched for it. Ruby: [8]. [1] http://code.activestate.com/recipes/491264-mini-fake-dns-ser... [2] https://gist.github.com/andreif/6069838 [3] https://gist.github.com/pklaus/b5a7876d4d2cf7271873 [4] https://stackoverflow.com/questions/33531551/how-to-create-a... [5] https://pypi.org/project/pydnserver/ [6] https://gist.github.com/walm/0d67b4fb2d5daf3edd4fad3e13b162c... [7] https://gist.github.com/CheRuisiBesares/f35f71f028926e65191d... [8] https://github.com/socketry/rubydns
In Let's Encrypt: an automated certificate authority to encrypt the entire web

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.