- db-wg - mailman.ripe.net

Novel NetMail users
by Denis Walker 10 Nov '03

10 Nov '03

Dear Colleagues, In the process of testing mail clients for s/mime compatibility I am trying to install Novell NetMail on our linux test box running RedHat 8.0. I have no previous knowledge at all about this product. I have tried several times to install it and can never get past a window asking for the Administrator user name and password. I have included the log of what I did below. Any help from users of this mail client would be very much appreciated. Regards Denis Walker RIPE NCC Software Engineering Department. [root@linux setup]# ./nds-install %% Welcome to the installation of Novell eDirectory 8.7.0 %% The Novell eDirectory (8.7.0) for Linux End User License Agreement will now be displayed. %% Please read the agreement carefully before accepting the terms. %% Press ENTER to continue. %% Do you accept the terms of the Novell eDirectory (8.7.0) license agreement '[y/n/q] ? 'y %% List of Novell eDirectory (8.7.0) components available to install %% 1 Novell eDirectory Server %% 2 Novell eDirectory Administration Utilities %% 3 Management Console for Novell eDirectory (ConsoleOne) %% Select the components you wish to install [?, q] : 1,2,3 %% Enter the path to License File (.nfk): /var %% License file Copied. %% Adding packages... Preparing... ########################################### [100%] 1:NDSmasv ########################################### [100%] Preparing... ########################################### [100%] 1:NDSbase ########################################### [100%] Preparing... ########################################### [100%] 1:NLDAPsdk ########################################### [100%] Preparing... ########################################### [100%] 1:NLDAPbase ########################################### [100%] Preparing... ########################################### [100%] 1:NDScommon ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLpkis ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLpkia ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLpkit ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLsas ########################################### [100%] Preparing... ########################################### [100%] 1:ntls ########################################### [100%] Preparing... ########################################### [100%] 1:NDSserv ########################################### [100%] Preparing... ########################################### [100%] 1:NDSrepair ########################################### [100%] Preparing... ########################################### [100%] 1:NDSimon ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLsnmp ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLsubag ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLnmas ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLembox ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLlmgnt ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLstlog ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLxis ########################################### [100%] Preparing... ########################################### [100%] 1:NOVLice ########################################### [100%] Preparing... ########################################### [100%] 1:NDSdxevnt ########################################### [100%] %% Installing ConsoleOne.... The following is a list of languages that are available to install. 1 English 2 French 3 All Select the languages you wish to install [?,q]: 1 The following are all the available snapins you can choose to install 0 NONE 1 ICE Snapin 2 Index Manager Snapin 3 LDAP Snapin 4 SLP Snapin 5 WAN Manager Snapin 6 PKI Snapin 7 Filtered Replica Snapin 8 All Select the snapin(s) you wish to install [?,q]: 8 Do you wish to install Java Runtime Environment [y,n,q] ? y OpenSLP rpm " openslp-1.0.11-0.fdr.6.rh80 " is already installed. NDSslp will not be installed. %% Adding package IBMJava2-JRE ... Preparing... ########################################### [100%] 1:IBMJava2-JRE ########################################### [100%] %% NDSbase package is already installed. %% NDScommon package is already installed. %% NLDAPsdk package is already installed. %% NLDAPbase package is already installed. %% NOVLxis package is already installed. %% NOVLlmgnt package is already installed. %% NOVLice package is already installed. %% NOVLsas package is already installed. %% NOVLpkia package is already installed. %% NOVLpkis package is already installed. %% Adding package NOVLc1 ... error: Failed dependencies: NDSslp is needed by NOVLc1-1.3.4-1 %% ERROR: Failed to add NOVLc1 (NOVLc1) package. %% Installation of packages failed, not all packages were installed. ucd-snmp package is not installed on your system. Please ensure that you install this package before using any SNMP related features of Novell eDirectory (8.7.0) . Please refer to the admin_guide.pdf for more details. %% Novell eDirectory Server packages successfully installed. %% Novell eDirectory Administration Utilities packages successfully installed. %% Use "ndsconfig" to configure Novell eDirectory Server. %% Please update following environment variables to use LDAP tools from Novell - PATH=/usr/ldaptools/bin:$PATH MANPATH=/usr/ldaptools/man:$MANPATH %% Please go through ../readme.txt carefully before using the product. [root@linux setup]# [root@linux setup]# rpm -i /home/test-receiver/novel/Linux/ConsoleOne/NDSslp-8. 7.0-1.i386.rpm Starting NDS SLP services... Done [root@linux setup]# ./nds-install %% Welcome to the installation of Novell eDirectory 8.7.0 %% The Novell eDirectory (8.7.0) for Linux End User License Agreement will now be displayed. %% Please read the agreement carefully before accepting the terms. %% Press ENTER to continue. %% Do you accept the terms of the Novell eDirectory (8.7.0) license agreement '[y/n/q] ? 'y %% List of Novell eDirectory (8.7.0) components available to install %% 1 Novell eDirectory Server %% 2 Novell eDirectory Administration Utilities %% 3 Management Console for Novell eDirectory (ConsoleOne) %% Select the components you wish to install [?, q] : 1,2,3 %% Enter the path to License File (.nfk): /var %% License file Copied. %% Adding packages... NDSmasv is already installed NDSbase is already installed NLDAPsdk is already installed NLDAPbase is already installed NDScommon is already installed NOVLpkis is already installed NOVLpkia is already installed NOVLpkit is already installed NOVLsas is already installed ntls is already installed NDSserv is already installed NDSrepair is already installed NDSimon is already installed NOVLsnmp is already installed NOVLsubag is already installed NOVLnmas is already installed NOVLembox is already installed NOVLlmgnt is already installed NOVLstlog is already installed NOVLxis is already installed NOVLice is already installed NDSdxevnt is already installed %% Installing ConsoleOne.... The following is a list of languages that are available to install. 1 English 2 French 3 All Select the languages you wish to install [?,q]: 1 The following are all the available snapins you can choose to install 0 NONE 1 ICE Snapin 2 Index Manager Snapin 3 LDAP Snapin 4 SLP Snapin 5 WAN Manager Snapin 6 PKI Snapin 7 Filtered Replica Snapin 8 All Select the snapin(s) you wish to install [?,q]: 8 OpenSLP rpm " openslp-1.0.11-0.fdr.6.rh80 " is already installed. NDSslp will not be installed. %% NDSbase package is already installed. %% NDScommon package is already installed. %% NLDAPsdk package is already installed. %% NLDAPbase package is already installed. %% NOVLxis package is already installed. %% NOVLlmgnt package is already installed. %% NOVLice package is already installed. %% NOVLsas package is already installed. %% NOVLpkia package is already installed. %% NOVLpkis package is already installed. %% Adding package NOVLc1 ... Preparing... ########################################### [100%] 1:NOVLc1 ########################################### [100%] %% Adding package NDSsice ... Preparing... ########################################### [100%] 1:NDSsice ########################################### [100%] %% Adding package NDSsimgr ... Preparing... ########################################### [100%] 1:NDSsimgr ########################################### [100%] %% Adding package NDSsldap ... Preparing... ########################################### [100%] 1:NDSsldap ########################################### [100%] %% Adding package NDSsslp ... Preparing... ########################################### [100%] 1:NDSsslp ########################################### [100%] %% Adding package NDSswan ... Preparing... ########################################### [100%] 1:NDSswan ########################################### [100%] %% Adding package NDSspki ... Preparing... ########################################### [100%] 1:NDSspki ########################################### [100%] %% Adding package NDSsfrep ... Preparing... ########################################### [100%] 1:NDSsfrep ########################################### [100%] %% ConsoleOne Successfully Installed. %% Execute /usr/ConsoleOne/bin/ConsoleOne to run ConsoleOne %% Snapins Successfully Installed. ucd-snmp package is not installed on your system. Please ensure that you install this package before using any SNMP related features of Novell eDirectory (8.7.0) . Please refer to the admin_guide.pdf for more details. %% Novell eDirectory Server packages successfully installed. %% Novell eDirectory Administration Utilities packages successfully installed. %% Use "ndsconfig" to configure Novell eDirectory Server. %% Please update following environment variables to use LDAP tools from Novell - PATH=/usr/ldaptools/bin:$PATH MANPATH=/usr/ldaptools/man:$MANPATH %% Please go through ../readme.txt carefully before using the product. [root@linux setup]# ndsconfig new -t DW_TREE -o 80 -O 443 -a admin.DW Enter the password for admin.DW: Re-enter the password for admin.DW: Enter server context[org]:dw Starting the service 'ndsd'... Done. Configuring eDirectory with following parameters Admin name = admin.DW Tree name = DW_TREE Server Context = dw dibdir path = /var/nds/dib Searching for Duplicate Tree Name in the network. Please wait... Installing Novell eDirectory Server ... Novell eDirectory Server successfully installed on this system. Extending schema... For more details view schema extension logfile: /var/nds/schema.log Schema extended successfully. Configuring SAS service ... Successfully configured SAS service Nov 10 16:56:22 Could not set the preferred server LINUX Configuring LDAP Server with default SSL CertificateDNS certificate Done Restarting ndsd to load the tree key Stopping the service 'ndsd'... Done. Starting the service 'ndsd'... Done. [root@linux setup]# ps -ef | grep ndsd root 27255 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27257 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27258 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27259 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27260 1 9 16:53 ? 00:00:30 /usr/sbin/ndsd root 27261 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27262 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27263 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27264 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27265 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27266 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27267 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27268 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27269 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27270 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27272 1 10 16:53 ? 00:00:32 /usr/sbin/ndsd root 27273 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27275 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27277 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27278 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27279 1 0 16:53 ? 00:00:00 /usr/sbin/ndsd root 27314 1 0 16:54 ? 00:00:00 /usr/sbin/ndsd root 27315 1 0 16:54 ? 00:00:00 /usr/sbin/ndsd root 27430 7667 0 16:58 pts/0 00:00:00 grep ndsd [root@linux novel]# ./pinstall.lin To accept this license agreement, please enter 'Y': y Pervasive not found. Installing it now! Pervasive SQL server 2000 installed. Now installing NetMail 3.1. Please wait while nimsext loads Nov 10 17:04:39 Could not set the preferred server LINUX At this point it asks me to: ************************************************************** Login as the administrator Administrator name: Password: ************************************************************** I enter the user name admin.DW and password that I thought I had set up with the ndsconfig and I get ************************************************************** Login failed, try again? -Yes No ************************************************************** I do not have any other user name and password for an administrator. I tried entering the root password for the linux system and that did not work either. If I select No then it goes into a loop as below and I have to kill it. Assigning Pervasive rights Your installation is now complete. Thank you for using NetMail 3.1! The NetMail team. Starting NetMail Starting NetMail: [root@linux novel]# Nov 10 17:12:56 Could not set the preferred server LINUX DDB: Logged in with 'Public' identity. Functionality may be limited. (This message is OK if the schema has not been extended yet) [root@linux novel]# No agents configured Module rBåÿ¿sZBrB¬åÿ¿Äq(@Pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ @ died. Restarting. Starting: rbåÿ¿szbrb¬åÿ¿Äq(@pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ @ Load Error: No such file or directory Module rbåÿ¿szbrb¬åÿ¿Äq(@pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ @ did not load Module rbåÿ¿szbrb¬åÿ¿Äq(@pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ @ did not load Module rbåÿ¿szbrb¬åÿ¿Äq(@pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ @ did not load Module rbåÿ¿szbrb¬åÿ¿Äq(@pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ @ did not load Module rbåÿ¿szbrb¬åÿ¿Äq(@pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ @ did not load Module rbåÿ¿szbrb¬åÿ¿Äq(@pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ @ did not load Module rbåÿ¿szbrb¬åÿ¿Äq(@pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ @ did not load Module rbåÿ¿szbrb¬åÿ¿Äq(@pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ @ did not load Module rbåÿ¿szbrb¬åÿ¿Äq(@pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ @ did not load Module rbåÿ¿szbrb¬åÿ¿Äq(@pæÿ¿ýÿÿÌåÿ¿"q'@ýÿÿÜåÿ¿oq'@lÞ @ýÿÿ æÿ¿oq'@lÞ [test-receiver@linux init.d]$ ps -ef | grep ims root 27799 1 0 17:13 ? 00:00:00 /usr/local/nims/bin/ims kill -9 27799

