- NZNOG - lists.nznog.org

Something a bit more on-topic: UK firm recons it's got the busiest interchange!
by Craig Humphrey 04 Oct '04

04 Oct '04

http://news.bbc.co.uk/2/hi/technology/3700290.stm I'm surprised it's bigger than any in the USA or say Germany.

9 10

RE: [nznog] so ... what is the real reason there is whois anyway?
by Frank March 30 Sep '04

30 Sep '04

-----Original Message----- From: Robert Gray [mailto:bob(a)brockhurst.co.nz] Sent: Friday, 1 October 2004 7:30 a.m. Keith Davidson wrote: > InternetNZ has already agreed to implement DNSSEC. Waiting for the > resolution of the issue of "walking the zone" appears prudent. The debate about "walking the zone" has centered on whether this is actually an issue, luminaries such as Joe Abley and Bill Manning have suggested that it is not. Others, well DPF, has suggested that it is. ----------------------------------- The debate is much wider than this. It amounts to whether or not a technical standard circumvents a wider policy issue relating to access to the zone file and WHOIS data. It is an international debate - although as far as .nz is concerned it is an issue of local Internet community concern. There is a tension between those concerned with the technical issues relating to the DNSSEC standard and those concerned with public policy issues - the problem plainly arises from a failure on the part of the standards setters to take the wider policy issues into account... Unfortunate, but certainly understandable. Whether .geek.nz should have a difference policy set from the other unmoderated .nz 2LDs was debated at the time it was established... The outcome has been well canvassed on this list and I will not repeat it. The policy relating to release of the .nz zone file has been recently reviewed and all received views taken into account. The zone file will be released at the discretion of the NZOC and (ultimately) InternetNZ Council provided that there is a clear public interest and the party concerned is prepared to sign up to strict usage criteria. Timing (not the principle) of DNSSEC implementation is also under constant review. All of these matters have been debated in public, there are no hidden agendas, the only concerns have been the best stewardship of .nz in the interests of all Internet users and, especially, those reliant on the .nz DN space According to Robert Gray: <quote>That the society wishes to ignore the views, however well informed, of a "handful of NZNOGers" speaks volumes about the need for industry membership of InternetNZ. Why pay money to be ignored when you can be ignored for free.</quote> To which the only response I can make is that democracy does have its downside for those who find themselves in the minority. ---- Frank March Chair, .nz Oversight committee _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog http://www.govt.nz - connecting you to New Zealand central & local government services Any opinions expressed in this message are not necessarily those of the Ministry of Economic Development. This message and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivery to the intended recipient, be advised that you have received this message in error and that any use is strictly prohibited. Please contact the sender and delete the message and any attachment from your computer.

2 1

ns1,2,3,5.dns.net.nz hot being helpful
by Tim Nicholas 30 Sep '04

30 Sep '04

Hi all, Anyone know why ns1 ns2 ns3 and ns5.dns.net.nz aren't giving out useful information? That's 4 of 7 primary servers for all of .nz and seems to be affecting all of the second level domains. 22:35:04 tim(a)stella ~$ for i in 1 2 3 4 5 6 7; do host -t ns dnc.net.nz ns$i.dns.net.nz;echo; done dnc.net.nz NS record currently not present at ns1.dns.net.nz dnc.net.nz NS record currently not present at ns2.dns.net.nz dnc.net.nz NS record currently not present at ns3.dns.net.nz dnc.net.nz NS ns2.actrix.co.nz dnc.net.nz NS internetnz.net.nz dnc.net.nz NS ns1.actrix.co.nz dnc.net.nz NS record currently not present at ns5.dns.net.nz dnc.net.nz NS ns2.actrix.co.nz dnc.net.nz NS ns1.actrix.co.nz dnc.net.nz NS internetnz.net.nz dnc.net.nz NS internetnz.net.nz dnc.net.nz NS ns1.actrix.co.nz dnc.net.nz NS ns2.actrix.co.nz 22:37:40 tim(a)stella ~$ Cheers, Tim -- Tim Nicholas || Cilix Email: tim(a)nicholas.net.nz || Wellington, New Zealand http://tim.nicholas.net.nz/ || Cell/SMS: +64 21 337 204

17 42

Notification of NZRR Database changes
by NZRR Database Notifications 29 Sep '04

