http://slashdot.org/comments.pl?sid=55040threshold=-1commentsort=3tid=185mode=threadpid=5379648
Well this isn't really as true or good as I wish it was.
The nsd in this case is not the naviserver daemon we all enjoy but a
nameserver daemon written at NLnet Labs in cooperation with RIPE.
On 2003.02.25, Jerry Asher [EMAIL PROTECTED] wrote:
The nsd in this case is not the naviserver daemon we all enjoy but a
nameserver daemon written at NLnet Labs in cooperation with RIPE.
Should we add to the confusion and start coding up an nsdns module so
one could use AOLserver to serve DNS?
Dossy wrote:
On 2003.02.25, Jerry Asher wrote:
The nsd in this case is not the naviserver daemon we all enjoy but a
nameserver daemon written at NLnet Labs in cooperation with RIPE.
Should we add to the confusion and start coding up an nsdns module so
one could use AOLserver to serve DNS? :-)
Dossy [EMAIL PROTECTED] writes:
If there was an nsudp socket, we could implement a DNS server that
runs out of AOLserver that could use any nsdb to store zone data in
a DBMS ... that might be mildly interesting.
Really cool, in fact! If it were efficient enough, it would save the
trouble of
On Tuesday, February 25, 2003, at 03:05 PM, Rob Mayoff wrote:
+-- On Feb 25, Dossy said:
Added bonus would be a web interface for viewing zones and editing
them, which would persist changes back down to the DBMS.
Note that a web interface to your DNS data doesn't require that
AOLserver
- Original Message -
From: Rob Mayoff [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, February 25, 2003 1:07 PM
Subject: Re: [AOLSERVER] Root-server switches from BIND to NSD.
+-- On Feb 25, Patrick Spence said:
I'd certainly be willing to use it here :) it would
