Re: Use of RIPE DNS registration form
Havard Eidnes <Havard.Eidnes@runit.sintef.no> writes: * Hi, * * a question has recently arisen concerning the use of the RIPE form for * registering DNS domains in relation to registering names which only have MX * records associated with themselves. In this case, several of the mandatory * fields defined in the RIPE document ripe-49. In particular, we wonder what * we should do about these fields: Questions have been raised before. I have put in some comments given by people: * zone-c: * Should be zone contact of closest parent domain with a separate SOA * record? Why duplicate the information? According to some the zone-c for the closest SOA should be mentioned here. Other suggest that for MX only domains have no zone-c. * nserver: * Same as above? Each domain has a nserver, even an MX only domain. The MX records must be somewhere. This domain has no SOA though. * sub-dom: * Is it really necessary to list the sub-names in use (this also goes * for the general case, but also for the MX-only case) If you wish so. Most people do. Last meeting the DNS working group decided that the first level of useful domain names should be stored in the database, below that is for your own choice. You van in this way restrict the number of objects you have. Most useful level is usually 2, 3 in cases where co, ac and other second level domains are used: Useful: nikhef.nl ulcc.ac.uk ... Database and DNS working group, what say you ? -Marten
Questions have been raised before. I have put in some comments given by people:
* zone-c: * Should be zone contact of closest parent domain with a separate SOA * record? Why duplicate the information?
According to some the zone-c for the closest SOA should be mentioned here. Other suggest that for MX only domains have no zone-c.
Since the MX-only domain is not a zone, there is really no need for a zone-c.
* nserver: * Same as above?
Each domain has a nserver, even an MX only domain. The MX records must be somewhere. This domain has no SOA though.
Same as above -- only zones have name servers, and MX-only domains do not have "name servers" of their own, they live in the parent zone. Thus, this will be duplication of information, and will be harder to maintain consistently whenever anything changes in the name server list of the parent zone.
* sub-dom: * Is it really necessary to list the sub-names in use (this also goes * for the general case, but also for the MX-only case)
If you wish so. Most people do.
Ouch! This is also duplication of information. If you are interested in all domains under a given top-level country domain registered in the RIPE database, you can perform this search by transferring the RIPE database and doing "agrep" on it, no? Or, if people insist that this information should be contained in a single object in the RIPE database, the list of subdomains of a domain could be automatically generated by the RIPE database software (more work for the database software hackers, I know...) - Havard
Havard Eidnes <Havard.Eidnes@runit.sintef.no> writes: * > * sub-dom: * > * Is it really necessary to list the sub-names in use (this also * goes * > * for the general case, but also for the MX-only case) * > * > If you wish so. Most people do. * * Ouch! This is also duplication of information. If you are interested in * all domains under a given top-level country domain registered in the RIPE * database, you can perform this search by transferring the RIPE database and * doing "agrep" on it, no? Or, if people insist that this information should * be contained in a single object in the RIPE database, the list of * subdomains of a domain could be automatically generated by the RIPE * database software (more work for the database software hackers, I know...) For top-level domain administrators it is not much work is it ? With all other administrativia it should be easy to update the top-level domain as well as the domain itself. I assume that a top-level domain administrator is the person that should send in domain entries for a top-level. Since he has to keep all objects himself, it cannot be very difficult to make a little tool to automatically generate the top-level domain. If you want us to make the tool, I'd be happy to ;-) I kind of like it to do the thing below, and not having to "agrep" through the complete database. -Marten % whois nl domain: nl descr: Top level domain for the Netherlands descr: c/o CWI, Kruislaan 413, NL 1098 SJ Amsterdam admin-c: P.C. Baayen tech-c: Piet Beertema zone-c: Daniel Karrenberg nserver: sering.cwi.nl mcsun.eu.net sunic.sunet.se nserver: brouilly.inria.fr ns.uu.net aos.brl.mil sub-dom: 400net sub-dom: aasup abd ace agro agrobtc aha ahold aie akam alliant amolf and sub-dom: antenna archis artmediatech ascad ashton-tate asml asser atcmp sub-dom: audacter azn azr sub-dom: baan baltzer bazis bimbv bmc borsu brinkman bso bssi bull sub-dom: can cbm cbs cbsc ccsom chess chw cipher comcons compunication comtecno sub-dom: consul convex cpb cpu cri ctg cti-software cwi sub-dom: dasc dataman dcmr delftgeot delgeo dg digicash digitalis diho dobdh sub-dom: dupaco sub-dom: ecn eim elsevier encore esa eur sub-dom: fokker fom force5 fourc fousupp foxim frame franciscus sub-dom: gbsp gbu getronics geveke ghbo gig gli gobe group gti-ia sub-dom: hacktic harris hbg hbo-raad hcsvt hen hes-rdam hhg hhs hivnet sub-dom: hkl hku hmb hny hobby hro hsa hsbos hsdehorst hse hut hwb hzeeland sub-dom: iaf iahl iamcr ibmx400 ice icgned icim icin icl icodo ict idg ifla sub-dom: ihe impact inducom ingres integrity ioo irdeto isc island ita itc sub-dom: ittpub ixonet sub-dom: jason jrc sub-dom: kap kema khzeist kim kitlv knaw-bibl kncv knmi koha konbib ksepl sub-dom: ksla ktibv kub kun kvi sub-dom: leidenuniv li logos sub-dom: marin meteocon mey mh minow mmph motorola mpi sub-dom: nacee nbd nblc nboi ncs neabbs neddata nedlloyd neogeo nfra nhl nhtv sub-dom: nias nidi nih nijenrode nikhef nimex niob nioz nki nlbb nlbc nlr nluug sub-dom: nmi nota nrv ns nuclint nucphys nwo sub-dom: oba obdov obr obtilburg oce oceonics olivetti open-i oracle origin ouh sub-dom: pact parcom pbf pecoma pggm philips pica positronika prismia propell sub-dom: prvnh psyline ptt pttnwb pttrnl sub-dom: q8 sub-dom: rabo radix raet rare rcc-ivev rdm repko rgd rhg rhij rigo rijnh riks sub-dom: rivm rodelco rtm rug rulimburg ruu rvb rws sub-dom: sagan sara scp serc sgi sierra signaal skferc source spc spex stam stc sub-dom: stegge stork stw suaa sun surfbureau surfdiensten surfnet suub svo swets sub-dom: swidoc swov syllogic sub-dom: tasking technolution term1 thijssen thu-k tmu tno tpsc transfer sub-dom: translogic trc trendbox tudelft tue txbase sub-dom: uniface unisys univforhuman usn utwente uva sub-dom: valkieser vdl vdvalk vimec vmx vsnu vu sub-dom: wau west wkap wldelft wlink wmt wsf sub-dom: xelion xirion sub-dom: y-net yaupon remarks: fully-managed changed: piet@cwi.nl 930303 source: RIPE
I kind of like it to do the thing below, and not having to "agrep" through the complete database.
-Marten
% whois nl
Of course, it is good example, but it seems that NL domain is more exception than rule. Other domains are usually described very poor. -- Algirdas
participants (3)
-
Dr Algirdas Pakstas -
Havard Eidnes -
Marten Terpstra