May 1994 - dns-wg - mailman.ripe.net

Re: register esa.ch
by Piet Beertema 25 May '94

25 May '94

What's in a name...? Piet ---------------------------------------------------------------------------- Newsgroups: nlnet.announce From: jan(a)cs.ruu.nl (Jan van Leeuwen) Subject: ESA'94 accepted papers Message-ID: <Cq9GI0.4Lz(a)cs.ruu.nl> Keywords: ESA'94, algorithms Organization: Utrecht University, Dept. of Computer Science Date: Mon, 23 May 1994 15:03:36 GMT 2nd Annual EUROPEAN SYMPOSIUM ON ALGORITHMS (ESA'94) Utrecht (the Netherlands), September 26-28, 1994 ADVANCE INFORMATION The Final Program/Call for Participation for ESA'94 will be distributed around June 1st. Further information on ESA'94 can also be obtained by consulting the `ESA page' on World Wide Web under the following URL: http://www.cs.ruu.nl/esa/ or by sending email to esa(a)cs.ruu.nl (preferably). See you at ESA'94!

1 0

Re: register esa.ch
by Dave Morton 24 May '94

24 May '94

> > Arnold Nipper <nipper(a)xlink.net> writes: > > > > Of course. Any other ideas how to cope with the problem? > >How about the latest Postel proposal: Actually I quite like Jon's proposal but it was not quite the same as you suggest. Replace .DE with .PVT below. >Create 999 subdomains 1.de to 999.de. Have to the the current DE-NIC consortium to agree to this and they probably wont... >In each of them create 999 subdomains 1.x.de - 999.x.de. >You have just mapped namesapce for a million registries >under DE with names that have little to no connotations with >anything. Agreed. >To anyone who wants to run a registry for individuals, >assign *randomly* an x.y.de combination. I can then find a >friend who will register me as karrenberg.123.456.de, if >I do not like his policy I will go to 453.295.de and register >there. > >Anything wrong with that? Nope, but it still doesn't help finance a NIC for DE or replace DE with your favourite European TLD. > >Daniel Dave

1 0

Re: register esa.ch
by Dave Morton 24 May '94

24 May '94

>a) Is this plan actually to be considered as serious or more rumor? Serious but without consenus yet.. >b) Is this mailing list the right forum to discuss it? Well, yes and no. It's a national issue but has global effects. >Michael > Dave

4 3

Re: Removal nameserver an rev-srv tags
by Daniele Vannozzi 24 May '94

24 May '94

On Fri, 20 May 94 18:28:53 GMT you said: >> Concerning the assumption of dns-wg about the useless of those tags and >> the absence of procedures based on them we would like to inform you that >> we are presently testing some automatic tools based exactly on those >> tags which we use before actually registering a new direct or inverse >> domain. >> Starting from the contained information, each server is queried on >> properly resolving the query. > >Do you mean, you first build the domain object, insert it into the database >and then get a list of nameservers out of it, in order to do your querying? >And only then you consider the domain configuration ok? > >If this is the case, why don't you get the NS list from the (soon to be) >primary nameserver, and if all is ok then you register the domain itself >and the domain object in the database? Or did I miss something? Artur, many thanks for your help. I think it's necessary to explain our procedure. When we receive a domain form (domain registration template) we check the primary nameserver (we use the first "nameserver:" tag to locate it). How to find otherwise that server without a nameserver tag? If the primary nameserver is reachable and properly configured we continue checking secondary nameservers which should be listed in the domain form and as NS records in the primary nameserver. The above is a useful check because many times there are discrepancies in what is "declared" and what is actually configured. In addition, if in the domain form there is our nameserver listed as a secondary, we also check the refresh time, retry time, expiration period and default ttl. Only after a successful check the domain object is added to database and the country master server is reloaded with the new information. Regards, Daniele > >We do this before registering a domain under PT... > >.artur > Daniele Vannozzi Phone: +39 50 593280 GARR-NIS Phone NIS: +39 50 593360 c/o CNUCE - Istituto del CNR Fax: +39 50 904052 Via Santa Maria 36 Telex: 500371 - CNUCE 56100 Pisa - Italy E-mail: vannozzi(a)nis.garr.it

2 1

register esa.ch
by Walter Dillen - ESAnet Services Section (ECNOD/COM/ES) 24 May '94

24 May '94

- To all you gentlemen who have contributed to the discussion so far - As ESA-internal coordinator of domains and naming structure, I am obviously not too pleased to see another organisation use the same acronym, but I don't believe that this necessarily causes major problems. This is because of the following. In addition to adopting the registration policy recommended to us by RIPE, namely to register in each country esa.<TLD>, we have established a further convention. Underneath the esa.<TLD>, the name of the ESA establishment is added as a further subdomain in all cases, e.g. estec.esa.nl esoc.esa.de esrin.esa.it, etc. This implies that chances of a clash in domain names are *very* small. Furthermore, ESA has currently no establishments in CH and therefore no intention to register esa.ch. For the hypothetical case where this would happen, the question remains for me if and how the responsibility for a 2nd-level subdomain can be shared and coordinated between two organisations? Btw, I also know about another potential conflict coming up - I've heard of plans within Germany to align 2nd-level domain names with the regional abbreviations known to all from German car plates - e.g. K for Cologne, DA for Darmstadt, etc. Assuming that we as international organisation could stay out of this scheme and retain esa.de, this would cause a clash with the region of Eisenach (also ESA), and the same considerations as above would apply. Comments/Suggestions welcome! Regards, Walter ------------------------------------------------------------------ European Space Agency/Operations Centre Tel: +49-6151-90-2213 Robert Bosch Strasse 5 Fax: +49-6151-90-4213 D-64293 Darmstadt, Germany email: wdillen(a)esoc.bitnet

4 6

Re: register esa.ch
by Dave Morton 22 May '94

22 May '94

> Btw, I also know about another potential conflict coming up - I've heard > of plans within Germany to align 2nd-level domain names with the regional > abbreviations known to all from German car plates - e.g. K for Cologne, > DA for Darmstadt, etc. >Crazy idea: if company X moves from Cologne to Darmstadt, >its domain name would change, they would have to reprint >their letter heads, business cards, etc., and someone would >have to cope with all the bounces of mails sent to the old >domain name... Walter - I don't know where you heard of plans - there is some brainstorming in progress to somehow put structure on the DE domain - that's about as far as things have progressed until now. I'd believe the people involved (many of whom are on the RIPE DNS list) are aware of the potential problems so don't expect any surprises. > Assuming that we as international organisation could stay out of this scheme > and retain esa.de, this would cause a clash with the region of Eisenach (also > ESA), and the same considerations as above would apply. >Which makes it unlikely that you could stay out of such a >"reorganisation" (I'd rather call it a mess-up). I, for one, would expect any such plan, assuming it ever were to be implemented, not to be implemented retrospectively, this would not be acceptable. > Comments/Suggestions welcome! >Contrary to what I've suggested to you long ago, I'd now >recommend that you put ESA under the .INT domain; chances >are zero that there will ever be a .EU domain for Europe, >unless someone can convince the Powers That Be that there >is a very clear need for such a "pseudo top level domain", >quite analogous to the current 3-letter TLD's; or maybe >the analogy could be carried even further by creating a >domain .EUR; but then, who is going to manage it? Good idea with INT now that X.400 is dying. Mabye EU or EUR is not such a good idea for ESA since one cannot exclude that they establish or have a launch facility in S. America but that's beside the point. Why shouldn't we beat up Mr. IANA for an .EUR and get the Commission to finance it, after the event that is :-) > Piet Dave

1 0

Re: Removal nameserver an rev-srv tags
by Artur Romao 20 May '94

20 May '94

> Concerning the assumption of dns-wg about the useless of those tags and > the absence of procedures based on them we would like to inform you that > we are presently testing some automatic tools based exactly on those > tags which we use before actually registering a new direct or inverse > domain. > Starting from the contained information, each server is queried on > properly resolving the query. Do you mean, you first build the domain object, insert it into the database and then get a list of nameservers out of it, in order to do your querying? And only then you consider the domain configuration ok? If this is the case, why don't you get the NS list from the (soon to be) primary nameserver, and if all is ok then you register the domain itself and the domain object in the database? Or did I miss something? We do this before registering a domain under PT... .artur

1 0

Re: register esa.ch
by Dave Morton 20 May '94

20 May '94

Mike - I think the context at that time (and I'm sure Piet will remind me if I'm wrong) was that in a few years we all might need to run this wonderful X.400 stuff and the addressing (if one can call it that) in X.400 did not foresee any ADMDs called INT or ORG so if one wanted to change later you'd have a problem (besides X.400 that is :-). Since X.400 seems more or less destined to die young now that we will have SMTP with all the goddies included (see the latest draft rfcs up for approval as standards) I would assume Piet's advice might be in this direction now. Again Piet will correct if I'm off the tracks here.... Given the above you can probably safely stay with .ORG and .INT until we all collect our pensions at least. Cheers. Dave PS: Also given that J. Postel recently suggested a scheme for a new TLD's you also might want to register under one of them ;- This could have interesting consequences for current TL country Ds and financing thereof (names changed to protect the innocent - but I wander as usual :-)

1 0

RE: Removal nameserver an rev-srv tags
by Wilfried Woeber, UniVie/ACOnet 20 May '94

20 May '94

Dear all, >Blasco has informed us about the proposals and the decision taken during >the last Ripe meeting. >While we found all greats, we disagree about a particular proposal made >at the dns working group. To be concise, we believe obsoleting the I don't want to assess the technical merits of any decisions taken at the DNS-WG, however I'm worried about the organizational merits of any decisions that were taken in WG meetings that had to compete against the Routing-WG and the RIPE-81++ discussions. I for my part did certainly not feel having quorum in the DB-WG, and thus no decisions were taken this time. I'm also going to state this is my minutes... Wilfried. -------------------------------------------------------------------------- Wilfried Woeber : e-mail: Wilfried.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

Removal nameserver an rev-srv tags
by Daniele Vannozzi 20 May '94

20 May '94

Dear all, Blasco has informed us about the proposals and the decision taken during the last Ripe meeting. While we found all greats, we disagree about a particular proposal made at the dns working group. To be concise, we believe obsoleting the rev-srv and nameserver flags from the inetnum and domain objects to not be a meaningful action. Concerning the assumption of dns-wg about the useless of those tags and the absence of procedures based on them we would like to inform you that we are presently testing some automatic tools based exactly on those tags which we use before actually registering a new direct or inverse domain. Starting from the contained information, each server is queried on properly resolving the query. Daniele & Giuliana Daniele Vannozzi Phone: +39 50 593280 GARR-NIS Phone NIS: +39 50 593360 c/o CNUCE - Istituto del CNR Fax: +39 50 904052 Via Santa Maria 36 Telex: 500371 - CNUCE 56100 Pisa - Italy E-mail: vannozzi(a)nis.garr.it

2 1

Re: register esa.ch
by mfendt＠eso.org 20 May '94

20 May '94

>> > Totally correct. If the company moves, they will have to >> > change their business cards, letter heads ... >> > PTT's take care of forwarding letters. Who is going >> > to take care of forwarding e-mail? >> >> Unless the outdated domain name is reissued immediately (not a good idea >> at all) it still lives and the owner is free to populate it with >> appropriate CNAME and/or MX records. So you yourself or your friendly >> service provider care about e-mail forwarding. >> >> Within "DE" there have been some cases in the past where organizations >> changed their domain name (for other reasons but physical relocation), >> and this kind of "forwarding" was used. >> >> -Peter >> A few exceptions are fine and managable, but that idea would probably leads to the fact that there are more than a few. The other issue I see is the fact that we have already problems in addressing multinational organizations in various countries. How do we address lets say companies sitting in Hamburg and Munic. Do you think they like being registered with (This is an example; nobody should be offended by that!) siemens.hh.de, siemens.m.de (or siemens.muc.de), ... I think they will go with siemens.com :_) I consider this idea as good or as bad as the advice of RIPE to register international organizations in the various countries :-) a) Is this plan actually to be considered as serious or more rumor? b) Is this mailing list the right forum to discuss it? Michael

1 0

re: register esa.ch ?
by gveldman＠estcs1.estec.esa.nl 20 May '94

20 May '94

I strongly advice against the use of ESA for anything else but the European Space Agency, even though we use subdomains as estec, esoc etc. It would be very impractical to share the ESA domain with another company, if not practically impossible. Besides, ESA is known internationally around the world as European Space Agency on the international networks and I do not think another company will want to be confused with that well known name. Kind regards, Gerbrand Veldman Mail: Gerbrand Veldman, ESA/Estec, P.O. Box 299, 2200 AG Noordwijk, The Netherlands. Tel: (Int) 31 1719 83113 Fax:- (Int) 31 1719 85095 E-Mail: Internet: gveldman(a)estcs1.estec.esa.nl HEP/SPAN: ESTCS1::GVELDMAN (29717::GVELDMAN) X.400: C=NL A=400NET P=ESA O=ESTEC S=VELDMAN

1 0

Re: register esa.ch ?
by root＠estec.esa.nl 20 May '94

20 May '94

Hi Piet, we are discussing this at the moment with the other ESA sites, will reply soon Rob.

1 0

Re: register esa.ch ?
by root＠estec.esa.nl 20 May '94

20 May '94

I will reply to you in 10 minutes, sorry for the delay in reading the mail, regards ... Robert Williams - European Space Agency (ESA) Keplerlaan 1, 2200 AG Noordwijk - The Netherlands Phone: +31-1719-85403 Fax: +31-1719-85095 E-Mail: INTERNET: postmaster(a)bcserver.estec.esa.nl

1 0

Re: register esa.ch
by mfendt＠eso.org 20 May '94

20 May '94

Hello, Piet wrote: >> Comments/Suggestions welcome! >> Contrary to what I've suggested to you long ago, I'd now >> recommend that you put ESA under the .INT domain; chances >> are zero that there will ever be a .EU domain for Europe, >> unless someone can convince the Powers That Be that there >> is a very clear need for such a "pseudo top level domain", >> quite analogous to the current 3-letter TLD's; or maybe >> the analogy could be carried even further by creating a >> domain .EUR; but then, who is going to manage it? The last two mails actually clarified the issue for me in the respect that there is a more serious problem (i.e how to register multinational organisations) and the as a part the current problem what happens to esa.ch. The esa.ch seems to be solved by the mail from Walter (if ESA doesn't want to use it and doesn't feel that it should be reservered than nobody in Switzerland has to explain a small company that you do not get it, even so you were the first) The other thing which still has to renaimed is the issue of multinational organisations. I asked once on that list about the advice (it was mentioned in the 14. Ripe meeting as the case of the day) indicating that I found the advice stupid (I still do, but not because of the ESA case now :-) and asked for clarification, reasons. I got no serious answer back, so I thought to skip that issue (and stay with .org; that's what we use now). But the advice now to change ESA to .int (even if it would be a good idea to do so) might cause some trouble and I have my serious doubts that they will do that. So it would be quite a good idea to keep that point in mind if an international organization want's to register for the first time, but changing already existing organisation will cause a lot of overhead for them (I just got new business cards :-). Maybe a better solution can be found too, but I can not recommend one off hand. Michael P.S.: .int for ESA was reject in the 14 Ripe meeting with: "workable, but ESA is not a world wide organization" :-) according to the minutes ________________________________________________________________________________ Michael Fendt ESO (European Southern Observatory) Karl-Schwarzschild-Str. 2 85748 Garching Germany Tel: +49 89 32006 441 Fax: +49 89 32023 62 email: mfendt(a)eso.org

1 0

Re: register esa.ch ?
by Dave Morton 20 May '94

20 May '94

> > Dave Morton <Dave.Morton(a)ecrc.de> writes: > > > > Daniel - under that argument you wouldn't object either to someone > > registering RIPE.DE or NL or whatever ? > >I would not object to that given that they have been warned strongly >about all the requests for address space and what-have-you they will >receive and will have to forward. Or shall we register ripe.<all toplevel >domains in the world>? No - of course not and as long as they have been warned - no problem - if someone is silly enough to register such... >Some TLD registrars would ask us for proof that we are a legal entity >in the country concerned. Sure - and the local registry might also face legal problems if they give away an "obvious" name to joe.smoke. The assumption is that the lcoal IR can spot the "obvious" ones - probably not always true unfortunately. Use common sense I'd guess is the only formula - assuming there is any... In this case, anyway, the problem is now solved I see. >Daniel Dave

1 0

Re: register esa.ch ?
by Erik-Jan Bos 20 May '94

20 May '94

Piet, > I have got a request from the company "Einkaufsgenossenschaft > des Schweizerischen Autogewerbeverbands" to register the domain > esa.ch. ESA is the registered name of this company that appears > also on their letters. > I have called their attention to the fact, that esa stands for > European Space Agency in different European countries (e.g. esa.de, > esa.es, esa.nl) and that therfore it is not wise to register esa.ch > for something completely different. > But they insist on this name. Would you register it? > In cases like this I would give international context precedence > over national context. > I would first contact the European Space Agency to see if they > have any plans to register esa.ch in the (near) future. If they > do, I would give them the "first option" on that domain, but at > the same time I would ask them to register it immediately. This will remain a can of worms, always. Some time ago the "Instituut voor Nederlandse Geschiedenis" (Institute for Dutch History) registered "ing.nl". However, two Dutch banks merged (aroud the same) and became "Internationale Nederlanden Groep"... If you ask somebody in The Netherlands where ING stands for, 99 to 100 he'll say "Internationale Nederlanden Groep". __ Erik-Jan.

2 1

Re: register esa.ch ?
by Piet Beertema 20 May '94

20 May '94

this is a significant departure from FCFS which should not be done lightly. It establishes a precedent to poll all multi-nationals before registering locally. Please note that I'm *not* saying nor implying that this should be done lightly. And I think such cases will hardly show up: lots of commercial multi-nationals are registered in the various countries, so chances are minimal that some other company will be "entitled" to "their" domain name. For other organisations the situation is different; ESA is a clear example of this. And what if somebody would want to register cern.nl? I probably would think twice and contact CERN about it. Also note that these "name clashes" don't occur only on an international scale: on a national scale they occur as well. Under .NL I've had at least one such case. But that doesn't mean I'm going to "poll" or search for all organisations that I might suspect to have a "right" on a name. In other words: it's the exceptions that confirm the rule; in the case of esa.ch I see such an exception. Piet

1 0

register esa.ch ?
by Willi Huber 20 May '94

20 May '94

Dear colleagues, I have got a request from the company "Einkaufsgenossenschaft des Schweizer- ischen Autogewerbeverbands" to register the domain esa.ch. ESA is the registered name of this company that appears also on their letters. I have called their attention to the fact, that esa stands for European Space Agency in different European countries (e.g. esa.de, esa.es, esa.nl ) and that therfore it is not wise to register esa.ch for something completely different. But they insist on this name. Would you register it? Regards, Willi Huber

4 5

Re: register esa.ch ?
by Dave Morton 20 May '94

20 May '94

> > Willi Huber <huber(a)chx400.switch.ch> writes: > > > > But they insist on this name. Would you register it? > >If it is indeed their "local name" and they have been warned about the >conflict I see no reason why not. Daniel - under that argument you wouldn't object either to someone registering RIPE.DE or NL or whatever ? >Daniel I think Piet's approch is the best. Dave

2 1

Re: Root Nameserver
by Erik-Jan Bos 19 May '94

19 May '94

Marten, > rs.internic.net:domain/named.root says: > > ; > ; This file holds the information on root name servers needed to > ; initialize cache of Internet domain name servers > ; (e.g. reference this file in the "cache . <file>" > ; configuration file of BIND domain name servers). > ; > ; This file is made available by InterNIC registration services > ; under anonymous FTP as > ; file /domain/named.root > ; on server FTP.RS.INTERNIC.NET > ; -OR- under Gopher at RS.INTERNIC.NET > ; under menu InterNIC Registration Services (NSI) > ; submenu InterNIC Registration Archives > ; file named.root > ; > ; last update: May 11, 1994 > ; related version of root zone: 940516 > ; > . 99999999 IN NS NS.INTERNIC.NET. > NS.INTERNIC.NET. 99999999 A 198.41.0.4 > . 99999999 NS NS1.ISI.EDU. > NS1.ISI.EDU. 99999999 A 128.9.0.107 > . 99999999 NS C.NYSER.NET. > C.NYSER.NET. 99999999 A 192.33.4.12 > . 99999999 NS TERP.UMD.EDU. > TERP.UMD.EDU. 99999999 A 128.8.10.90 > . 99999999 NS NS.NASA.GOV. > NS.NASA.GOV. 99999999 A 128.102.16.10 > 99999999 A 192.52.195.10 > . 99999999 NS NS.NIC.DDN.MIL. > NS.NIC.DDN.MIL. 99999999 A 192.112.36.4 > . 99999999 NS AOS.ARL.ARMY.MIL. > AOS.ARL.ARMY.MIL. 99999999 A 128.63.4.82 > 99999999 A 192.5.25.82 > . 99999999 NS NIC.NORDU.NET. > NIC.NORDU.NET. 99999999 A 192.36.148.17 > ; End of File Most true, and since I am mirroring this file and have a notifier running the appearance of this new file was sent to me. I, however, never saw a announcement of this. I do not expect that the whole world needs to mirror this file... __ Erik-Jan.

4 5

Root Nameserver
by Arnold Nipper 19 May '94

19 May '94

Does anybody know the correct set of . NS? Since kava.... disappeared a new one (ns1.isi.edu) popped up. Regards, Arnold ; <<>> DiG 2.0 <<>> . ns @c.nyser.net ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10 ;; flags: qr aa rd ra; Ques: 1, Ans: 8, Auth: 0, Addit: 10 ;; QUESTIONS: ;; ., type = NS, class = IN ;; ANSWERS: . 518400 NS NS.INTERNIC.NET. . 518400 NS AOS.ARL.ARMY.MIL. . 518400 NS NS1.ISI.EDU. . 518400 NS C.NYSER.NET. . 518400 NS TERP.UMD.EDU. . 518400 NS NS.NASA.GOV. . 518400 NS NIC.NORDU.NET. . 518400 NS NS.NIC.DDN.MIL. ;; ADDITIONAL RECORDS: NS.INTERNIC.NET. 518400 A 198.41.0.4 AOS.ARL.ARMY.MIL. 518400 A 128.63.4.82 AOS.ARL.ARMY.MIL. 518400 A 192.5.25.82 NS1.ISI.EDU. 518400 A 128.9.0.107 C.NYSER.NET. 518400 A 192.33.4.12 TERP.UMD.EDU. 518400 A 128.8.10.90 NS.NASA.GOV. 518400 A 128.102.16.10 NS.NASA.GOV. 518400 A 192.52.195.10 NIC.NORDU.NET. 518400 A 192.36.148.17 NS.NIC.DDN.MIL. 518400 A 192.112.36.4 ;; Total query time: 3072 msec ;; FROM: xlink103 to SERVER: c.nyser.net 192.33.4.12 ;; WHEN: Thu May 19 14:28:43 1994 ;; MSG SIZE sent: 17 rcvd: 393

3 2

RIPE DB domain object
by Francis Dupont 17 May '94

17 May '94

Here are proposals about the RIPE DB domain object definition Francis.Dupont(a)inria.fr Some mandatory entries should become optional (i.e. can be missing): - zone-c (zone contact(s)) when the domain is not a zone (technically: it has no SOA RR), for instance MX only domains have no zone contacts. - nserver (name servers) is in the same case - sub-dom (sub domain(s)) when there is no sub domains Some important entries should be redefined: - nserver (name servers): the new syntax should be: (*) name [ (address)+ ] with a star for unpublished (secondary) name servers, fully qualified domain name of the name server and the list of the IP addresses of the name server. We have to write a detailed description of this, for instance what are the mandatory fields, what are unpublished ns, ... - sub-dom (sub domains): this entry should be either not present or not empty. Domain names should be fully qualified (change). New entries like the "notify" entry must be added (it is in the scope of of RIPE DB WG but we have to produce an up to date document about domain object)

3 4

BIND status
by Francis Dupont 13 May '94

13 May '94

Here is the current BIND software status with IPng support. Francis.Dupont(a)inria.fr The last experimental release is BIND 4.9.3 alpha4 (join the mailing list bind-workers(a)vix.com if you want to use/debug it). The last official release is BIND 4.9.2 and final distrib can be found in gatekeeper.dec.com:[~ftp/]pub/misc/vixie/4.9.2-940221.tar.{Z,gz} and on several anonymous FTP servers. Known problems are negative caching and validating then switch OFF the options NCACHE and VALIDATE. Another problem is resolver library security with SunOS, use the SUNSECURITY switch. SIPP support has been done by Susan Thomson <set(a)thumper.bellcore.com> and can be found in thumper.bellcore.com:[~ftp/]pub/pip/code/dns/feb94.tar.Z NSAP support has been done by Paul Traina <pst(a)cisco.com> and can be found in ftp.cisco.com:[~ftp/]bind/4.9.2-beta5-nsap-diffs NSAP support for nslookup (i.e. easy way to find PTR for NSAP addresses) has been done by Richard Colella <colella(a)nist.gov> and is in osi.ncsl.nist.gov:[~ftp/]pub/ncsa_tuba/nslook_rev_nsap.tar (note: the reverse map root is nsap.int)

1 0

DNS WG at the 18th RIPE meeting
by Francis Dupont 11 May '94

11 May '94

Here is the final draft agenda for the DNS WG meeting : First we have open actions: - prepare workplan and charter for the group - review the Domain object for RIPE DB and some "follow-up" items: - BIND software news - DNS security last I propose to discuss the "Taking Care of Your Domain" document from Arthur Romao. I believe we need 1.5 hour Thanks Francis.Dupont(a)inria.fr PS: I'll send domain object proposal and BIND news to the dns-wg list. PS (to NCC staff): can you prepare paper copies of Arthur Romao's paper ?

1 0