- NZNOG - lists.nznog.org

RE: Domainz information corruption.
by James Bell 11 May '00

11 May '00

At 12:24 PM 5/11/00 +1200, you wrote: >Right well, I registered those domain names, and as far as I understand, >that is the fuction of registrar. However I realise that doesn't >immediatly make me a registrar (as exciting a title as that is). So what >does? Paying Domainz $300 (or $3000). and signing a Registrar agreement. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

DRS availability
by Andrew McGhie 11 May '00

11 May '00

This is to inform you that the Domainz Registration System is again available as from 08.00 today. Regards Andrew Mason --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

DRS update
by Andrew McEwen Mason 10 May '00

10 May '00

This is to let you know that, although the DRS web-based system is still off-line, the automated email template interface continues to be available as before. The zone build has just been completed. We will continue to keep you posted re the web-based system. Regards --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

DRS availability
by Andrew McEwen Mason 10 May '00

10 May '00

We are currently experiencing some technical issues with the Domainz Registration System, as a result of which the system has been taken off-line while these issues are resolved. Despite the above, the zone build is happening and the process is due to start shortly. We are making every effort to get the system back up as quickly as possible, and will keep you posted as to progress. Our sincere apologies for this disruption. Andrew Mason --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Re: Domainz information corruption.
by Dylan Reeve 10 May '00

10 May '00

> My understanding is that the domain name holder is the only person who > will be sent a login and password for their domain. > However Registrars will have their own Registrar Login & Password which > will allow them to do much of what the name holder can do, if not all. > I am not a Registrat so am not sure what limitations there are. > Certainly it makes sense that for example Xtra can change the Name > Server IP Address for all the domains who are hosted on Xtra but as some > have pointed out being their "host" doesn't mean you are their > Registrar. Okay, so my box, wibble, is master for 19 .nz domains (including one *legitimate* school, neat eh?) and slave for 9. Obviously, I would like to be able to make the same sort of changes I could before, with the domain key. Specifically my Technical Contact details and the like. All the domains I host are "Unallocated", and I am not about to go and convert all the keys of the domains I don't actually own, so how do I get in? You will have to excuse me, I know little about the new system, as I don't really do a whole lot of domain stuff these days... Is there anywhere that explains exactly what the changes are, how they affect me, and what I can do? I have looked around the site, but well, it's doesn't seem to explain well what the new system does/is. Dylan Reeve - dylan(a)wibble.net "Um, yeah." --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 2

Re: Domainz information corruption.
by david＠farrar.com 10 May '00

10 May '00

> What concerns me is the fact that with all these domains with incorrect > registrar's, where are these logins and passwords going to go? > > Does the domain owner get them? > Does the registrar get them? > Does a person chosen purely at random get them? > > Dean My understanding is that the domain name holder is the only person who will be sent a login and password for their domain. However Registrars will have their own Registrar Login & Password which will allow them to do much of what the name holder can do, if not all. I am not a Registrat so am not sure what limitations there are. Certainly it makes sense that for example Xtra can change the Name Server IP Address for all the domains who are hosted on Xtra but as some have pointed out being their "host" doesn't mean you are their Registrar. DPF --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Domainz information corruption.
by Simon Lyall 10 May '00

10 May '00

I just had a look at my domain of darkmere.gen.nz on the new domainz site of www.domainz.glazier.co.nz. The problem seems to be that the Holder Phone number seems to have been truncated in the change. On the old site at: http://domainz.waikato.ac.nz/cgi-bin/DNZ-REGISTER?domain_name=darkmere.gen.… It is: Holder Phone: +64 9 358 5067 ex 9701 but on the new site ( http://www.domainz.glazier.co.nz/ , then "Domain Name Management" , then "Domain Name Search" ) It is: Phone: 64 9 358 5067 ext 97 Note, the "+64" has been changed to just 64 and the extention on 9701 has been changed to 97. I guess somebody didn't think when they programed in that field. Overseas phone numbers just look funny, check out dianetics.co.nz -- Simon Lyall. | Newsmaster | Work: simon.lyall(a)ihug.co.nz System/Network Admin. | | Home: simon(a)darkmere.gen.nz Ihug Limited, Auckland, NZ | Asst Doorman | Web: http://www.darkmere.gen.nz --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

7 9

RE: System live
by david＠farrar.com 09 May '00

09 May '00