1 0

Should the "e-mail" attribute be mandatory for the "person" object?
by Thor Kottelin 07 Nov '03

07 Nov '03

Folks, Email is the preferred communication medium when troubleshooting internetworking problems. Time and time again, "inetnum" objects with no valid email address cause grief. In the absence of relevant "e-mail" attributes, desperate administrators sometimes send mail to addresses found in "changed" and "notify" attributes. Sometimes the only option left is resorting to telephone calls, regardless of the expenses, time differences and language barriers often involved. I would therefore like to suggest making the "e-mail" attribute mandatory for the "person" object. If this isn't acceptable, then maybe at least one of the "person" or "role" objects referred to by an "inetnum" object should carry an "e-mail" attribute. Additionally, in order to enhance address validity, I would like to suggest performing some kind of validation on these "e-mail" attribute values - perhaps simple syntax checking, or maybe even full round-trip SMTP testing, or something in between. Your comments, please. Thor -- http://thorweb.anta.net/

5 7

Maintenance on RIPE Whois Server, 10 November 2003
by DB-News 07 Nov '03

07 Nov '03

Dear Colleagues, [apologies for duplicate messages] Next Monday, 10 November 2003, we need to perform a maintenance work on the RIPE Whois Server to replace a faulty piece of hardware. During the maintenance work, - Whois Database updates will be stopped, - all update mails to <auto-dbm(a)ripe.net> will be queued to be processed later, - Webupdate and syncupdate interfaces will be unavailable, - The whois queries will _not_ be interrupted. The maintenance work will start at 12:00 UTC (13:00 Amsterdam time) on 10 November 2003 and expected to last 2 to 3 hours. We apologise for the convenience caused. Please do not hesitate to contact <ripe-dbm(a)ripe.net> for any questions. Best regards, -- Engin Gunduz RIPE NCC

