- NZNOG - lists.nznog.org

NZ whois server
by Andy Linton 29 May '00

29 May '00

As a NZ domain holder, I am unimpressed by the apparent inability of the Council of ISOCNZ to require Domainz to carry out the policies it is supposed to and I am also unimpressed by the failure of the Board of Domainz in ensuring that the policies of ISOCNZ are carried out. I and a number of others have requested the introduction of a whois server that allows access to the data on the ISOCNZ NZ Registry that is operated on the Society's behalf by their operating company Domainz. This is consistent with the requirement stated in the Council's policy on New Zealand's Domain Name Structure. In that document (http://www.mcs.vuw.ac.nz/~hine/ISOCNZ/DNS/DNpolicy-8-97.html#SecondLevel) the section "Use of Information Gathered" the first paragraph says: 'Information is gathered in order to provide a public name listing service in line with other Internet domain name registry services world-wide.' Other registry services world-wide implement a whois service as well as a web-based service as a matter of course. I understand that the Council of the Society has instructed Domainz to implement such a server. Can you give an indication of when this service will be available? I also note that a name for this service is listed in the DNS. It is confusing to have this name there and then not have a service running. The details are below. whois.domainz.net.nz -> 202.46.160.18 -> www-wlg.domainz.net.nz Can you ensure that either the service that this host name purports to implement is commenced or that this host name is removed? --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

3 5

Re: NZ whois server
by Andy Linton 29 May '00

29 May '00

