From root at jimex.jinr.dubna.su Mon Oct 4 16:21:11 1993 From: root at jimex.jinr.dubna.su (Operator) Date: Mon, 4 Oct 93 16:21:11 MSK Subject: DNS form for JINR Message-ID: <9310041321.AA04494@jimex.jinr.dubna.su> 1. Top-level domain: su 2. Complete Domain Name: jinr.dubna.su 3a. Organization name: Joint Institute for Nuclear Research 3b. Organization address: P.O.Box 79 10100 Moscow 4. Date operational: 1-10-1993 Administrative Contact 5a. NIC Handle (if known) : VS86 5b. Name (Last, First) : Vladislav Shirikov 5c. Organization: Joint Institute for Nuclear Research 5d. Mail Address: shirikov at jinr.dubna.su 5e. Phone Number: Dubna (221) 62387 5f. Net Mailbox : Technical and Zone Contact 6a. NIC Handle (if known): 6b. Name (Last, First) : Evgeny Mazepa 6c. Organization: Joint Institute for Nuclear Research 6d. Mail Address: mazepa at jinr.dubna.su 6e. Phone Number: Dubna (221) 65020 6f. Net Mailbox : Primary Server: HOSTNAME, NETADDRESS, HARDWARE, SOFTWARE 7a. Primary Server Hostname: 1: ns.jinr.dubna.su (jimex.jinr.dubna.su) 2: ns.kiae.su 3: ns.ussr.eu.net 7b. Primary Server Netaddress: 1: 159.93.17.7 2: 144.206.130.3 3: 192.16.202.11 7c. Primary Server Hardware: 1: SUN SPARCstation 1+ 2: 3: 7d. Primary Server Software: 1: Sun/OS 4.1.1 2: 3: (8) The Secondary server information. 8a. Secondary Server Hostname: 1: ns.kiae.su 2: ns.ussr.eu.net 8b. Secondary Server Netaddress: 1: 144.206.130.3 2: 192.16.202.11 8c. Secondary Server Hardware: 1: 2: 8d. Secondary Server Software: 1: 2: (9) If any currently registered hosts will be renamed into the new domain, please specify old hostname, netaddress, and new hostname. (10) Please describe your organization briefly. Nuclear research From Daniel.Karrenberg at ripe.net Tue Oct 5 11:01:05 1993 From: Daniel.Karrenberg at ripe.net (Daniel Karrenberg) Date: Tue, 05 Oct 1993 11:01:05 +0100 Subject: DNS form for JINR In-Reply-To: Your message of Mon, 04 Oct 1993 16:21:11 -1000. <9310041321.AA04494@jimex.jinr.dubna.su> Message-ID: <9310051001.AA16758@ncc.ripe.net> Vladislav, Evgeny, you have just sent your message to about 50 people of the RIPE DNS working group. This is not the right address for registering sub-domains of dubna.su. The correct address is . If you have any problems getting your subdomain registered, please do not hesitate to contact ncc at ripe.net for assistance. Daniel Karrenberg RIPE NCC Manager > root at jimex.jinr.dubna.su (Operator) writes: > > 1. Top-level domain: su > > 2. Complete Domain Name: jinr.dubna.su > > 3a. Organization name: Joint Institute for Nuclear Research > ... From hh at tip.net Wed Oct 13 15:26:57 1993 From: hh at tip.net (Hakan Hansson) Date: Wed, 13 Oct 1993 15:26:57 +0100 Subject: MX in IN-ADDR.ARPA domains? Message-ID: <9310131427.AA12503@netman.tip.net> Hi there, Now we have delegation of the IN-ADDR.ARPA domains from the root servers, similar to the delegation of the 'ordinary' domains. Before this happened there were only one single registry that handled all the reverse NS delegations, former . This was easy to understand. Yesterday I spent some time trying to explain for one of our customers how the registration currently works. Well, you know the story.... Then I come to think of: Why couldn't he send a request to hostmaster at 44.193.in-addr.arpa? The information about the hostmaster of each domain is of course already viewable in the zone files, but wouldn't it be more user-fiendly to be able to address the hostmaster of the IN-ADDR domain directly? Maybe this way of using IN-ADDR.ARPA isn't approved in applicable RFC's (I haven't checked)? Regards, Hakan Hansson == Unisource Business Networks Sweden == Unidata IP Services * TIPnet NMC * Gothenburg == phone +46-31-7708072 * fax +46-31-114664 *** Aktiv medlem i '8:e bit:ens vdnner' *** From Daniel.Karrenberg at ripe.net Wed Oct 13 16:41:23 1993 From: Daniel.Karrenberg at ripe.net (Daniel Karrenberg) Date: Wed, 13 Oct 1993 16:41:23 +0100 Subject: MX in IN-ADDR.ARPA domains? In-Reply-To: Your message of Wed, 13 Oct 1993 15:26:57 MET. <9310131427.AA12503@netman.tip.net> Message-ID: <9310131541.AA15770@ncc.ripe.net> > hh at tip.net (Hakan Hansson) writes: > Hi there, > > Then I come to think of: > Why couldn't he send a request to hostmaster at 44.193.in-addr.arpa? The main problem would be that not even all sevice providers will get their mail systems to recognise hostmaster at 44.193.in-addr.arpa as local mail! Daniel From hh at tip.net Wed Oct 13 16:52:47 1993 From: hh at tip.net (Hakan Hansson) Date: Wed, 13 Oct 1993 16:52:47 +0100 Subject: MX in IN-ADDR.ARPA domains? Message-ID: <9310131553.AA12856@netman.tip.net> At 04:41 PM 10/13/93 +0100, Daniel Karrenberg wrote: > > > hh at tip.net (Hakan Hansson) writes: > > Hi there, > > > > Then I come to think of: > > Why couldn't he send a request to hostmaster at 44.193.in-addr.arpa? > >The main problem would be that not even all sevice providers >will get their mail systems to recognise hostmaster at 44.193.in-addr.arpa >as local mail! > >Daniel > Well, I have only experience from sendmail, and there it is possible to configure multiple mail-domains for incoming mail. Do you mean that this does no apply for all mail softwares? If so, then I agree that this was a bad idea.... /Hakan From Daniel.Karrenberg at ripe.net Wed Oct 13 16:55:48 1993 From: Daniel.Karrenberg at ripe.net (Daniel Karrenberg) Date: Wed, 13 Oct 1993 16:55:48 +0100 Subject: MX in IN-ADDR.ARPA domains? In-Reply-To: Your message of Wed, 13 Oct 1993 16:52:47 MET. <9310131553.AA12856@netman.tip.net> Message-ID: <9310131555.AA15854@ncc.ripe.net> > hh at tip.net (Hakan Hansson) writes: > > Well, I have only experience from sendmail, and there it is possible to > configure multiple mail-domains for incoming mail. Do you mean that this > does no apply for all mail softwares? If so, then I agree that this was a > bad idea.... Even with sendmail this depends on what your sendmail.cf looks like and how well you can debug sendmail. Daniel From hh at tip.net Wed Oct 13 17:03:00 1993 From: hh at tip.net (Hakan Hansson) Date: Wed, 13 Oct 1993 17:03:00 +0100 Subject: MX in IN-ADDR.ARPA domains? Message-ID: <9310131603.AA12906@netman.tip.net> At 04:55 PM 10/13/93 +0100, Daniel Karrenberg wrote: > > > hh at tip.net (Hakan Hansson) writes: > > > > Well, I have only experience from sendmail, and there it is possible to > > configure multiple mail-domains for incoming mail. Do you mean that this > > does no apply for all mail softwares? If so, then I agree that this was a > > bad idea.... > >Even with sendmail this depends on what your sendmail.cf >looks like and how well you can debug sendmail. > >Daniel > > I don't think it is hard to do that, just do like this: Cmubn.net Cmse.ubn.net Cmtip.net Cmtipnet.se Cmsti.se Cm44.193.in-addr.arpa /Hakan From Daniel.Karrenberg at ripe.net Wed Oct 13 17:06:35 1993 From: Daniel.Karrenberg at ripe.net (Daniel Karrenberg) Date: Wed, 13 Oct 1993 17:06:35 +0100 Subject: MX in IN-ADDR.ARPA domains? In-Reply-To: Your message of Wed, 13 Oct 1993 17:03:00 MET. <9310131603.AA12906@netman.tip.net> Message-ID: <9310131606.AA15932@ncc.ripe.net> > hh at tip.net (Hakan Hansson) writes: > > I don't think it is hard to do that, just do like this: > > Cmubn.net > Cmse.ubn.net > Cmtip.net > Cmtipnet.se > Cmsti.se > Cm44.193.in-addr.arpa Fine. WIth *Your* paricaular configuration: sendmail and your sendmail.cf. I still postulate it will give some SPs quite some problems.