1 0

RE: [db-wg] Should the "e-mail" attribute be mandatory for the "p erson" object?
by Titley, Nigel 03 Nov '03

03 Nov '03

Thor Kottelin wrote: > Folks, > > Email is the preferred communication medium when troubleshooting > internetworking problems. Time and time again, "inetnum" > objects with no > valid email address cause grief. In the absence of relevant "e-mail" > attributes, desperate administrators sometimes send mail to > addresses found > in "changed" and "notify" attributes. Sometimes the only > option left is > resorting to telephone calls, regardless of the expenses, > time differences > and language barriers often involved. The argument against making the email attribute mandatory has always been the bootstrapping problem... In the olden days (defined by my children as "when Daddy was young") it was genuinely possible for a person in the RIPE database to not actually have an email address during the setting up phase of a LIR. I would however agree with Thor, that this circumstance no longer exists. Anyone can get a temporary email address, hotmail via the local cybercafe, if nothing else, to tide them over the bootstrapping period. > > I would therefore like to suggest making the "e-mail" > attribute mandatory > for the "person" object. If this isn't acceptable, then maybe > at least one > of the "person" or "role" objects referred to by an "inetnum" > object should > carry an "e-mail" attribute. Additionally, in order to enhance address > validity, I would like to suggest performing some kind of > validation on > these "e-mail" attribute values - perhaps simple syntax > checking, or maybe > even full round-trip SMTP testing, or something in between. > > Your comments, please. > > Thor ********************************************************************** This e-mail message is confidential and is intended only for the use of the individual or entity named above and contains information which is or may be confidential, non-public or legally privileged. Any dissemination or distribution of this message other than to its intended recipient is strictly prohibited. If you have received this message in error, please notify us by email to postmaster(a)flagtelecom.com immediately and delete the original message and all copies from all locations in your computer systems. This e-mail has been swept by Mailsweeper TM for viruses. However, FLAG Telecom cannot accept liability for any damage which you may sustain as a result of software viruses. **********************************************************************