At 05:49 PM 5/30/00 +1200, you wrote: >Andy Linton <asjl(a)netlink.net.nz> wrote: > >My apologies! I'm using the RIPE whois client and it never returns when > >I type: > > > >whois -h whois.domainz.net.nz lionra.net.nz > > > >although it's quite able to talk to other whois servers around the > >planet. > >OK, I was kinda intrigued about this one. So I downloaded the RIPE stuff >and had a play. > >It seems that the RIPE whois terminates its query with a single LF, >not CRLF as as the Domainz server is expecting. From tcpdump: > >17:02:01.058956 toyunix.zl2tnm.gen.nz.62311 > >www-wlg.domainz.net.nz.whois: P 1: >16(15) ack 1 win 17520 > 4500 0037 d189 0000 4006 7d4c c0a8 0102 > ca2e a012 f367 002b 3d2b 3c24 0827 44dd > 5018 4470 cec9 0000 6461 6564 616c 7573 > 2e63 6f2e 6e7a 0a > >(for those who don't read hex, that's <ip-header> <tcp header> >"daedalus.co.nz\n" No "\r". I suspect the Domainz server is waiting >for the CR not the LF. >I'm amazed. I didn't think it was possible to screw up the whois >protocol, much less have an outfit like RIPE do it. From RFC 954: Agreed. That's why I was so surprised when it didn't work and why I didn't check when I should have. If we're talking RFCs - RFC 1123 (:-) 1.2.2 Robustness Principle At every layer of the protocols, there is a general rule whose application can lead to enormous benefits in robustness and interoperability: "Be liberal in what you accept, and conservative in what you send" Software should be written to deal with every conceivable error, no matter how unlikely; sooner or later a packet will come in with that particular combination of errors and attributes, and unless the software is prepared, chaos can ensue. In general, it is best to assume that the network is filled with malevolent entities that will send in packets designed to have the worst possible effect. This assumption will lead to suitable protective design, although the most serious problems in the Internet have been caused by unenvisaged mechanisms triggered by low-probability events; mere human malice would never have taken so devious a course! Thanks for sorting this out, by the way! --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

FW: [apnic-announce] Maintenance Announcement: June 3rd 8:00 - 12:00 UTC+10
by jabley＠automagic.org 29 May '00

29 May '00

----Original Message----- From: Paul Gampe <paulg(a)apnic.net> To: apnic-announce(a)lists.apnic.net Cc: Subject: [apnic-announce] Maintenance Announcement: June 3rd 8:00 - 12:00 UTC+10 Reply-To: apnic-talk(a)apnic.net Date: Tuesday, May 30, 2000 1:23 PM [Note "reply-to:" field] Dear APNIC Member, APNIC will be performing an operating system maintenance on the primary whois server, whois.apnic.net during the Saturday June 3rd maintenance window between 8:00 - 12:00 UTC+10. The following services will be affected for periods of at most 15 minutes during the maintenance window: whois, dns, www.apnic.net and mailing lists. Both dns and email services will be provided by our secondary servers during this time. Should you have any questions regarding this announcement please e-mail: technical(a)apnic.net. We apologise in advance for any inconvenience that this may cause. Regards, Paul Gampe -- _______________________________________________________________ For PGP Key ID B49E3514, mailto:paulg(a)apnic.net send mail with Subject: pgp-key-request phoneto:+61-7-3367-0490 Paul Gampe - Technical Manager - APNIC faxto:+61-7-3367-0482 * APNIC-ANNOUNCE: Announcements concerning APNIC * * To unsubscribe, send "unsubscribe" to apnic-announce-request(a)apnic.net *

1 0

IHUG oddities
by Rob Isaac 29 May '00

29 May '00

Folks, Terabyte in Auckland have a bunch of dialup accounts that they use to test sites in development. One of these accounts is with IHUG. The bizarre thing is that this dialup account isn't able to access any web pages at Terabyte from the PPP connection to IHUG. You can look up the name fine, and you can ping the remote server -- it's specifically HTTP traffic (tcp/80) that doesn't work. In the tests I've seen, the source address was 203.109.194.220 (presumably handed out by IHUG's DHCP), and the destination networks are Terabyte's hosting, at either 203.167.248.0/24 or 203.97.64.0/24. Can someone else test this via IHUG (and perhaps via someone else, in case there is some more obscure problem). http://www.terabyte.co.nz/ will do fine as an address to test. They've tested it already using a handful of other dialup ISPs around the countryside, and they work fine -- it's just IHUG that doesn't seem to work, and only for web traffic. I want to get some more tests done before I go pester IHUG with a vague complaint that may be nothing to do with them. Regards, Rob. --------- 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 full service registrars
by Peter Mott 28 May '00

28 May '00

We are trying to build a list of "domainz full service registrars". We have many customers who have setup domain name service on our system, but are having difficulty navigating the domainz site to register their name. When they contact domainz for assistance, they are told the reason they have a problem is because they are not using a full service registrar. XTRA, CLEAR Net, IHUG, WEBFARM and others have all been mentioned in communications. On several occasions our customers have contacted one of the above to have them register their domain name, but the "full service registrar" concerned refused to enter 2day.com domain name servers into the registry record. If you are a domainz registrar willing to enter name server records according to customer requirements, please email me. Regards Peter Mott Chief Enthusiast 2day.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

Re: [i-c-discuss] Help request
by Roger De Salis 26 May '00

26 May '00

Sue Leader wrote: > > Greetings > > I have an inquiry to answer and am missing one essential piece of > inforamtion. Can anyone tell me what the rationale was for having a > second level domain (2LD) structure rather than a flat structure in > .nz? So that the address structure can be divided into things that humans can remember. Also the 2LD provides some clue as to the purpose of the organisation eg .mil. .gov. or .co. There are of course variations in between the USA (1LD) and ROW (2LD). .co - .com .govt - .gov .ac - .edu. NZ has an interesting variation of this at the 3LD level. the 3rd level domain called domainz.net.nz which is a loopback domain. This loopback feature has a unique feature based on the amount of SPAM created this particular domain, so SPAM sent to this particular domain is endlessly recycled permitting near perfect service levels when responding to SPAM. In order to cater for loopback domains, the 3LD known as domainz is permanently wired to ORBS, which is an interactive mail responder. This permits meaningful dialog between the loopback domain and SPAM origination. In order to avail themsleves of this wonderful service, most ISP's in this country have implemented RFC 42064.32 which adheres to the Irish variation of ORBS. This means that all communication from the loopback domain is directed via sendmail to /dev/null. Unfortunately Microsoft clients have no way of implementing this device, and are therefore forced forever to endure SPAM which commences "Domainz is considering changes to.......". There is unfortunately no way to ever leave this highly desirable email domain. Hope this helps.... Rgds Roger De Salis > > Thanks > Sue > Sue Leader - Executive Director > ISOCNZ (Internet Society of New Zealand Inc) > Exe.Dir(a)isocnz.org.nz Voice: +64-4-801-6256 http://www.isocnz.org.nz > Postal: Level 1, (e)-Vision Centre, 282 Wakefield St, Wellington > "Error: Press any key to continue or any other key to quit..." > > All information contained in this message is > confidential to members of the ISOCNZ Council. > _______________________________________________________ > isocnz-council-discuss mailing list > isocnz-council-discuss(a)isocnz.org.nz > http://listserver.actrix.co.nz/mailman/listinfo/isocnz-council-discuss -- \_ 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

Amazing
by Chris Foster 26 May '00

26 May '00

Guess what? I only received my name holder id yesterday and today I received my password. How have domainz done it? took them a while to figure out? Chris --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

Re: [i-c-discuss] Help request
by Michael Newbery 23 May '00

23 May '00

On 24 May 2000, Simon Lyall <simon.lyall(a)ihug.co.nz> wrote: > On Wed, 24 May 2000, Andy Linton wrote: > > Except to note that it's not necessary and in fact simply causes > > confusion. For example, if you wanted to contact Paradise (the ISP) > > would you choose paradise.co.nz or paradise.net.nz? Now make the choice > > as a naive user. > > Of course if they pick www.paradise.gen.nz then they might really have a > problem. > > > With the benefit of hindsight I'd advocate that it's all a crock and a > > single domain, .nz is all we need. > > It does have the advantage in letting "clashing" names have an > alternative. This is especially good since if your name is Mcdonald or > Harrods then if you take a .gen.nz or .org.nz domain then it is > automaticly assumed to be personal rather than taking a shot at the big > boys. As I recall, the intent was also to delegate authority. Thus the owner of .mil.nz would accept only suitably armed and dangerous organisations. The Universities, who were de facto running ".nz" thought they might be considered presumtuous if they allocated all sub-domains, and even then we did not consider it part of our 'core' business. As it happened of course, we ended up doing it for everyone anyway, pretty much. Bear in mind that this was the time of GOSIP, when Standards NZ wanted a large number of thousands of dollars, per year, to assign you an X.121 address. Countries coming to the Internet somewhat later have had the benefit of experience and have sometimes chosen different schemes. Another consideration was that in the VERY early days, we had big and little endian addresses (JANET style nz.ac.vuw vs Internet style vuw.ac.nz), and since NZ had Spearnet (Coloured book, JANET derived protocols) and TCP style addressing simultaneously for a while, PLUS the BITNET link between Auckland and VUW, plus uucp bang paths, plus Compuserve (remember them :-) we tried to make names unambigous under several transformations. That was one reason we explicitly chose 2LDs that were *not* gov, com or edu. By the time mil.nz and org.nz were necessary, this was no longer considered a problem. -- Michael Newbery Technology Manager Saturn Communications Tel: +64-4-939 5102 Mobile:021-642 957 Fax:+64-4-939 5100 --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

1 0

Email notifications et al
by Andrew McEwen Mason 23 May '00

23 May '00

1. Email notifications ------------------- Ted is correct. The messages are going out to Registrars as notified last week and as Ted has discovered. However, they are not as yet going to name server managers who are _not_ Registrars, but this will be changed to include NS managers as from tomorrow morning. 2. Names on hold ------------- We will start tomorrow on releasing the backlog of names on hold. 3. Bugs/issues/change requests --------------------------- We are setting up a discussion list for these, which we plan to have live by this weekend - might cut down on traffic to the public lists :-) Will also have a tool for Registrars in particular to notify and track resolution of bugs. Cheers Andrew > -----Original Message----- > From: isocnz-l-admin(a)isocnz.org.nz > [mailto:isocnz-l-admin(a)isocnz.org.nz]On Behalf Of Ted Grenfell > Sent: 23 May, 2000 17:22 > To: isocnz-l(a)isocnz.org.nz; isocnz-l(a)isocnz.org.nz > Subject: RE: [isocnz-l]Domainz debacle continues > > > At 17:13 23/05/00, Peter Mott wrote: > > > Still nothing from domainz in regard to email notifications. > > > >Just rang domainz, they dont know when soa notifications are going to be> >fixed either. Nothing changes. > > POB told me they should be going today and I've seen some that > are in fact > coming through. We don't yet know though if we're getting all the ones we > should be but we're definitely getting some of them. > > > -- > Ted Grenfell > Xtra ISP Performance Manager > Mob 025 435 455; DDI 09 359 5854; Fax 09 355 5283 > Level 12, Telecom Tower, 16 Kingston St, Private Bag 92028, Auckland > > > > _______________________________________________ > go to http://listserver.actrix.co.nz/mailman/listinfo/isocnz-l > for subscription/unsubscription information. > --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1

Re: List of Registry Problems
by david＠farrar.com 22 May '00

22 May '00

> > I have compiled (and yes it did take me a long time) a list of known > > problems and bugs encountered with the new DOMAINZ registry system. > > It stands at 49 at present. Many of them have now been resolved but I > > believe it is important to note them as they occurred. > > > > The list is at http://www.dpf.ac.nz/isocnz/domainz.htm > > Excellent idea - I can see this list growing rapidly as more people add > issues to the list. I think it's safe to say that Domainz are unaware of > many of the problems with their system, and so it is important for us to > (politely) raise these issues. A buglist such as this one is an ideal way > to do so. Thanks for the extra eight points. I had had several from others and will update the site tonight. While my original intention was more historical to be of use in any inquiry (and showing the need for one) I am happy to modify it so it can be used to show what problems are still outstanding. Hence I will add on tonight a field called "Resolution" showing if the problem has been resolved, was one-off, is a philosphical as opposed to a technical problem or if it is still unresolved. These will be based on my knowledge which is based on mainly the public lists. I would be most happy once the "Resolution" field has been added on to have DOMAINZ inform me of further resolutions so I can keep it up to date. DPF --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

2 1