> > As promised, this is to let you know that the Domainz > > Registration System is > > now live. > > It's a pity that the name of the SSL certificate for the Domainz secure > site is incorrect. www.domainz.net.nz != www.domainz.glazier.co.nz. > > Some proxy servers and well configured browsers will throw this away. I've been having great problems with the site. I got the same security wrror (using IE5). Using a new password (we haven't received these automatically yet - can anyoen advise when we will) which I generated from their converter I tried to log in and it failed several times. Finally let me in but when I tried to change my registrar it came up no such webpage. Then started getting message saying the site is temporarily offline. Now the main site itself is giving me a no such page error. Can someone advise if the site is up and staying up? ta DPF --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 3

After-market RIPE whois service for the NZ ccTLD
by Joe Abley 09 May '00

09 May '00

As per subject; server running on maggie.automagic.org. Feedback welcome. Source attached. There are surely bugs. To those who have already seen this, apologies for the duplicates. To use, whois -h maggie.automagic.org blah.co.nz or, if you're using an OpenBSD snapshot more recent than the 2.6 release, whois blah.co.nz which is really a shortcut for whois -h nz.whois-servers.net blah.co.nz or, if you must, fwhois blah.co.nz(a)maggie.automagic.org or you could always use some Windows variant by feverishly clicking buttons and sliding scroll bars, forwarding VBS files to all your friends and relatives whilst distracted by the dancing paperclip. GEEK FAQ 1. Sometimes it looks very much as though I am returning duplicate person objects. However, the technical and holder contact details are not normalised within the glazier schema, and in fact the records where data is stored are quite different. I implemented an elaborate scheme which compared holder and tech details using a (patent-pending) fumbling hack heuristic, but abandoned it as soon as I realised that it's a fool's errand, really. 2. The whois server on whois.patho.gen.nz used "root(a)patho.gen.nz" as the e-mail address in the "changed" fields. This caused all kinds of spam complaints to be directed at that address, so in this new proxy I construct a postmaster address at the domain -- I can't use the real address of the last person to submit a change, since the Glazier system doesn't store it. 3. Check the header comments in each response to see which real server is being queried (this may well change). 4. Before you mail me and say "domain proz.ac.nz doesn't have a tech contact record!" check the authoritative glazier data, because so far that's where all the anomolies I have found actually originate. Don't shoot the messenger. 5. I run this on a BSD box out of tcpserver, using something like tcpserver -q -c 8 -u nobody -g nobody \ 0 whois /usr/local/libexec/whois-domainz.sh & but you could run it out of inetd just as easily. If you attempt to run it on certain (cough) user-friendly linux distribution, you'll have to hack the hideous fwhois syntax around the more correct and elegant "standard" berkeley whois syntax shown in the script (troll, troll). 6. Buffer bounds checking is weak in awk, so I'd advise running the script with no privileges (as above) if you want to run a local copy. 7. I had to use a nasty y2k hack when reformatting the "changed" field, since the Glazier system returns a two-digit year in the dates it returns. 8. The Glazier whois server from which we try to pull our source data has been periodically refusing connections. If we get connection refused, we fall back to using whois.patho.gen.nz (which reports on data from the Waikato system). A "%"-prefixed comment at the top will tell you when this happens. 9. Share and enjoy :) #!/bin/sh # # glazier/domainz whois proxy 0.11 # # I run this out of tcpserver, see http://cr.yp.to/ucspi-tcp/tcpserver.html # which is where TCPREMOTEIP comes from. The server at 202.46.160.18 is # running right now, but may move since I'm not aware that it's an offically- # supported service. # # This proxy is currently running on maggie.automagic.org, if you want # to test it out. Bugs, improvements and baseless legal threats should # be sent to jabley(a)automagic.org. # # This source is public domain. A courtesy tip of the hat would be # appreciated if you manage to make millions whilst using it :) # # Joe Abley, 7 May 2000 whois_glazier=whois.domainz.net.nz whois_waikato=tardis.patho.gen.nz tmp=/var/tmp/whois-glazier.$$ read key key=$(echo ${key} | tr ' ' ' ') echo "% * Proxy connection at $(date) from ${TCPREMOTEIP}" echo "% *" echo "% * Attempting whois from server ${whois_glazier}" echo "% *" if whois -h ${whois_glazier} ${key} 2>/dev/null >${tmp}; then awk -v whois_date="$(date)" -v whois_client="${TCPREMOTEIP}" \ -v whois_key="${key}" -v whois_glazier="${whois_glazier}" ' BEGIN \ { print "% * This data was harvested from a public whois interface"; printf "%% * hosted at %s. Retrieval and use of the data", whois_glazier; print "% * below are subject to the same restrictions and conditions"; print "% * imposed by the source server. No responsibility is taken"; print "% * nor warranty made for the accuracy of the information"; print "% * presented here. Administrative contact for this server"; print "% * is whois(a)automagic.org."; print "% "; printf "%% query: %s\n", whois_key; printf "%% client: %s\n", whois_client; printf "%% date: %s\n", whois_date; print "% "; } { gsub(/\r/, ""); } /^domain_name: / \ { ripe_domain = $2; next; } /^holder_contact: / \ { sub(/^holder_contact: /, ""); ripe_admin_c = $0; next; } /^technical_contact: / \ { sub(/^technical_contact: /, ""); ripe_tech_c = $0; next; } /^ns_name_[0-9][0-9]*: [a-zA-Z0-9]/ \ { ripe_nserver[ns++] = $2; next; } /^holder_name: / || \ /^domain_name_status: / || \ /^registrar: / || \ /^domain_datecreated: / \ { ripe_remarks[rk++] = $0; next; } /^domain_datelastmodified: / \ { sub(/^domain_datelastmodified: /, ""); split($0, field); split(field[1], subfield, /\//); year = (subfield[3] > 70 ? 1900+subfield[3] : 2000+subfield[3]); ripe_changed = sprintf("%4d%02d%02d", year, subfield[2], subfield[1]); next; } /^technical_contact_address_line_[0-9]: / \ { sub(/^technical_contact_address_line_[0-9]: /, ""); if ($0 !~ /^ *$/) ripe_tech_address[tad++] = $0; } /^technical_contact_phone: / \ { sub(/^technical_contact_phone: /, ""); ripe_tech_phone = $0; next; } /^technical_contact_fax: / \ { sub(/^technical_contact_fax: /, ""); ripe_tech_fax = $0; next; } /^technical_contact_email: / \ { sub(/^technical_contact_email: /, ""); ripe_tech_email = $0; next; } /^holder_address: / \ { sub(/^holder_address: /, ""); ripe_admin_address[0] = $0; next; } /^holder_addr_citycountry: / \ { sub(/^holder_addr_citycountry: /, ""); ripe_admin_address[1] = $0; next; } /^holder_phone: / \ { sub(/^holder_phone: /, ""); ripe_admin_phone = $0; next; } /^holder_fax: / \ { sub(/^holder_fax: /, ""); ripe_admin_fax = $0; next; } /^holder_email: / \ { sub(/^holder_email: /, ""); ripe_admin_email = $0; next; } {} END \ { if (ripe_admin_c == "") print "% * no registration data returned by query"; else { printf "domain: %s\n", ripe_domain; printf "admin-c: %s\n", ripe_admin_c; if (ripe_tech_c != "") printf "tech-c: %s\n", ripe_tech_c; for (s in ripe_nserver) printf "nserver: %s\n", ripe_nserver[s]; for (s in ripe_remarks) printf "remarks: %s\n", ripe_remarks[s]; printf "changed: postmaster@%s %s\n", ripe_domain, ripe_changed; printf "source: AUTOMAGIC\n\n"; printf "person: %s\n", ripe_admin_c; for (s in ripe_admin_address) printf "address: %s\n", ripe_admin_address[s]; if (ripe_admin_phone != "") printf "phone: %s\n", ripe_admin_phone; if (ripe_admin_fax != "") printf "fax-no: %s\n", ripe_admin_fax; if (ripe_admin_email != "") printf "e-mail: %s\n", ripe_admin_email; printf "changed: postmaster@%s %s\n", ripe_domain, ripe_changed; printf "source: AUTOMAGIC\n\n"; if (ripe_tech_c != "") { printf "person: %s\n", ripe_tech_c; for (s in ripe_tech_address) printf "address: %s\n", ripe_tech_address[s]; if (ripe_tech_phone != "") printf "phone: %s\n", ripe_tech_phone; if (ripe_tech_fax != "") printf "fax-no: %s\n", ripe_tech_fax; if (ripe_tech_email != "") printf "e-mail: %s\n", ripe_tech_email; printf "changed: postmaster@%s %s\n", ripe_domain, ripe_changed; printf "source: AUTOMAGIC\n"; } } }' ${tmp} rm -f ${tmp} logger -p daemon.info -t whois-glazier query key ${key} \ from ${TCPREMOTEIP} used ${whois_glazier} else echo "% * Connection refused from Domainz/Glazier whois server at" echo "% * ${whois_glazier}; reverting to Domainz/Waikato whois proxy" echo "% * at ${whois_waikato}" echo "% *" whois -h tardis.patho.gen.nz ${key} 2>/dev/null logger -p daemon.info -t whois-glazier query key ${key} \ from ${TCPREMOTEIP} used ${whois_waikato} fi --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 1

[Fwd: DRS request rejected]
by Andy Linton 09 May '00

09 May '00

drs-admin(a)domainz.net.nz wrote: > > Your request to the DRS mailing list: > > Posting of your message entitled: > Re: [DRS] DRS roll-out > > has been rejected by the list moderator. The moderator gave the > following reason for rejecting your request: > > Please do *not* post administrative requests to the mailing list! > If you wish to subscribe, visit > http://listserver.actrix.co.nz/mailman/listinfo/drs or send a 'help' > message to the the request address, drs-request(a)domainz.net.nz , for > instructions > > Any questions or comments should be directed to the list administrator > at: > > drs-admin(a)domainz.net.nz > > Your original message follows: > Received: from satva.actrix.co.nz (satva.actrix.co.nz [203.96.16.107]) > by mail2.actrix.gen.nz (8.10.0.Beta12/8.10.0.Beta10) with ESMTP id e4A3suq21870 > for <drs(a)mail2.actrix.gen.nz>; Wed, 10 May 2000 15:54:56 +1200 (NZST) > Received: from lemon.office.netlink.net.nz (lemon.office.netlink.net.nz [203.97.244.37]) > by satva.actrix.co.nz (8.10.0/8.10.0.Beta10) with ESMTP id e4A3stk15680 > for <DRS(a)domainz.net.nz>; Wed, 10 May 2000 15:54:56 +1200 (NZST) > Received: from netlink.net.nz (saw.cb.telstra.net.nz [203.97.244.24]) > by lemon.office.netlink.net.nz (8.10.1/8.10.1) with ESMTP id e4A3snA22918; > Wed, 10 May 2000 15:54:49 +1200 (NZST) > Sender: asjl(a)netlink.net.nz > Message-ID: <3918DD88.37507B06(a)netlink.net.nz> > Date: Wed, 10 May 2000 03:54:48 +0000 > From: Andy Linton <asjl(a)netlink.net.nz> > X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.5-15 i686) > X-Accept-Language: en > MIME-Version: 1.0 > To: Andrew McEwen Mason <andrew(a)bsa.co.nz> > CC: DRS(a)domainz.net.nz > Subject: Re: [DRS] DRS roll-out > References: <LNBBIAJHHJHJEBDNLNPBMEAODCAA.andrew(a)bsa.co.nz> > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > > Andrew McEwen Mason wrote: > > > > Greetings to all > > > > This is an update on where we are with the roll-out. > > > > As Andrew Jamieson notified earlier today, we have made good progress, but > > unfortunately we have been struck with a number of problems effectively > > outside our control, especially power cuts which (while they haven't done > > any damage to the servers) have made it very difficult for staff to connect > > to the systems for testing. The situation was compounded by a major fire > > alarm which also happened this morning! > > I'd like to make it clear to all concerned that the power cuts mentioned > above were not at the Telstra Saturn telehousing facilities where the > Domainz system is housed in Auckland and Wellington. Both facilities > have UPS and generator back up and no failure occurred at the nodes. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

NZ Address Space
by Chris Wedgwood 09 May '00

09 May '00

A while back I mentioned I would make a snapshot of what NZ networks (IP addresses) are in use. A couple of people have asked for this recently so I have compiled a rough list based on various prefixes within CLEAR's BGP tables. ftp://ftp.clear.net.nz/pub/netinfo/nz-address-space/ If there is any interest, I'll look at doing a better job of this at some point and perhaps having it automagically update from time to time. --cw -- Chris Wedgwood chris.wedgwood(a)clear.co.nz --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

RE: System live
by Sam Sargeant 09 May '00

09 May '00

> As promised, this is to let you know that the Domainz > Registration System is > now live. It's a pity that the name of the SSL certificate for the Domainz secure site is incorrect. www.domainz.net.nz != www.domainz.glazier.co.nz. Some proxy servers and well configured browsers will throw this away. ##----Sam-Sargeant---------NetLink-Ltd--------Systems-Developer----## until($x>=40){print$"x$x;for('#4V%M','+(%-A<F=E86YT("T`','%($IU<W0`', '(($%N;W1H97(`','.(%!E<FP(a)2&%C:V5R(0H`'){print unpack('u*',$_)}$x+=2} ##.................................................................## --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

System live
by Andrew McGhie 09 May '00

09 May '00

As promised, this is to let you know that the Domainz Registration System is now live. We have carried out a successful zone build as part of the switch-over process. There will be a daily zone build at 16.00 from today until further notice. Best regards to all Andrew Mason (from Andrew McGhie's email and on behalf of all at Domainz and Advantage Group) --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

RE: Domainz information corruption.
by Andrew McGhie 09 May '00

09 May '00

Hi Simon Thanks for pointing out this problem, which relates to the field length for phone numbers. We have added it to our list of "things to fix". Will also investigate the US example you gave. Cheers Andrew Mason (from Andrew McGhie's email). -----Original Message----- From: owner-nznog(a)list.waikato.ac.nz [mailto:owner-nznog(a)list.waikato.ac.nz]On Behalf Of Simon Lyall Sent: Wednesday, May 10, 2000 10:42 AM To: nznog(a)list.waikato.ac.nz Subject: Domainz information corruption. I just had a look at my domain of darkmere.gen.nz on the new domainz site of www.domainz.glazier.co.nz. The problem seems to be that the Holder Phone number seems to have been truncated in the change. On the old site at: http://domainz.waikato.ac.nz/cgi-bin/DNZ-REGISTER?domain_name=darkmere.gen.n z It is: Holder Phone: +64 9 358 5067 ex 9701 but on the new site ( http://www.domainz.glazier.co.nz/ , then "Domain Name Management" , then "Domain Name Search" ) It is: Phone: 64 9 358 5067 ext 97 Note, the "+64" has been changed to just 64 and the extention on 9701 has been changed to 97. I guess somebody didn't think when they programed in that field. Overseas phone numbers just look funny, check out dianetics.co.nz -- Simon Lyall. | Newsmaster | Work: simon.lyall(a)ihug.co.nz System/Network Admin. | | Home: simon(a)darkmere.gen.nz Ihug Limited, Auckland, NZ | Asst Doorman | Web: http://www.darkmere.gen.nz --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

DRS live cut-over
by Andrew McGhie 09 May '00

09 May '00

Good afternoon. This is an update on progress with bringing in the new DRS. We have just (at midday today) carried out a final successful zone comparison, and are now confident that we can proceed to cut over the system to fully live running. This will happen over the next 1 to 2 hours as we move all elements of the system (including email and web pages) between hosts, and we expect that the process will be complete no later than 14.00 today. It will include the first live zone build. We will then carry out another zone build at 16.00 today and daily at 16.00 thereafter as before. We will post to these lists as soon as the whole process has been successfully completed. Best regards Andrew Mason (from Andrew McGhie's email today) --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

NETWORK SOLUTIONS SECURITY TRUTHS? (fwd)
by Joe Abley 09 May '00

09 May '00

Presumably when someone uses this vulnerability to take down the root registry, any concerns about the technical viability of the Domainz/ Glazier system will be rather academic :) ---------- Forwarded message ---------- Date: Tue, 9 May 2000 13:53:54 -0700 (PDT) From: Exiled Dave <exiled_dave(a)yahoo.com> To: nanog(a)nanog.org Subject: NETWORK SOLUTIONS SECURITY TRUTHS? http://www.networksolutions.com/cgi-bin/makechanges/easysteps/easysteps.pl?… Check out /var/named/internic.net as well. __________________________________________________ Do You Yahoo!? Send instant messages & get email alerts with Yahoo! Messenger. http://im.yahoo.com/ --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

ns_ip_* vs. ns_name_* in new Domainz system
by Joe Abley 08 May '00

08 May '00

Has anybody else seen instances in the new register where a domain has ns_name_* records, but no corresponding ns_ip_* records? For example, patho.gen.nz has: ns_name_1: dns1.clear.net.nz ns_ip_1: 203.97.33.1 ns_name_2: soa2.qsi.net.nz ns_ip_2: ns_name_3: tardis.patho.gen.nz ns_ip_3: 203.97.2.226 ns_name_4: medusa.blackops.org ns_ip_4: This makes me slightly nervous. Has anybody else seen this kind of thing for other domains? Are the current zone files running at ns99.waikato.ac.nz built from this new data, or are the old zone files still running? If the former, when will the first authoritative zone from the new system be loaded? (it looks like it will be worth checking). The fact that the hosts soa2.qsi.net.nz and medusa.blackops.org are quite possibly unknown to Domainz makes me suspect a systematic problem of some kind, and not a random one. Joe --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 4

[DRS] DRS roll-out (fwd)
by Simon Green 08 May '00

08 May '00

From the 'super-secret' domainz registrars mailing list. I feel that this information should be made available to those that need it and not just registrars, hence me reposting it. -- ---------- Forwarded message ---------- Date: Tue, 9 May 2000 12:18:20 +1200 From: Andrew Jamieson <AndrewJ(a)advantagegroup.co.nz> To: "'drs(a)domainz.net.nz'" <drs(a)domainz.net.nz> Cc: "'p.o.brien(a)domainz.net.nz'" <p.o.brien(a)domainz.net.nz>, "'a.mcghie(a)domainz.net.nz'" <a.mcghie(a)domainz.net.nz>, "'andrew(a)bsa.co.nz'" <andrew(a)bsa.co.nz> Subject: [DRS] DRS roll-out Hi to all The system went live for Registrars about an hour ago. By now I hope everyone has received an email with their logon ID and password, together with requisite information for accessing and using the system at www.domainz.glazier.co.nz. If you have any problems with this, please contact registrars(a)domainz.net.nz. We are planning to go fully live before midday tomorrow, at which time the URL for the system will change to www.domainz.net.nz. We will let you know when this happens. Cheers Andrew Mason _______________________________________________ DRS mailing list DRS(a)domainz.net.nz http://listserver.actrix.co.nz/mailman/listinfo/drs --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

[Fwd: Domainz Registration System]
by Geoff Thompson 08 May '00

08 May '00

2Day Tech Support wrote: > > > This is to notify you that the new Domainz system (DRS) has gone live for > > Registrars as of 11.00 today. > > I still see the old site at www.domainz.net.nz > > How about switching that on so we can stop getting all the phone calls from > people!! > I think Domainz has only opened the system for registrars, and not to the general public. They'll probably change the 'www.domainz.net.nz' stuff once they've gone fully live. Geoff. ---------------------------------- Geoff Thompson <geofft(a)waikato.ac.nz> University of Waikato, Hamilton, New Zealand Ph: (07) 838 4748 Random Quote of the Minute : And now for something completely the same. ---------------------------------- --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

Domainz Registration System
by Andrew Jamieson 08 May '00

08 May '00

Greetings to all This is to notify you that the new Domainz system (DRS) has gone live for Registrars as of 11.00 today. We plan to go fully live to "the world" before midday tomorrow. Cheers Andrew Mason (from Andrew Jamieson's system) --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

Updating tech contact info at Domainz
by Joe Abley 08 May '00

08 May '00

Hey, Perhaps someone who has stuck with the Domainz/Glazier testing for longer than me could tell me how to do this: I want to update my contact details in all the domain records for which I am listed as technical contact. I don't have an accurate list of domains that fit that criteria; I just want to change _all_ of them. In the old system, accomplishing this would be a case of performing a zone transfer, enumerating every possible domain I could be associated with, pulling the registry data for each domain in turn and discarding those that don't match a proscribed regular expression on the tech_contact field (or whatever it was called). Does the new system provide anything better than this? I have an inkling that holder_contact fields are normalised, but I don't think the tech contact fields are. If anybody can tell me an easy way to do this, I'd be keen to hear it. [Interesting to note that this is a trivial exercise in the original InterNIC and RIPE database schemas, which featured published database keys for person/contact objects (NIC handles) and were designed more or less by accident twenty years ago :)] --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

FW: [DRS] DRS roll-out
by Peter Mott 07 May '00

07 May '00

Looks like the monopoly .nz registrar DOMAINZ is going to be yet another day off line. I wonder what the next delay will be, an earthquake in wellington? p.s. Looks like somebody needs to donate them a UPS or two, apparently they haven't thought of the need for them yet. Regards Peter Mott Chief Enthusiast 2day.com -/- > -----Original Message----- > From: drs-admin(a)domainz.net.nz [mailto:drs-admin(a)domainz.net.nz]On > Behalf Of Andrew McEwen Mason > Sent: Monday, 8 May 2000 8:24 p.m. > To: DRS(a)domainz.net.nz > Subject: [DRS] DRS roll-out > > > Greetings to all > > > This is an update on where we are with the roll-out. > > As Andrew Jamieson notified earlier today, we have made good progress, but > unfortunately we have been struck with a number of problems effectively > outside our control, especially power cuts which (while they haven't done > any damage to the servers) have made it very difficult for staff > to connect > to the systems for testing. The situation was compounded by a major fire > alarm which also happened this morning! > > Be that as it may, we are confident that the name-nameholder data > on the new > system is as it should be, and that the zone file creation process is > working as we expected. There are a few issues to clear up with some > accounting data on a small number of domains, and we still need > to generate > randomised IDs and passwords, but apart from that we are looking pretty > good. > > We obviously want to be entirely sure that the system, the data > and the zone > files are absolutely as they should be before releasing them. We are > therefore planning to work through the night on them with a view to > releasing the system with everything working to Registrars at 09.00am > tomorrow (9th May 2000). We then plan to have the system fully > live to the > world on Wednesday 10th May 2000. > > Our apologies that the system roll-out has been delayed by a day > or so. We > hope it has not been too much of an inconvenience for you. We will notify > you as soon as the system is ready for use, with your Registrar > logon ID and > password for testing. > > _________________________________ > Andrew McEwen Mason > BSA Consulting Group > 7 Mariri Road, Kelburn > Wellington, NZ > > Phone +64 4 934-3178 Mobile +64 21 466-181 > > > _______________________________________________ > DRS mailing list > DRS(a)domainz.net.nz > http://listserver.actrix.co.nz/mailman/listinfo/drs --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

ORBS.
by Roger De Salis 07 May '00

07 May '00

By chance... since you lot have been particularly noisy this weekend on the subject of ORBS, I wanted to obtain a more rounded opinion of the value of ORBS with respect to SPAM Prevention. ISOCNZ has charged myself and three others with coming up with a policy concerning ORBS and potentially other SPAM prevention methods. :-( My understanding of the situation is as follows:- Paul Vixie contributes to/manages???? an RBL repository of Open Mail Relays on the side of www.vix.com. ie MAPS and RBL. How many carriers (even carriers with only 6 staff...) in NZ piggyback off this effort? And contribute? ORBS is a similar idea, run by AB of Manawatu Internet Services. An area of concern is that ORBS uses a method of publicity to shame Open-Relay holders into changing their status. However the publicity mechanism can also be used by Spammers to work out best SPAM procreation locations. How useful is this, and are their better ways of doing it? ========================================================= Should NZ ISP's all support RBL/MAPS? (realising that there is no requirement today, other than best customer service and best endeavours.) Is ORBS complementary? Is it appropriate? What do others think? Should ISOCNZ but out of this matter, and stick to mindlessly boring meetings with 10,000 points of order? Flames to myself at Cisco. Fabulously written, illuminating, insightful pieces will certainly receive a direct response of thanks and comments. All others >/dev/null. Rgds Roger De Salis -- \_ Roger De Salis Cisco Systems NZ Ltd </' +64 25 481 452 L3, 117 Customhouse Qy /) +64 4 473 4912 Wellington, New Zealand (/ roger(a)desalis.gen.nz rdesalis(a)cisco.com ` --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

4 3

[off-topic] Re: 2.7 ordering (fwd)
by Joe Abley 06 May '00

06 May '00

Ah. Looks like I jumped the gun :) ---------- Forwarded message ---------- Date: Sat, 06 May 2000 20:00:07 -0600 From: Theo de Raadt <deraadt(a)cvs.openbsd.org> To: Joe Abley <jabley(a)automagic.org> Cc: misc(a)openbsd.org Subject: Re: 2.7 ordering > Am I correct in thinking that the aim is a 2.7 release on May 19? No. June 15 this time around. > Anybody know when the on-line ordering page will be taking orders on 2.7 > media? When we have artwork :-) --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

ORBS blocking
by Andy Linton 06 May '00

06 May '00

I haven't seen all of the messages posted in nznog on this subject so forgive me if I go over some ground that has been covered already. I'd like to make it quite clear to all NZ operators reading this that neither Telstra Saturn or any of its operating companies have any rules in place on their routers which are blocking traffic from the ORBS tester, relaytest.orbs.vuurwerk.nl We have not had any such rules and I am more than happy to make arrangements for an independant party to inspect the relevant router configurations and the audit trail of those configurations which is kept under RCS. Alan Brown has published a traceroute which he says demonstrates that Telstra Australia is blocking traffic. I have inspected the configuration of the pad19 router and no such filter exists on that host. Let me remind you of his posting: [RelayTst(a)amersfoort alan]$ /usr/sbin/traceroute 203.97.144.41 traceroute to 203.97.144.41 (203.97.144.41), 30 hops max, 40 byte packets 1 router (194.178.232.1) 0.871 ms 0.928 ms 1.077 ms 2 border (194.178.232.125) 0.834 ms 0.726 ms 0.688 ms 3 Vuurwerk.cust.ip.versatel.net (212.189.159.237) 1.132 ms 1.047 ms 1.152 m ... 16 199.37.127.190 (199.37.127.190) 284.622 ms 277.222 ms 288.499 ms 17 205.174.74.34 (205.174.74.34) 414.984 ms 406.353 ms 396.054 ms 18 FastEthernet0-0-0.pad19.Sydney.telstra.net (203.50.13.68) 399.113 ms 381.658 ms 405.766 ms 19 * * * 20 * * * 21 * * * 22 * * * He says this demonstrates that Telstra is blocking his tester. It does no such thing. The explanation is straightforward but not obvious. Traffic to 203.97.144.41 under the above traceroute was taking a path to New Zealand via Sydney at the time of the traceroute. The return path from Sydney is: pad19.Sydney>traceroute 194.178.232.55 Type escape sequence to abort. Tracing the route to relaytest.orbs.vuurwerk.nl (194.178.232.55) 1 FastEthernet1-0-0.pad16.Sydney.telstra.net (203.50.13.67) 0 msec 0 msec 0 msec 2 205.174.74.33 220 msec 220 msec 224 msec 3 199.37.127.193 [AS 5727] 220 msec 220 msec 224 msec 4 POS2-0-0.GW5.SFO4.ALTER.NET (157.130.197.77) [AS 701] 224 msec 220 msec 224 msec 5 145.ATM3-0.XR2.SFO4.ALTER.NET (146.188.149.38) [AS 701] 224 msec 220 msec 224 msec 6 190.at-1-0-0.TR2.SAC1.ALTER.NET (152.63.51.10) [AS 701] 224 msec 228 msec 228 msec 7 127.at-6-1-0.TR2.NYC9.ALTER.NET (152.63.6.81) [AS 701] 304 msec 308 msec 308 msec 8 186.ATM6-0.XR2.NYC1.ALTER.NET (152.63.21.73) [AS 701] 304 msec 308 msec 304 msec .... The next hop that a packet takes on route to 203.97.144.41 is to Telstra Australia's router in Auckland. This is Telstra Saturn's interconnect point with Telstra Australia. The nzsx-core1 router has two paths out of New Zealand, one to pad19 and the other to above.net at the PAIX. The preferred path for return packets to relaytest.orbs.vuurwerk.nl on that router in Auckland is via the direct route to Palo Alto. So we have an assymetric path from the site in the Netherlands to 203.97.144.41 on that trans Pacific part of the packet flow. Why is this important? Because above.net appear to have something on one of their routers which drops packets to/from relaytest.orbs.vuurwerk.nl Compare this trace: $ traceroute relaytest.orbs.vuurwerk.nl traceroute: Warning: ckecksums disabled traceroute to relaytest.orbs.vuurwerk.nl (194.178.232.55), 30 hops max, 40 byte packets 1 router.wlg.office.netlink.net.nz (203.97.244.1) 1.458 ms 1.202 ms 3.674 ms 2 b1.wlg.netlink.net.nz (203.97.132.129) 2.402 ms 2.696 ms 1.383 ms 3 Fe0-0.nzlq1.Wellington.telstra.net.nz (203.98.56.177) 1.584 ms 1.324 ms 1.474 ms 4 FastEthernet0-0-0.nzsx-core1.Auckland.telstra.net.nz (203.98.21.26) 31.880 ms 24.598 ms 21.631 ms 5 Serial0-1-0.paix1.PaloAlto.telstra.net (203.50.126.18) 155.577 ms 155.112 ms 290.211 ms 6 core1-gige.pao.above.net (209.249.0.244) 155.199 ms 155.356 ms 155.082 ms 7 sjc-pao-oc12.sjc.above.net (209.133.31.149) 159.880 ms !H 155.972 ms !H 156.138 ms !H with: $ traceroute 194.178.232.1 traceroute: Warning: ckecksums disabled traceroute to 194.178.232.1 (194.178.232.1), 30 hops max, 40 byte packets 1 router.wlg.office.netlink.net.nz (203.97.244.1) 1.687 ms 1.436 ms 1.317 ms 2 b1.wlg.netlink.net.nz (203.97.132.129) 1.806 ms 1.753 ms 1.545 ms 3 Fe0-0.nzlq1.Wellington.telstra.net.nz (203.98.56.177) 1.834 ms 1.755 ms 1.652 ms 4 FastEthernet0-0-0.nzsx-core1.Auckland.telstra.net.nz (203.98.21.26) 22.730 ms 21.084 ms 23.203 ms 5 Serial0-1-0.paix1.PaloAlto.telstra.net (203.50.126.18) 156.800 ms 159.412 ms 382.058 ms 6 core1-gige.pao.above.net (209.249.0.244) 195.495 ms 154.912 ms 155.196 ms 7 core3.sjc2-core1.pao-oc12.sjc2.above.net (216.200.254.185) 157.541 ms 156.235 ms 159.225 ms 8 core5.sjc2-core3.sjc2.above.net (208.185.156.66) 156.049 ms 155.687 ms 157.684 ms 9 nyc-sjc-oc12.nyc.above.net (208.185.156.162) 232.711 ms 233.514 ms 232.355 ms 10 core2-core1-oc12.nyc.above.net (209.133.31.202) 232.135 ms 231.995 ms 232.695 ms 11 POS3-0-0.GW4.NYC4.ALTER.NET (157.130.31.45) 237.016 ms 242.895 ms 241.483 ms 12 146.ATM2-0.XR2.NYC4.ALTER.NET (146.188.179.174) 237.683 ms 238.036 ms 237.969 ms .... So let me summarise this for you all. 1) We are not blocking nor have we been blocking traffic from this particular ORBS tester or any other ORBS tester. Until this incident occurred we had no knowledge that this address hosted such a tester. 2) My technical staff have reiterated this on a number of occasions on this list and directly to Alan Brown. He has consistently refused to accept their explanations and assurances. 3) We have a customer who had a misconfigured host. They have taken steps to rectify that. Our published Terms & Conditions make it clear that we do not tolerate spam and we acted promptly on notification of the problem. 4) We are guilty of having an assymetric routing path. I am not aware that this is an "ORBSable" offence. 5) Any discussion on 'filters' needs to be with above.net who provide connectivity for Telstra and a number of other NZ providers. Now can I please get back to my weekend? Regards, andy --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0