1 0

Change of Country entries in the database
by Christoph Mohr 23 Oct '03

23 Oct '03

Dear colleagues of the RIPE NCC database group! I'm using the RIPE whois database in its bulk version ripe.db.inetnum for statistical uses while evaluating the netflow data of our border routers. What I'm much interested in is the origin of an IP address which I get by the country entry of the respective inetnum block of the database. Therefore, I'm always a bit confused about the many addresses which are located in the Netherlands. Since I prefer large inetnum blocks for reasons of performance of my software, I often use entries of many C blocks which are registered for the RIPE NCC with the country entry NL. In the meantime, I already corrected the country entries of some inetnums in my own local copy of the database but this is just a workaround which isn't really satisfying. So I would like to suggest the change of the country entry of - at least - the following inetnum blocks (only inetnum, netname and country entries): inetnum: 0.0.0.0 - 255.255.255.255 netname: IANA-BLK country: NL proposed country: EU # Country is really world wide inetnum: 10.0.0.0 - 10.255.255.255 netname: IANA-ABLK-RESERVED1 country: NL proposed country: EU # Country is really world wide inetnum: 145.224.0.0 - 145.254.255.255 netname: RIPE-NCC-145 country: NL proposed country: EU # Country is really world wide inetnum: 145.0.0.0 - 145.127.255.255 netname: RIPE-NL country: NL proposed country: EU inetnum: 147.233.0.0 - 147.237.255.255 netname: RIPE-ISRAELB-NET country: NL proposed country: EU [or IL] inetnum: 149.132.0.0 - 149.134.255.255 netname: RIPE-149-BLK country: NL proposed country: EU inetnum: 149.202.0.0 - 149.204.255.255 netname: RIPE-149-202-BLK country: NL proposed country: EU inetnum: 149.221.0.0 - 149.250.255.255 netname: EU-ZZ-990225 country: NL proposed country: DE inetnum: 149.206.0.0 - 149.251.255.255 netname: RIPE-149-206-BLK country: NL proposed country: EU inetnum: 163.156.0.0 - 163.175.255.255 netname: NETBLK-RIPE-B country: NL proposed country: EU inetnum: 164.128.0.0 - 164.143.255.255 netname: NETBLK-RIPE-B-128 country: NL proposed country: EU inetnum: 164.0.0.0 - 164.40.255.255 netname: RIPE-164-BLK country: NL proposed country: EU inetnum: 172.16.0.0 - 172.31.255.255 netname: IANA-BBLK-RESERVED1 country: NL proposed country: EU # Country is really world wide inetnum: 192.168.0.0 - 192.168.255.255 netname: IANA-CBLK-RESERVED1 country: NL proposed country: EU # Country is really world wide With the entry 'EU # Country is really world wide' I'm referring to an invention of the RIPE NCC due to the ERX project. You created in 2003 the following inetnums: inetnum: 141.0.0.0 - 141.255.255.255 netname: EU-ZZ-141 country: EU # Country is really world wide inetnum: 151.0.0.0 - 151.255.255.255 netname: EU-ZZ-151 country: EU # Country is really world wide inetnum: 188.0.0.0 - 188.255.255.255 netname: EU-ZZ-188 country: EU # Country is really world wide Better would be nevertheless the creation of let's say 'ZZ' or 'WW' for worldwide use, but if you put in exactly 'EU # Country is really world wide', this will be easily been parsed by Perl. I think that this is a good solution, since it doesn't make sense to put in NL for the whole IPv4 address space for example or for let's say RIPE-ISRAELB-NET. The fact that anybody in the Netherlands has to deal with the related range is clearly reflected by the contact persons or roles which is CREW-RIPE or something like that and which is situated in NL. I'm looking forward to hear your opinion. Best regards, Christoph Mohr -- -- Christoph Mohr, BelWue Coordination ---------- mailto:mohr@belwue.de ----- Computing Center University of Stuttgart (RUS) Phone: +49 711 685-2079 Allmandring 30, D-70550 Stuttgart Fax: +49 711 678-8363 ------------------------------------------------- http://www.belwue.de/ -----

