- dns-wg - mailman.ripe.net

RE: DNS Top Level Domain Questionnaire
by Wilfried Woeber, UniVie/ACOnet 07 Nov '95

07 Nov '95

>It is not clear to me what the difference is between "ETLDF" and the >DNS-WG is. Actually, I think this is a very interesting question. I think we would never have asked ourself this question if we hadn't received the (for me) surprising formal statement from the Dutch Naming Authority! I'd like to think that most of the parties involved are slightly over-reacting. On the other hand, we have had a couple of issues in the past where I perceived a less than perfect agreement between RIPE-WGs and the points of view of some TLD administrator... > Further the request was for a closed repository. These are I think this is really a minor issue - if the RIPE-NCC is not the proper place to store non-public information, well then there is alternatives available. My *personal* point of view is that DNS coordination, and TLD administration, with all of it's aspects should be an open activity. If some of the TLD administrations do think otherwise, then this should be sorted out first. The other conclusions would then be rather easy, I suppose. >both different from EOF. EOF is a normal RIPE working group governed by >the RIPE Terms of Reference and any of their material stored at the NCC >is publicly available. > >In other words: If the RIPE-DNS WG asks for an open repository there is >no problem and we will do it immediately. If a closed subgroup asks for >a closed repository this needs consultation with the RIPE chair, the WG >chair and possibly the contributors. Reasonable. More so as there is not necessarily a direct realtionship between a TLD administration function and the RIPE-NCC contributions. >Please understand that I take this slightly more formally than usual >because it is a matter of principle that all activities of RIPE and RIPE >working groups are open. I support this view. Although I have the feeling that the reasoning about how and/or where to store this type of information was fairly less formal :-) Wilfried. -------------------------------------------------------------------------- Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at Computer Center - ACOnet : Vienna University : Tel: +43 1 4065822 355 Universitaetsstrasse 7 : Fax: +43 1 4065822 170 A-1010 Vienna, Austria, Europe : NIC: WW144 --------------------------------------------------------------------------

1 0

RE: DNS Top Level Domain Questionnaire
by Christian Panigl, ACOnet/UniVie +43 1 4065822-383 07 Nov '95

07 Nov '95

>Date: Mon, 06 Nov 1995 16:54:26 +0100 >From: Daniel Karrenberg <Daniel.Karrenberg(a)ripe.net> > >I think the WG should re-ask itself what the purpose of the exercise >was. Was it to let TLD admins see what others do? If yes, circulate >the results among the respondents and give it a wider audience (the WG) >later on, if all respondents agree. At least this was my interpretation. Christian --- Christian Panigl : Vienna University Computer Center - ACOnet --- --- VUCC - ACOnet : -------------------------------------------- --- --- Universitaetsstrasse 7 : Internet: Christian.Panigl(a)CC.UniVie.ac.at --- --- A-1010 Vienna / Austria : Tel: +43 1 4065822-383 (Fax: -170) ---

1 0

Re: A proposal from RIPE DNS Working Group
by Artur Romao 03 Nov '95

03 Nov '95

Hello, > I'm glad to contact you, acting on request of the ripe dns working > group which, during the last RIPE meeting in Amsterdam, discussed about > DNS failures and made a proposal as stated in the following excerpt > from the minutes: > > {...} > Some people do not watch their name servers: it happens that some name > servers are left unattended and fail without anyone noticing. This > has an impact on the performance and reliability of the overall name > service. > > People should watch their name servers and their zones on their primary > and secondaries. At least the 'host' command can be used with the '-C' > option to do this at regular intervals. > > During the plenary session someone remembered the existance of > RFC1713 A. Romao, "Tools for DNS debugging", which is usually > referred to as the guide for DNS administrators and suggested to ask > the author to include such recommendation. > > [ACTION on ABB] > {...} I was planning to write an updated version of the RFC some time next year (since it's also an FYI I'm supposed to update it regularly). Among other things I'm waiting for BIND-4.9.3 final to be released, and there seems to be a lot of new tools available, so I have to take a look at them. I appreciate your comments, they fit well in the new scheme I'm thinking about. Of course, if anyone has any other suggestions, they're very welcome, too. Thanks for your input. Regards, .artur -- ======== ____ ==== Artur Romao ======= / / / ___ ___ /_ ===== PUUG - EUnet Portugal ====== /---- / / / / /___/ / ====== Qta Torre 2825 Mte Caparica ===== /____ /___/ / / /___ /_ ======= http://www.Portugal.EU.net/ ==== ======== mailto:Artur.Romao@puug.pt

