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]/
2nd Root Server in Europe (fwd)
- Previous message (by thread): 2nd Root Server in Europe (fwd)
- Next message (by thread): 2nd Root Server in Europe (fwd)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Lothberg
roll at Stupi.SE
Sun Jan 19 16:00:46 CET 1997
> > What has been > > discussed in the past at the LINX, and I believe was discussed again > > today, was a root server for "." We think that what would be of most > > benefit to Europe would be a full root name server, including the > > largest domains (.com and .net), and this is what we discussed with > > Paul Vixie and proposed to Jon Postel last year. The .COM and .NET domains are very large, they have many querries, but the . nameservers serves the universe. Suggestion; Separate the . (root) from the next level (.country, .net, .com) servers.. So, instead of putting ONE host on the network behind the router, put TWO, and the second one could handle the second level domains you wish. Maybe there should be a THIRD host to serve the country toplevel domain (.uk in this case) and maybe toplevel for other countries the region. (.nl, .es, etc..) Hosts are cheap, running them with a quality service is more expensive, but the number of users affected by the performance and availiabilty and performace are VERY high... > > > Shared resources has to bee keept as neutral as possible, and having > > > for example a root-name-server behind it's own router attached to a well > > > recogized public exchange point seems to be the best avaliable > > > implementation today. > > > > This is in fact exactly the physical arrangement that we have proposed: > > a root name server on its own class C one hop off the LINX. > > Not from a routing policy point of view - will you put the root > server in a seperate AS, or will connectivity be constrained by > your peering/routing policy ? The nameservers has to be in their own AS, behind their own router(s) and account for traffic to be in the 400kbps in / 700kbps out range and estimate growth to 10% month. So full-duplex FDDI or full-duplex fast Ethernet is a requrement. The peering policy of this as should be something like; Peer with anyone who request to peer. Maybe it even should accept circiuts from those who just want to have good connectivity to the nameservers, but don't care about the particular exchanage point. ------------------------------------------------------------------------ I would suggest that once everyone agreed on a workable model that we also implement that for other root namseservers. --Peter
- Previous message (by thread): 2nd Root Server in Europe (fwd)
- Next message (by thread): 2nd Root Server in Europe (fwd)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]