29 Sep '04

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. These objects are used to configure the APE and/or WIX route servers so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers, you will maintain at least one BGP session at all times and consequently a full set of APE and/or WIX routes. The update causing these changes had the following mail headers: - From: Andy Linton <asjl(a)citylink.co.nz> - Cc: - Subject: - Date: Thu, 30 Sep 2004 12:42:53 +1200 (NZST) - Msg-Id: <Pine.LNX.4.58.0409301238310.22181(a)jennings.citylink.co.nz> NZRR Database Notification Department --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 199.212.90.0/23, 199.212.92.0/23, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: asjl(a)wix.net.nz 20030407 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040831 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 198.32.66.0/24, 199.212.90.0/23, 199.212.92.0/23, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.240.0/23, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.41.136.0/22, 202.41.140.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: asjl(a)wix.net.nz 20030407 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040831 changed: rpsl-admin(a)wix.net.nz 20040930 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 199.212.90.0/23, 199.212.92.0/23, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: asjl(a)wix.net.nz 20030407 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040831 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS4770 descr: Route set for AS4770 members: 138.235.0.0/16, 192.107.113.0/24, 192.173.16.0/21, 198.32.66.0/24, 199.212.90.0/23, 199.212.92.0/23, 202.6.84.0/24, 202.12.70.0/24, 202.12.248.0/21, 202.14.100.0/24, 202.21.130.0/24, 202.21.136.0/23, 202.36.155.0/24, 202.36.157.0/24, 202.36.32.0/24, 202.36.36.0/22, 202.36.44.0/24, 202.36.45.0/24, 202.36.76.0/23, 202.37.136.0/24, 202.37.140.0/22, 202.37.144.0/21, 202.37.163.0/24, 202.37.197.0/24, 202.37.200.0/22, 202.37.224.0/21, 202.37.232.0/24, 202.37.240.0/23, 202.37.252.0/23, 202.37.76.0/24, 202.37.85.0/24, 202.41.136.0/22, 202.41.140.0/24, 202.49.62.0/24, 202.49.89.0/24, 202.49.249.0/24, 202.50.87.0/24, 202.50.246.0/24, 202.55.96.0/20, 202.74.224.0/21, 203.9.179.0/24, 203.9.180.0/24, 205.233.128.0/21, 205.233.136.0/23, 205.233.243.0/24, 210.185.0.0/18, 210.48.0.0/17, 210.54.136.0/22, 210.54.140.0/24, 210.54.160.0/19, 210.55.182.0/23, 210.55.24.0/22, 210.55.253.0/24, 210.56.32.0/20 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)ape.net.nz notify: nznog(a)list.waikato.ac.nz notify: john.johnston(a)iconz.net mnt-by: MAINT-NZRR-NZ changed: asjl(a)wix.net.nz 20030407 changed: rpsl-admin(a)wix.net.nz 20040629 changed: rpsl-admin(a)wix.net.nz 20040831 changed: rpsl-admin(a)wix.net.nz 20040930 source: NZRR

1 0

ICONZ Prefix update 20040930
by John Johnston 29 Sep '04

29 Sep '04

AS: 4770 APE: 192.203.154.44 WIX: 202.7.1.1 Guys, another prefix list update. Prefix list is attached or can be pulled from http://www.iconz.co.nz/prefix Cheers -- John Johnston Engineering Manager ICONZ New Zealand Limited DDI: +64 9 977 3500 FAX: +64 9 977 3535 Mobile: +64 21 277-5692 Email:john.johnston(a)iconz.net 0800 THE NET www.iconz.co.nz

1 0

Whois Server Policy Review
by Peter Macaulay 28 Sep '04

28 Sep '04

InternetNZ, through the Office of the Domain Name Commissioner, is reviewing the Whois Server Policy. All aspects of the policy are subject to this review. For more information, including a consultation paper, feedback form, and details about the review working group, please see: http://dnc.org.nz/whois-review Feedback is due by 5pm on Monday 1 November 2004, and comments will be published on the DNC website as they are received. -- Peter Macaulay Executive Director InternetNZ Direct +64 4 495 2113

1 0

Re: [nznog] so ... what is the real reason there is whois anyway?
by Ewen McNeill 28 Sep '04

28 Sep '04

