HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
jpf
eventdns
HISTORICAL RECORD2009–2009
jpf / eventdns · Not publicly available

eventdns

Discover this repository through its Hacker News conversations.

2Distinct people
2Mentions
0Explicit recommenders
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

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 6-hour interval2 dated mentions

Observed mentions: 2009-12-22 01:19:03 UTC to 2009-12-28 00:09:46 UTC.

012009-12-22 00:00:00 UTC to 2009-12-22 06:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsDec 22, 00:002009-12-22 06:00:00 UTC to 2009-12-22 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-22 12:00:00 UTC to 2009-12-22 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-22 18:00:00 UTC to 2009-12-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-23 00:00:00 UTC to 2009-12-23 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-23 06:00:00 UTC to 2009-12-23 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-23 12:00:00 UTC to 2009-12-23 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-23 18:00:00 UTC to 2009-12-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-24 00:00:00 UTC to 2009-12-24 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-24 06:00:00 UTC to 2009-12-24 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-24 12:00:00 UTC to 2009-12-24 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-24 18:00:00 UTC to 2009-12-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-25 00:00:00 UTC to 2009-12-25 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsDec 25, 00:002009-12-25 06:00:00 UTC to 2009-12-25 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-25 12:00:00 UTC to 2009-12-25 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-25 18:00:00 UTC to 2009-12-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-26 00:00:00 UTC to 2009-12-26 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-26 06:00:00 UTC to 2009-12-26 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-26 12:00:00 UTC to 2009-12-26 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-26 18:00:00 UTC to 2009-12-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-27 00:00:00 UTC to 2009-12-27 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-27 06:00:00 UTC to 2009-12-27 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-27 12:00:00 UTC to 2009-12-27 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-27 18:00:00 UTC to 2009-12-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2009-12-28 00:00:00 UTC to 2009-12-28 06:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 28, 00:00

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 22, 00:002009-12-22 00:00:00 UTC2009-12-22 06:00:00 UTC110
Dec 22, 06:002009-12-22 06:00:00 UTC2009-12-22 12:00:00 UTC000
Dec 22, 12:002009-12-22 12:00:00 UTC2009-12-22 18:00:00 UTC000
Dec 22, 18:002009-12-22 18:00:00 UTC2009-12-23 00:00:00 UTC000
Dec 23, 00:002009-12-23 00:00:00 UTC2009-12-23 06:00:00 UTC000
Dec 23, 06:002009-12-23 06:00:00 UTC2009-12-23 12:00:00 UTC000
Dec 23, 12:002009-12-23 12:00:00 UTC2009-12-23 18:00:00 UTC000
Dec 23, 18:002009-12-23 18:00:00 UTC2009-12-24 00:00:00 UTC000
Dec 24, 00:002009-12-24 00:00:00 UTC2009-12-24 06:00:00 UTC000
Dec 24, 06:002009-12-24 06:00:00 UTC2009-12-24 12:00:00 UTC000
Dec 24, 12:002009-12-24 12:00:00 UTC2009-12-24 18:00:00 UTC000
Dec 24, 18:002009-12-24 18:00:00 UTC2009-12-25 00:00:00 UTC000
Dec 25, 00:002009-12-25 00:00:00 UTC2009-12-25 06:00:00 UTC000
Dec 25, 06:002009-12-25 06:00:00 UTC2009-12-25 12:00:00 UTC000
Dec 25, 12:002009-12-25 12:00:00 UTC2009-12-25 18:00:00 UTC000
Dec 25, 18:002009-12-25 18:00:00 UTC2009-12-26 00:00:00 UTC000
Dec 26, 00:002009-12-26 00:00:00 UTC2009-12-26 06:00:00 UTC000
Dec 26, 06:002009-12-26 06:00:00 UTC2009-12-26 12:00:00 UTC000
Dec 26, 12:002009-12-26 12:00:00 UTC2009-12-26 18:00:00 UTC000
Dec 26, 18:002009-12-26 18:00:00 UTC2009-12-27 00:00:00 UTC000
Dec 27, 00:002009-12-27 00:00:00 UTC2009-12-27 06:00:00 UTC000
Dec 27, 06:002009-12-27 06:00:00 UTC2009-12-27 12:00:00 UTC000
Dec 27, 12:002009-12-27 12:00:00 UTC2009-12-27 18:00:00 UTC000
Dec 27, 18:002009-12-27 18:00:00 UTC2009-12-28 00:00:00 UTC000
Dec 28, 00:002009-12-28 00:00:00 UTC2009-12-28 06:00:00 UTC101

What Hacker News says

2 sources
I would love a simple way to manage my DNS entries, like a version controlled text file :) I presently use a free service (http://gratisdns.dk) and also run bind9 for one domain (the free service can act as my backup NS) — I looked at http://cr.yp.to/djbdns.html in my quest for something simpler, but I wasn’t swayed. Your comment made me optimistic, but correct me if I am wrong, but dig.jsondns.org is completely unrelated to any of this — what I would need is http://github.com/jpf/eventdns and dig.jsondns.org is more of a test server for EventDNS if I am not mistaken?
In Query DNS via a RESTful HTTP interface
dnsworks·Dec 22, 2009Submission

DNSworks is looking for a technical cofounder.

Greetings! We're DNSworks, and we're working on solving operations problems. DNS is the first peg in a large board. We're looking for a technical-cofounder to join our team. SOMA is our home, but we believe if someone is a good fit, they can be located anywhere within the same timezone. What we'll offer - A significant equity stake - Caffeine, lots of it - An opportunity to make an impact on operations groups - Some compensation What you bring to the table - A solid work ethic - A "Do No Harm" attitude - Expertise in Ruby & Ruby On Rails - Love of understanding how things work - You're not afraid of re-implementing protocols from RFCs - You have a very strong understanding of TCP/IP Here are some links to projects & papers that are really exciting to us. http://github.com/jpf/domdori | http://github.com/jpf/
Read the rest
eventdns | http://tinydns.org/ | http://bind-dlz.sourceforge.net/ | http://en.wikipedia.org/wiki/Anycast | http://www.pch.net/technology/anycast.php | http://www.sanog.org/resources/sanog5-woody-anycast-v10.pdf | http://www.ietf.org/rfc/rfc3258.txt | http://www.quagga.net/ | http://www.bgp4.as/ We're not just a web start-up, we're building real infrastructure, the kind of fun technologies that keep enterprises afloat. If this excites you, then send a tweet to @dnsworks and let's get some coffee!
17 points · Open discussion

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.