- dns-wg - mailman.ripe.net

list of European/Southern & Eastern Mediterranean countries
by Guy Davies 27 Oct '95

27 Oct '95

Hi All, This is the list of Countries to which I have sent the questionnaire. It is based on the list in The Whole Internet... and includes those countries in Europe, on the Eastern and Southern Coast of the Mediterranean and those I recognised from the former Soviet Union. 'al','dz','ad','am','at','az','by','be','ba','bg','hr','cy','cz','dk','eg','ee', 'fo','fi','fr','ge','de','gi','gr','gl','hu','is','ie','il','it','kz','kg','lv', 'lb','ly','li','lt','lu','mk','mt','md','mc','ma','nl','no','pl','pt','ro','ru', 'sm','sk','si','su','es','se','ch','tj','tn','tr','tm','ua','uk','uz','va','yu' If anyone knows of a country I have missed, please do not be offended. Tell me who it is and I will send the SOA a copy of the questionnaire. :-) Regards, Guy Davies tel: 01223 250122 ---------- fax: 01223 250121 Network Support Engineer email: guyd(a)pipex.net Unipalm PIPEX url: http://www.pipex.net 216 Cambridge Science Park, Milton Road, Cambridge, CB4 4WA

2 1

Final version of BIND
by zsako＠banknet.net 24 Oct '95

24 Oct '95

Hello everybody, You probably remember the discussion at the 22nd RIPE meeting about trying to get a "final" version of BIND, that could be recommended for everybody to use. It seems it is not possible yet. :( Regards, Janos ----- Begin Included Message -----

1 0

Re: Latest version of BIND
by paul＠vix.com 24 Oct '95

24 Oct '95

>Does anybody know about the release date for the FINAL version of >bind-4.9.3. If so, please email it to me at ali(a)protosoft.com. there will be at least another beta. -- Paul Vixie La Honda, CA "Illegitimibus non carborundum." <paul(a)vix.com> pacbell!vixie!paul ----- End Included Message -----

1 0

TLD Questionnaire
by Guy Davies 15 Oct '95

15 Oct '95

Hello All, Here's the first draft for the TLD questionnaire. I propose to send it to the SOA for each European TLD with a note to forward it to the SOA for any neutral subdomains (e.g. co.uk, ac.at) as they are more likely to be aware of the day to day running of the domains available for use by the 'public'. If anyone has any objections or modifications, please contact me and I'll try to include them. If I hear nothing by the end of next week (20th October), I'll send the questionnaire unaltered. If anyone has a list of *all* the European TLDs, please send me a copy so I can mail all the SOAs. Regards, Guy Davies tel: 01223 250122 ---------- fax: 01223 250121 Network Support Engineer email: guyd(a)pipex.net Unipalm PIPEX url: http://www.pipex.net 216 Cambridge Science Park, Milton Road, Cambridge, CB4 4WA -------------------------------------------------------------------------- DNS Questionnaire ================= 1. Who defines your policies? 2. How do you establish your naming policies? 3. What legal status, if any, do your decisions/policies have? 4a. Would you register sub.tld (e.g. co.uk, ac.uk etc)? b. Do you have geographic subdomains in the tld (e.g. state.tld, county.tld)? c. If so, how do you split your tld? 5a. Would you register domain.tld (e.g. microsoft.uk)? b. Would you register domain.sub.tld (e.g. microsoft.co.uk)? 6a. Do you allow individuals to register names or just organisations? b. If you differentiate between individuals and organisations, what are your criteria? 7a. Do you require proof of identity? b. If so, how do you prove the identity of a requestor? 8. Do you register domains only for organisations/individuals located in your country or do you allow anyone to register in your tld? 9a. Do you allow a single organisation to register more than one domain? b. If so, do you limit the number of domains registered by a single organisation? 10a.To whom would you allocate well known names like digital.tld/ digital.sub.tld? b.What criteria do you use when deciding whether or not to allow a name? 11a.How do you arbitrate between two or more claims to the same name? b.Who is responsible for the arbitration? 12a.Do you allow the registration of geographical names (cities, countries, rivers, etc)? b.If so, would you register one for an individual organisation? 13a.Do you have any names which may not be registered (e.g. names in bad taste, names of protocols, etc)? 14a.Do you run secondary nameservice for subdomains of the tld? b.If so, is this optional/mandatory and do you charge for the service? 15a.Do you check for a running nameserver at the time of request? b.Do you check for a running nameserver at regular intervals after the name has been delegated? 16. Do you allow the reservation of names (i.e. no running service)? 17a.Do you charge for reservation/registration of names? b.If so, is it a one off fee, an annual subscription or both? c.How much is the fee? 18a.Do you remove unused domain names? b.If so, how do you define an unused domain? 19. Do you think that the current system you operate will be changed over the next 12 months? 20. Do you accept requests for domains from providers only, from anyone or from a different group only? 21. What resources are allocated to the administration of the domain? 22. Do you have any automation of the registration/delegation process?

1 0

RIPE 22 agenda proposal
by egoshin＠ihep.su 27 Sep '95

27 Sep '95

Hello All, I can suggest the following questions for discussion in nearest RIPE 22 on DNS WG. It is only my opinion, and any comments, proposal and objections are approved. 1. DNS failures. Report about some results of problem investigation. - I can do some short report. - Also it would be beautifull if somebody (from CH?) can comment the last situation about invalid A RR of one root server, I don't have detail information yet. 2. Directions of DNS development. During last IETF I met with Paul Vixie and we have some talk about possible directions of DNS development. I can report about this (DNS v2 ?). 3. Domain name payment. Consequences and problems for cooperation and DNS. It is about last decision of .XXX domain payment. Regards, - Leonid Yegoshin, LY22

1 0

Re: DNS Problem
by Mike Norris 15 Sep '95

15 Sep '95

On Mon, 11 Sep 1995 11:39:26 +0200 Willi Huber <huber(a)chx400.switch.ch> said: >Dear all, > >there seems to be a DNS problem regarding the root name servers. We >(that means the ch top-level DNS server) has picked up several times >now a false A record for E.ROOT-SERVERS.NET. The address picked up is binary >zero. A restart only helps for a short time. Other top-level DNS servers >contain the false entry as well. Are there any recommendations for hostmasters of (1) top-level domains and (2) subsidiary domains? Should all be using the new A, B, C etc list of root-level servers? Many thanks. Mike Norris

4 8

Re: DNS Problem
by e07＠nikhef.nl 15 Sep '95

15 Sep '95

> BTW, 'dig . txt' gives an empty response. Don't know > what to think of that... :-) I know what to think of that. See my message of yesterday on the ripe-list. (Sorry, couldn't resist :-) -- Eric