NOTE: operational content here is marginal; replies in email may be best In message <20040929014242.GD5188(a)stateless>, Nicholas Lee writes: >How about restricting access to whois information via a >registration-required web interface, rate limit access dependant on >GeoIP location, and make it difficult for scripts. The New Zealand whois interface is already rate limited (as David mentioned). Taking away the traditional whois interface again (Domainz didn't provide it for a long time) and replacing it with a web interface will reduce the ability for legitimate users to use the traditional tools to look up information (which may be integrated into their workflow). But it won't make it any more difficult for someone who is determined to extract the information from the whois database; HTTP libraries are just as available as TCP/IP connection libraries these days. If you put in a registration step, then again you make it more difficult for someone who is legitimately trying to look up information without really making it more difficult for a scripted solution. If you add a "type in the text from this distorted image" step (eg, a captcha), then there is a proven workaround for such things -- you offer free pr0n to anyone that decodes one of those images, then feed the result back into the system. It's unlikely there'll ever be a short supply of people wanting free pr0n. If you "randomize" the output of the whois information, then you make the service more difficult for legitmate users to use, but again nothing that's particularly hard for a scraping script to work around (if the output is programatically generated then it's almost always programatically parsable, particularly if you only want a subset of the information and aren't too concerned about false parsing). Besides which only one scammer (or enterprising supplier of scammers) needs to extract this information; it can be sold or reused for quite a while after it's extracted. The "useful lifetime" of the information is probably in the order of 6-12 months, and if you get a few "good" scams through in that time, the effort to extract it easily pays off. Since most of the scams that have been effective have been paper-based, and since the main operational need is for an email contact or a phone number contact, possibly the most productive thing to do is review whether the physical address information is made available (by default). But ultimately I think that so long as there's money to be made (and gullible people available to be scammed), such things will continue to happen almost irrespective of how difficult one tries to make it to obtain the information -- at least up to the point where legitimate users have long since given up trying to use the service. And it's not always a good idea to substantially interfere with legitimate use just because of a small amount of illegitimate use. Ewen

1 0

OT: Laptop repairs.
by barry＠unix.co.nz 27 Sep '04

27 Sep '04

Hey guys, sorry to post off topic, just wanted to get a general idea on whats going on here. I bought a laptop 2months ago from Noel Lemmings, top of the range of the NEC model, shortly after getting it I had issues with software freezing etc and then the sound just stopped functioning. I tried installing other OSs on the laptop thinking it was just windows being its self, however the problem occurred on both FreeBSD and Debian linux. I sent the laptop in for repair (Theyve now had it close on 2 weeks) where they said they couldnt find a fault (typical) so I told them to keep it for a few more days. They then did find a fault and said it looked to be hardware related as per what I told them. They sent it in for repair where some other doofis tried to reinstall windows and then 2 days later said it was hardware related and it would take 5 days for a new MB to be sent from Malaysia. Well this morning I was called and asked if it would be alright if they could reinstall my laptop and did I want anything backed up; obviously no notes have been left with the laptop saying that its been reinstalled 11 times in the last 2 weeks and nothing is on the laptop. I call up this afternoon and ask when I can pickup the machine, they tell me that Malaysia dont have stock of my MB and Ill have to wait another 2 weeks before I might get my laptop back. When I asked if this was normal, they said yes, no laptop vendors keep stock in the country, only for desktops. So my questions are 1./ Should they be replacing the laptop with a new one 2./ Do hardware vendors never keep stock of parts in NZ (specially for a new range of equipment) 3./ How long should a laptop be in for repairs if its a P1 (Priority 1) job? Please reply directly. Thanks Barry ------------------------------------------------------------- This mail sent through UnixCo Webmail: http://www.unix.co.nz/

1 1

OT: A bit of a rash
by David Zanetti 27 Sep '04

27 Sep '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I know this is off-topic, so please excuse my stupidity in thinking anyone cares about this anyway. I recently partook of some "services", and now I've developed a bit of a rash. At first, I denied it existed, because that would make me unclean, but now it's ruined my life, and I'm losing my hair, and also my dog has developed a bit of an interest in the neighbours. Anyway, I thought I ask here, of all places, if: 1. How long does it normally take for rashes of a random and unspecified nature to go away? 2. What's the going rate for "services"? 3. Just how many people are going to use this list to air completely irrelevent issues ranging from end users with ADSL problems thru to completely offtopic posts about the service you get from random big name retail chains. [Aside: BTW, in case it's not obvious, I am of course joking about the rash. No really.] - -- David Zanetti | (__) #include <geek/unix.h> | ( oo Mooooooo http://hairy.geek.nz/ | /(_O ./ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFBWNqYT21+qRy4P+QRAveOAKCprXgFaYq2C3ZwAC5eMoPPmCx//gCfQgeE vuelU3xnDdmdscfLTDiFHgk= =r8aX -----END PGP SIGNATURE-----

1 0

RE: [nznog] Acceptable levels of Latency, Jitter and Packet loss on national links
by Craig Humphrey 27 Sep '04

27 Sep '04

That's all well and good, but since it's also the only "performance metrics" given in the contract, it's all I have to go on (hence soliciting references from existing customers). It would be nice to get an indication of what performance we can expect, not just "oh, it'll never get worse than this..." I've got a load of questions for the provider around these (and other) issues, so I'll just have to see what they come up with. Later'ish Craig > -----Original Message----- > From: Joe Abley [mailto:jabley(a)isc.org] > Sent: Tuesday, September 28, 2004 2:54 AM [snip snip] > It may actually be that the performance guarantee is a paper-dwelling > construct, and has little or no form in the actual network. > > I have certainly come across providers in my past for whom > performance > guarantees were necessary in order to be able to bid for > projects, but > the cost of deploying infrastructure to support the > guarantees was much > higher than just giving a few refunds now and then. As such the > guarantees didn't really exist outside the billing department. > > > Joe

1 0