1 0

DNS registration ?
by Alex V. Soldatov 01 Nov '95

01 Nov '95

Good day! Help me, please. How my organization stand in DNS registration? Which sheet must be feel ? kAK ZAREGISTRIROWATX DNS DOMEN? ~TO TREBUETSQ DLQ \TOGO? Best regads, Alexey V. Soldatov /* Sverdlovsk Main Regional Department /* the Central Bank of Russia /* Ekaterinburg

2 1

Re: A proposal from RIPE DNS Working Group
by e07＠nikhef.nl 31 Oct '95

31 Oct '95

> People should watch their name servers and their zones on their primary > and secondaries. At least the 'host' command can be used with the '-C' > option to do this at regular intervals. [] host -C -A -L 1 zonename is what you really want to do. This covers most common problems. If that comes out clean, you are probably safe ... -- Eric Wassenaar P.S. For those of you who want to stay up to date: [] host -V Version 951024

1 0

A proposal from RIPE DNS Working Group
by Antonio_Blasco Bonito 31 Oct '95

31 Oct '95

Dear Artur Romao, I'm glad to contact you, acting on request of the ripe dns working group which, during the last RIPE meeting in Amsterdam, discussed about DNS failures and made a proposal as stated in the following excerpt from the minutes: {...} Some people do not watch their name servers: it happens that some name servers are left unattended and fail without anyone noticing. This has an impact on the performance and reliability of the overall name service. People should watch their name servers and their zones on their primary and secondaries. At least the 'host' command can be used with the '-C' option to do this at regular intervals. During the plenary session someone remembered the existance of RFC1713 A. Romao, "Tools for DNS debugging", which is usually referred to as the guide for DNS administrators and suggested to ask the author to include such recommendation. [ACTION on ABB] {...} ---------- ---------- Antonio_Blasco Bonito E-Mail: bonito(a)nis.garr.it GARR - Network Information Service c=it;a=garr;p=garr;o=nis;s=bonito c/o CNUCE - Istituto del CNR Tel: +39 50 593246 Via S. Maria, 36 Fax: +39 50 904052 I-56126 PISA Telex: 500371 CNUCE I Italy Url: http://www.nis.garr.it/nis/staff/bonito.html ---------- ----------

1 0

Draft minutes of ripe22-dnswg
by Antonio_Blasco Bonito 30 Oct '95

30 Oct '95

Better late than never... Here are the drafts minutes scribed by Benoit Grange and edited by me. Please send corrections/additions to the list before 951110. ---------- ---------- Antonio_Blasco Bonito E-Mail: bonito(a)nis.garr.it GARR - Network Information Service c=it;a=garr;p=garr;o=nis;s=bonito c/o CNUCE - Istituto del CNR Tel: +39 50 593246 Via S. Maria, 36 Fax: +39 50 904052 I-56126 PISA Telex: 500371 CNUCE I Italy Url: http://www.nis.garr.it/nis/staff/bonito.html ---------- ---------- --------------------cut here------------ DRAFT-DRAFT-DRAFT-DRAFT-DRAFT-DRAFT-DRAFT-DRAFT-DRAFT-DRAFT-DRAFT-DRAFT-DRAFT RIPE 22 DNS Working Group minutes Amsterdam 12 October 1995 Chairman: Antonio Blasco Bonito (ABB) Scribe: Benoit Grange (BG) Preliminaries ------------- Rob Blokzijl presented the apologies from the working group chairman, Leonid Yegoshin (LY), who had a visa problem and asked ABB to chair the group. The agenda was reorganized and agreed. 1) Reports about DNS Failures -------------------------- [This item should have been covered by LY, but because he was not there some of us reported current problems] BG talked about the known problem with uncesessary glues that appear in zone transfers. This happens on most old implementations (BIND prior to 4.9) as shipped my most of the vendors. DNS Operation suffer from old implementation that have known bugs and proble ms. The usual suggestion is to install a recent version of BIND, which happens to be a beta version. It was noted that, altough that effectively eliminates the problem, many DNS administrators are not willing to use a beta version. The working group agreed on sending a letter to the ISC to ask to put BIND 4.9.3 in final so that doubts about it are solved. [ACTION on ABB] Many expressed concern about how delegation changes are done at the Internic. Today Internic accepts any change to current delegation (normal and reverse) and also to glue records. This leads to situation where some bad data is introduced, either as an error, or as some malicious action. Eg: 'ns.ripe.net' (193.0.0.193) is primary for 'ripe.net' and a lot of important zones. John Doe wants to create a 'johndoe.com' zone and submits a request to Internic mentionning both 'banana.johndoe.com' (198.1.2.3) as primary and 'ns.ripe.net' with a WRONG address 193.0.0.93 because of a typo. Internic creates the 'johndoe.com' zone and CHANGES the glue record for 'ns.ripe.net'. All delegations to 'ns.ripe.net' are affected because Internic accepted unnecessary glue record from John Doe and blindly accepted to change an existing name server IP address. The working group recommends that Internic does not accept unneccessary glue records and double checks any change to existing glue records. [ACTION on Geert Jan de Groot] Some people do not watch their name servers: it happens that some name servers are left unattended and fail without anyone noticing. This has an impact on the performance and reliability of the overall name service. People should watch their name servers and their zones on their primary and secondaries. At least the 'host' command can be used with the '-C' option to do this at regular intervals. During the plenary session someone remembered the existance of RFC1713 A. Romao, "Tools for DNS debugging", which is usually referred to as the guide for DNS administrators and suggested to ask the author to include such recommendation. [ACTION on ABB] 2) 'in-addr.arpa' automatic checking and delegation (D. Kessens) ------------------------------------------------------------- David briefly talked about the tool he wrote which is being used at RIPE- NCC. This tools checks if the reverse zone is correctly configured as per RIPE requirements. Usage: Send an e-mail message to 'auto-inaddr(a)ripe.net' containing the 'inet-num' object with 'rev-svr:' attributes listing the desired name servers (1 name server per line). Send an empty message to get help. The final editing of the zone file is still done manually and the operators also checks the author of the update. After a short discussion the group agreed that some authentication mechanism be added in order to avoid malicious changes to current delegation, specially when the reverse delegation process will be completly automated. [ACTION on RIPE-NCC] This tool could also be used to check for normal delegations, but only after some rewriting because some of the checks are specific to reverse delegation or RIPE requirements. Sources are on ftp://ftp.ripe.net/tools/inaddrtool-VERSION Another tool to check delegation exist under http://www.nic.fr/ZoneCheck Sources of this tool will be freely available by the end of the year. [ACTION on BG] 3) Future developments of the name servers --------------------------------------- It was reported that: Paul Vixie got RU-BIND and will somehow merge the two programs. IBM has donated code to do dynamic updates, and an other source is available as well. 4) About the recent changes of the root name servers ------------------------------------------------- All root name servers have been renamed as '<letter>.root-servers.net'. If you want to know the "old name" of a name server, query for the TXT record associated with the name. A new primary for the root zone will be created and managed directly from IANA, and the primary for the '.com', etc. zones will remain managed by Internic. 5) Charging for domain names, etc. ------------------------------- A European 'TLD' forum might be useful, and the first move should be to collect how TLD management is done over Europe. Different countries have different policies, etc. Some multinational company which wants to create a bunch of domains in different countries needs more information on how this can be done and who should be contacted. The working group decided to set up a questionnaire and Guy Davies (GD) collected a lot of questions. He will organise the questionnaire and submit it to the list for review and later send it to the European TLD admins. [Action on GD] DRAFT-DRAFT-DRAFT-DRAFT-DRAFT-DRAFT-DRAFT-DRAFT-DRAFT-DRAFT-DRAFT-DRAFT-DRAFT

5 8

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