1 0

Re: DNS Problem
by e07＠nikhef.nl 15 Sep '95

15 Sep '95

> in the old situation one could see at first glance > where a root server is located. With the ABC list > system that's no longer possible. It is at second glance. -- Eric [] for SERVER in A B C D E F G H I [] do [] host -t txt ${SERVER}.root-servers.net [] done A.root-servers.net TXT "formerly ns.internic.net" B.root-servers.net TXT "formerly ns1.isi.edu" C.root-servers.net TXT "formerly c.psi.net" D.root-servers.net TXT "formerly terp.umd.edu" E.root-servers.net TXT "formerly ns.nasa.gov" F.root-servers.net TXT "formerly ns.isc.org" G.root-servers.net TXT "formerly ns.nic.ddn.mil" H.root-servers.net TXT "formerly aos.arl.army.mil" I.root-servers.net TXT "formerly nic.nordu.net"

2 1

Re: DNS Problem
by e07＠nikhef.nl 15 Sep '95

15 Sep '95

> your dislike of the new ABC system. For the sake of > alphabetical order it sacrifices useful positional > information. No, the only reason for the change was to be able to use much better name compression to prevent udp packet overflow for those replies that need the list of all root servers and their addresses. -- Eric

1 0

Re: DNS Problem
by zsako＠banknet.net 15 Sep '95

15 Sep '95

> From: Robert Martin-Legene <robert(a)dknet.dk> > To: Piet Beertema <Piet.Beertema(a)cwi.nl> > Cc: dns-wg(a)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

1 0