ISC Blogs

BIND 10: The First Year

19 Mar 2010
By Shane Kerr

We have nearly reached the end of the first year of the BIND 10 project. To celebrate this, we are releasing the first version of BIND 10.

Perspectives on a DNS-CERT

12 Mar 2010
By Paul Vixie

This week at the ICANN meeting in Nairobi, a plan was announced by ICANN staff to create a "CERT" for DNS. That's a Community Emergency Response Team (CERT) for the global Domain Name System (DNS). There are all kinds of CERTs in the world today, both inside and outside the Internet industry. There isn't one for DNS, and that's basically my fault, and so I have been following the developments in Nairobi this week very closely.

BIND 10 and Unit Testing

10 Mar 2010
Jeremy C. Reed

The past few months, the BIND 10 developers have been using a test-driven development model. As classes and functions are coded, corresponding unit tests are also coded to help verify the routines do what is expected -- with good or bad input providing correct results. Sometimes the unit tests are written before the new code or the tests are written soon after.

An analysis on the DNSKEY query storm problem

02 Mar 2010
by Jinmei Tatuya

Summary:

We have developed a patch to BIND 9 DNSSEC validator to address a recently reported problem that the validator can cause a massive number of DNSSEC related queries at a high rate when it's configured with a stale trust anchor.  This patch suppresses such queries by caching the trust anchor mismatch and temporarily caching other DNSSEC related responses toward the secure entry point, and should reduce the number of unnecessary queries by 1-2 orders of magnitude.  However, the validator periodically (and unsuccessfully) tries to check the validity of the trust anch

Whither DNSCurve?

25 Feb 2010
by Paul Vixie

At the risk of having this blog begin to read like a FAQ, let me begin once again with the words, "folks have been asking me...".  So:

Surprise bugs and release schedules

10 Feb 2010
By Michael Graff

I know this won’t be a shock to anyone, but software has bugs.

Sometimes they are discovered and have little real impact — perhaps a few lines of code change and are easily tested. Ideally they occur early in a release cycle so they don’t really affect much. Most of the time these are minor and are easily put into a release at any point.

The Signed Root Is Coming! (And what this means for you)

30 Jan 2010
By Peter Losher

In the Fall of 2009, the organizations responsible for generating the root zone, ICANN, Verisign, and the US Department of Commerce, announced that they had come to a agreement on how to sign the root zone with DNSSEC (DNS Security Extensions) A website has been created by ICANN and Verisign to provide information about the change and a rollout timeline.

Why is ISC a not-for-profit?

23 Jan 2010
Paul Vixie

I was asked recently, "why is ISC a not-for-profit?" Apparently we walk
like a for-profit and we quack like a for-profit but we are in fact not
for-profit. Most companies with a strong brand like ours have share
holders. Why not ISC?

Primarily because the infrastructure we're responsible for -- BIND, F-root,
our network -- has to be kept in the public interest. If the current
staff and board got killed by a freak meteor shower, it's nice to know
that our successors couldn't take ISC's assets out of the public's service.

ASN Collisions and Human Error

03 Jan 2010
Leo Bicknell

There is nothing more sensational than the unexpected, and when the NANOG (North American Network Operators Group) community was recently informed that an ASN collision had occurred it caused a lot of people to sit up and take notice. This event was also very interesting in that researching takes us back to a time before ARIN and RIPE existed, creating an interesting historical twist.

Some ideas from the AFTR implementation

11 Dec 2009
By Francis Dupont
I'd like to share an idea I implemented for AFTR (so I am describing it in the AFTR context) which is a part of the debug primer and which could be integrated into BIND 10.
 
AFTR is managed through control channels (over TCP or a stream Unix socket) like a BIND 9 rndc but in a connected mode (so on the AFTR side it is named "sessions").

blog topics

monthly archive

Share this