11 16

Prototype release of RPSLng IRRToolSet
by Katie Petrusha 23 Oct '03

23 Oct '03

[ Apologies for multiple messages ] Dear Colleagues, The RIPE NCC is pleased to announce version 4.8.1 prototype release of IRRToolSet. RPSLng is an effort to extend RPSL language, enabling the language to document routing policies for the IPv6 and multicast address families currently used on the Internet. The prototype of IRRToolSet implements the Internet Draft Document draft-blunk-rpslng-01 (http://www.ietf.org/internet-drafts/draft-blunk-rpslng-01.txt). The prototype release contains peval, rpslcheck and RtConfig that already work with a new dictionary (you can also try the Web prototype for peval and RtConfig). Currently work is in progess to make other tools RPSLng compatible. More details can be found at: http://www.ripe.net/db/irrtoolset Please contact irrtoolset(a)ripe.net for any comments. -- Best regards, Katie Petrusha RIPE NCC

1 0

Re: [db-wg] Change of Country entries in the database
by Wilfried Woeber, UniVie/ACOnet 23 Oct '03

23 Oct '03

Leo, >Hank Nussbacher <hank(a)att.net.il> wrote: > >[...] > >>I wouldn't make it optional > >What is the benefit of having it as a mandatory attribute? > >Regards, I can't see any at first glance (rather stuff being optional tends to get omitted anyway :-) > >-- >leo vegoda >RIPE NCC >Registration Services Manager My admin question would be: is there any internal machinery @ the NCC which assumes the presence (and "correctness") of that attribute? Wilfried.

1 0

Re: [db-wg] Change of Country entries in the database
by Hank Nussbacher 10 Oct '03

10 Oct '03

At 11:26 AM 09-10-03 +0200, Peter Koch wrote: >Hank Nussbacher wrote: > > > PS I think the country code should 00 for whole world since as countries > > split - who knows if ZZ or any two letters will be used in the future. > >ZZ is fine. ISO 3166-1 has reserved code points for exactly this purpose. >See >http://www.iso.ch/iso/en/prods-services/iso3166ma/10faq/frequently-asked-qu… Ya learn something new every day. Thanks, -Hank >"EU" is not on this list, but it's on a - meanwhile non-public - separate list >and will not be assigned. Different topic :-) > >-Peter

4 3

Fw: FAILED:
by benhadjira 06 Oct '03

06 Oct '03

Dear sir We have tried several times to add inetnum to the data-base, but unfortunetely this is the error message we received every time . Could you please give us some help & advices on how to do it ? Thanking you in advance Mourad Techni-communication -------Original Message------- From: ripe-dbm(a)ripe.net Date: samedi 4 octobre 2003 10:34:28 To: benhadjira(a)techni-communication.com Subject: FAILED: > From: benhadjira(a)techni-communication.com > Subject: > Date: Sat, 04 Oct 2003 05:34:19 -0400 > Reply-To: benhadjira(a)techni-communication.com > Message-ID: <04df532f66b14c6c874ce4e412db3b3d(a)techni-communication.com> SUMMARY OF UPDATE: Number of objects found: 1 Number of objects processed successfully: 0 Create: 0 Modify: 0 Delete: 0 No Operation: 0 Number of objects processed with errors: 1 Create: 1 Modify: 0 Delete: 0 Syntax Errors: 0 DETAILED EXPLANATION: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The following object(s) were found to have ERRORS: --- Create FAILED: [inetnum] 217.29.219.0 - 217.29.219.255 ***Error: Authorisation failed ***Info: Syntax check passed inetnum: 217.29.219.0 - 217.29.219.255 netname: Techni-communication descr: Techni-Communication - customer SEI.NET country: DZ admin-c: MA1973-ripe tech-c: BM1974-RIPE status: LIR-PARTITIONED PA mnt-by: BM-MNT mnt-lower: BM-MNT mnt-routes: TACHYON-EU-MNT changed: benhadjira(a)techni-communication.com 20031004 source: RIPE ***Info: Authorisation for parent [inetnum] 217.29.208.0 - 217.29.223.255 using mnt-lower: not authenticated by: BM-MNT ***Info: Authorisation for [inetnum] 217.29.219.0 - 217.29.219.255 using mnt-by: not authenticated by: BM-MNT ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The following paragraph(s) do not look like objects and were NOT PROCESSED: -------------------------------------------------------------------- mail2web.com - Check your email from the web at http://mail2web.com. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For assistance or clarification please contact: RIPE Database Administration <ripe-dbm(a)ripe.net> .

2 1

Reverse DNS Restructuring Project
by Olaf M. Kolkman 01 Oct '03

01 Oct '03

Dear Colleagues, I have just posted a proposal about the restructuring of the reverse DNS setup to the ncc-services-wg mailing list. I'd like to point out that this proposal has relevance to both the dns-wg and db-wg. You can find the proposal on http://www.ripe.net/reverse/proposal.html Please provide your feedback on the ncc-services-wg mailing list. With excuses for the cross-post, -- Olaf ---------------------------------| Olaf M. Kolkman ---------------------------------| RIPE NCC

1 0