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 Problem
- Previous message (by thread): DNS Problem
- Next message (by thread): DNS Problem
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Janos Zsako
zsako at banknet.net
Fri Sep 15 12:55:12 CEST 1995
> From: Robert Martin-Legene <robert at dknet.dk> > To: Piet Beertema <Piet.Beertema at cwi.nl> > Cc: dns-wg at ripe.net > On Fri, 15 Sep 1995, Piet Beertema wrote: > > > - In the init file one could still see where a given > > root server is located, by comparing the A record > > with the A records of the root servers. > > A bit complicated.. If the in-addr.arpa didn't map to the root-servers.net > zone, but to the old name you could easily use host -A e.root-servers.net > and find the old "location". Why they didn't do that I'm not really sure.= I suppose it is mainly because the "old location" can have several IP addresses only one of which is defined in the root-servers.net domain (ns.nasa.gov is such an example). This can probably allow for security features such as packet filtering on destination address. By the way, PSI.NET has solved the problem in a similar manner to what you suggest, but the other way round: c.psi.net CNAME c.root-servers.net c.root-servers.net A 192.33.4.12 Janos Zsako
- Previous message (by thread): DNS Problem
- Next message (by thread): DNS Problem
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]