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/[email protected]/
[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 ]
Jaap Akkerhuis
jaap at NLnetLabs.nl
Wed Oct 27 12:07:57 CEST 2004
<Just back from a trip, and checking mail. Seems that dns-wg got busy when I was gone> That said, I do believe that huge text files for zone files and name server configurations will eventually move to some sort of database back-end. This is the direction that most DNS implementations seem to be moving towards. Some TLDs have already adopted this approach and I'd be surprised if others didn't follow. The drawback of using a direct database back-end is that this means that are close ties between the nameserver and the database. If one of the two fails, you have a problem. That is why I don't see zone files go away. Whit a zone file you can easely change the name server for a new one when needed. jaap
- 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 ]