This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/dns-wg@ripe.net/
[dns-wg] Elimination of 2nd level ccTLD domain names
- Previous message (by thread): [dns-wg] Elimination of 2nd level ccTLD domain names
- Next message (by thread): [dns-wg] Elimination of 2nd level ccTLD domain names
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Yiorgos Adamopoulos
adamo at central.tee.gr
Mon Oct 25 15:23:37 CEST 2004
Jay Daley wrote: [ most of the message snipped ] > - You then have to manage another system on each nameserver, and that > brings with it a new set of dependencies and vulnerabilities, that you > could just as easily do without. Out view has always been to minimise the > number of unnecessary processes on any production nameserver. > > Some of this is, of course, supposition so I would be interested to know > if anyone else thinks using database in this way is simple. Well for the moment we are using a flat-file "database" that is going to be moved to Oracle in the next 4 months (as part of many other things integrated to it). Actually you do not have to run a database instance on every node where you want to run a DNS server. Why not have the Database system produce the zone files for the nameserver of your taste (be it NSD, tinydns, BIND, etc) and then rsync to the actual servers? -- Yiorgos Adamopoulos -- adamo at central.tee.gr Technical Chamber of Greece -- #include <std/disclaimer.h> Work Phone: +30.2103671130 -- FAX: +30.2103671101
- Previous message (by thread): [dns-wg] Elimination of 2nd level ccTLD domain names
- Next message (by thread): [dns-wg] Elimination of 2nd level ccTLD domain names
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]