- NZNOG - lists.nznog.org

Notification of NZRR Database changes
by NZRR Database Notifications 21 Nov '05

21 Nov '05

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 various NZIX route servers (http://nzix.net/) 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 at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS24189 descr: Route set advertised to AS9439 by IBM - AS24189 members: 202.36.192.0/22^22-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: scott.walsh(a)nz1.ibm.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051122 source: NZRR

1 0

Requirements for a Fast Uplink Internet Access
by Theodore＠ur1.com 18 Nov '05

18 Nov '05

We have an office in MT Wellington Auckland and we require a 256 or preferably a 512Mb Uplink Internet Line. Can anyone suggest, or does anyone know who might be able to provide such a service ? Any assistance is much appreciated. Thanks Theodore

6 7

Re: [nznog] Spammers Again (pricecutter.co.nz/brands4less.co.nz)
by Tim John 17 Nov '05

17 Nov '05

Thanks for the heads-up Craig. We will attempt to contact the Registrant of these names and verify the contact details at the least. Tim -----Original Message----- From: Craig Whitmore [mailto:lennon(a)orcon.net.nz] Sent: Tuesday, 8 November 2005 8:52 p.m. To: Cc: 4service(a)domainz.net.nz Subject: [nznog] Spammers Again (pricecutter.co.nz/brands4less.co.nz) People have been talking about this company lately... pricecutter.co.nz/brands4less.co.nz strike again and sends out their new batch of blatent spams today Recieved a load of spam this afternoon to email addresses which have not been used for over 7 years old. (The info on their website says they've only been running since 2005) pricecutter/brands4less registered to John Kyle (Cannot find any company owned by him) Calypso Records (cannot find any company called that) Address: 68 Lincoln Road, Henderson (This is The Lincoln Road Bible Chapel ) (I live 2 mins away and I checked !) Phone Number: 09 828 7890 (invalid number) (invalid exchange) Email: zxd(a)xtra.co.nz (when you email it you get back saying "Your email gas been removed. This is an automated message please do not reply." (same with Looks like same people as fitnessgear.co.nz with very similar style ads and invalid domain contacts and same hosting/ip address!! Be aware of this company.. (Search for brands4less.co.nz on google) I've also emailed their kliksend.com about this spam (or are they the same people and ignore me) Also.. can Domainz contact this customer of theirs and get some valid details for their domain as they are breaking Domainz's T&C and also I believe the DNC's for having false details. Thanks Craig Talking for Myself _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

2 2

Notification of NZRR Database changes
by NZRR Database Notifications 16 Nov '05

16 Nov '05

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 various NZIX route servers (http://nzix.net/) 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 at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051114 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051117 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 16 Nov '05

16 Nov '05

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 various NZIX route servers (http://nzix.net/) 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 at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9889 descr: advertised to AS9439 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051031 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9889 descr: advertised to AS9439 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051117 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 16 Nov '05

16 Nov '05

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 various NZIX route servers (http://nzix.net/) 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 at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: aut-num: AS24078 as-name: NZRR-AS24078 descr: TradeMe descr: APE peering at '192.203.154.18' descr: see Citylink RT job #2209 descr: WIX peering at '202.7.1.67' descr: see Citylink RT job #359 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24078 import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS24078 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050408 source: NZRR REPLACED BY: aut-num: AS24078 as-name: NZRR-AS24078 descr: TradeMe descr: APE peering at '192.203.154.18' descr: see Citylink RT job #2209 descr: WIX peering at '202.7.1.67' descr: see Citylink RT job #359 descr: WIX peering at '202.7.0.153' descr: see Citylink RT job #3725 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24078 import: from AS9560 accept ANY AND NOT fltr-bogons export: to AS9560 announce AS24078 import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24078 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051117 source: NZRR

1 0

100Mbps Internet for $150 per month
by Regan Murphy 15 Nov '05

15 Nov '05

"It's just a no-brainer these days," says InternetNZ president Colin Jackson of Wellington CBD businesses' attitude to using the CityLink service. "It costs you a few grand for a router and about $150 a month. For that you get [a connection speed of] 100 megabits per second. There's none of this metered bandwidth or anything." http://www.nzherald.co.nz/section/story.cfm?c_id=5&objectid=10355213 I always knew Citylink had a great product, but i never realised it was so cheap... -- Regan

6 6

Notification of NZRR Database changes
by NZRR Database Notifications 13 Nov '05

13 Nov '05

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 various NZIX route servers (http://nzix.net/) 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 at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9727 descr: advertised to AS9439 by Quicksilver Internet - AS9727 members: 202.89.128.0/19^19-29, 202.37.90.0/23^23-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: pjs(a)quicksilver.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051104 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9727 descr: advertised to AS9439 by Quicksilver Internet - AS9727 members: 202.89.128.0/19^19-29, 202.49.240.0/22^22-29, 202.37.90.0/23^23-29, 202.14.217.0/24^24-29, 202.49.59.0/24^24-29, 202.50.176.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)quicksilver.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051114 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 13 Nov '05

13 Nov '05

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 various NZIX route servers (http://nzix.net/) 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 at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9872 descr: Route set advertised to AS9560 by Actrix - AS9872 members: 202.154.128.0/19^19-24, 203.96.16.0/20^20-24, 203.96.48.0/20^20-24 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mikej(a)connections.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040809 changed: rpsl-admin(a)nzix.net 20040810 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9872 descr: advertised to AS9560 by Actrix Networks - AS9872 members: 202.154.128.0/19^19-29, 203.96.16.0/20^20-29, 203.96.48.0/20^20-29, 202.36.204.0/23^23-29, 192.100.53.0/24^24-29, 202.49.158.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051114 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 13 Nov '05

13 Nov '05

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 various NZIX route servers (http://nzix.net/) 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 at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051028 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051114 source: NZRR

1 0

paypal phishing site
by Ian Batterbee 11 Nov '05

11 Nov '05

Have seen a few spams that has all the paypal images (even gets the images from the real paypal site) and lists a bunch of dummy IP addresses that my paypal (I don't have one) account was apparently used from recently, and encourages me to click on the given URL, which goes to [http://www.paypal.update-user-form.com/] Any request to *.update-user-form.com gets redirected to [http://www.paypal.update-user-form.com/webscr.php?cmd=LogIn] and the domain resolves to the following six IP addresses: 68.142.234.[52..57], which all seem to belong to Yahoo. God knows how people get away with registering DNS entries for sites that couldn't be used for anything other than phishing attempts.. I guess someone thought update-user-form.com looked innocent enough.

1 0

Re: [nznog] Paradise.Net SMTP server blocked.
by Simon Byrnand 10 Nov '05

10 Nov '05

At 10:31 10/11/2005, Mark Foster wrote: > > "Your server is not an open relay, but you have a user that is > > infected with a mass-mailer trojan/malware" > > > > (and finally a copy of some message headers that prove it) > > >Was this the honest-to-god reason? Yes, that was a verbatim quote from the message. >I thought that most malware did its own MX lookups and relayed directly? >Aka bypassing the SMTP relay provided by infected-parties ISP? I thought so too, but obviously some don't. >Given the sheer volume of smtp-crud that a lot of people see, it wouldnt >suprise me that large blocks get put in sooner rather than later. > >In some respects though, SORBS's policy is actually reasonably well >thought out. Entries get a TTL of 2 days and if now further 'hits' on the >IP are received, the TTL auto-expires and the block comes off. TTL gets >renewed each time a further report is received. The spamcop list auto-removes you after sometime between 12 and 24 hours too, but the problem as I see it is that they rely on unverified user entered "reports" so potentially you could keep getting unfairly listed over and over without any real comeback... Regards, Simon

2 1

Re: [nznog] Paradise.Net SMTP server blocked.
by Simon Byrnand 09 Nov '05

09 Nov '05

At 16:45 10/11/2005, Andrew Stephen wrote: >On 11/10/05, Lesley Walker <lrw(a)clear.net.nz> wrote: > > Simon Byrnand wrote: > > > Not only that, but the sample message header they provided > > > had many of the message fields obfuscated, including the > > > message id tag and the time, making it extremely > > > > The reason they obfuscate some of the fields is that in some > > cases the report could be going to the spammers themselves, > > and the concern is that spammer will be able to identify the > > user who reported them and exact some kind of revenge. > >Ah, yeah. That happens. I received several death threats after >reporting some spam a year or so ago. Nothing happened (and I didn't >really expect it to) but it does make one wary. In my case however it wasn't a person(s) reporting the message, it was one of their honeypot addresses that the spam was sent to, and they claimed in a later email that the obfuscation was to protect the honeypot address. Fair enough, except it didnt seem to dawn on the guy that if I couldn't work it out from my mailserver logs thanks to their obfuscation then I couldn't find the customer with the trojan to do anything about it, and on the other hand that if I could figure it out by deduction (which I did) that the honey pot address would be in my log files anyway and thus compromised if I were a spammer :) Security by obscurity ? :) Regards, Simon

1 0

Re: [nznog] Paradise.Net SMTP server blocked.
by Lesley Walker 09 Nov '05

09 Nov '05

Simon Byrnand wrote: > Not only that, but the sample message header they provided > had many of the message fields obfuscated, including the > message id tag and the time, making it extremely The reason they obfuscate some of the fields is that in some cases the report could be going to the spammers themselves, and the concern is that spammer will be able to identify the user who reported them and exact some kind of revenge. IIRC, the munging is set on a per-user basis by the users reporting spam. Some Spamcop users will argue that the spammer could be using a database to key the message id and timestamp to the recipient address. (I tend to think this is excessively paranoid, but some vigilante anti-spammers probably have good reason to exhibit this level of paranoia.) The other thing to bear in mind is that they have no way of knowing which ISPs are "spam-friendly" (ie very happy to recieve payment for the bandwidth used by spammers), which many Spamcop users regard as being just as evil as the spammers themselves and completely worthy of blocking. > I strongly suggest that people DONT do SMTP level blocks > using spamcop lists, as they are simply not trustworthy > enough, I only use spamcop as a points scoring mechanism > in spamassassin, I've never trusted it for outright > blocking... Indeed, Spamcop's own advice to users of the list includes the comments: "SpamCop encourages SCBL users to tag and divert email, rather than block it outright" and "The SCBL is aggressive and often errs on the side of blocking mail." (Quoting http://www.spamcop.net/bl.shtml) If anyone wants to get into a discussion with Spamcop about the issues, you could try their news server at news.spamcop.net. If you have time to spare, that is. Lesley W

2 1

Apology - Rod Donald Funeral
by Richard Naylor 09 Nov '05

09 Nov '05

A BIG sorry to Operators who may have been affected by higher than usual traffic this morning. As you know we like to issue pre-event warnings of potential traffic or support issues. Today we supported the streaming of the Rod Donald Funeral Webcast, picking up the load mid-event and using anycast routing to distribute the load. So we didn't get much warning either. The decision was made on the phone as we worked setting things up. While not a huge event, it did produce a higher than normal load. There was a steady 45Mbps coming out of our USA server, peaking to 85Mbps. ISPs *really, really* should peer to avoid this cost and also help us service the international viewers. It reflects badly on them internationally. There are at least 4 more significant events before the end of the year, so Operators are strongly urged to peer. Once again - sorry if your traffic graph got a nasty kink in it today. Rich

1 0

Re: [nznog] Paradise.Net SMTP server blocked.
by Ewen McNeill 09 Nov '05

09 Nov '05

In message <40972.203.97.112.6.1131571888.squirrel(a)webmail.blakjak.net>, "Mark Foster" writes: >I thought that most malware did its own MX lookups and relayed directly? >Aka bypassing the SMTP relay provided by infected-parties ISP? There's at least one common variant around now which seems to relay via the ISP mail servers. I notice it mainly through the reflections, including some where that ISP's mail server apparently tried to deliver to some nonexistant user at my domain, got rejected, and so instead delivers a bounce message to the (forged) from address at the same domain (which happens to exist; if that one didn't exist either I'd never see it). I'm not sure how much longer relaying mail without scanning it first (and rejecting anything that doesn't pass at SMTP time) is going to be a viaable strategy for both incoming and outgoing mail relays. Either that or dynamic IP addresses going away, so it's possible to assign reputation right back to the originating machine. Ewen

1 0

Paradise.Net SMTP server blocked.
by Steve Biddle 09 Nov '05

09 Nov '05

After experiencing email problems I've noticed Paradise's SMTP server is currently being blocked by SpamCop. http://www.spamcop.net/w3m?action=checkblock&ip=203.96.152.177 Anybody got any comments? These email problems have been ongoing over the last few weeks so I suspect the server (smtp1.paradise.net.nz) has been on the list for some time.

6 5

Re: [nznog] Paradise.Net SMTP server blocked.
by Nic Wise 09 Nov '05

09 Nov '05

> Warning, rant ahead. :) I see your rant, and raise you a rant and a beer (just to keep it ontopic) At my previous job, we moved from a single IP connection to a block of 8. Problem was, one of the addresses in the "new" block of 8 was black listed - and guess which one we put the mail server on <sigh> Got it cleaned up, but no outgoing (without a work around) for 48 hours. That said, on the RBL list on my server, I removed SpamCop. Why? Too many false positives, and WAY too many false negatives (letting spam in). It's close to useless.... (and there are other, GOOD ones, out there) Cheers Nic

1 0

Re: [nznog] Paradise.Net SMTP server blocked.
by Nic Wise 09 Nov '05

09 Nov '05

Paradise gets blocked about once a month (or more, some times). I've had to put a rule in, allowing *(a)paradise.net.nz :) (there again, my server is not huge - 2 users - so not really an issue for me :) ) I assume their admins are aware, as they appear to normally be on the ball..... I'm guessing they are now, anyway! Cheers Nic -- Nic Wise - Senior Developer - Microsoft MVP (.NET) AfterMail Limited > -----Original Message----- > From: Steve Biddle [mailto:sjbiddle(a)paradise.net.nz] > Sent: Wednesday, 9 November 2005 6:07 p.m. > To: nznog(a)list.waikato.ac.nz > Subject: [nznog] Paradise.Net SMTP server blocked. > > > > > After experiencing email problems I've noticed Paradise's > SMTP server is currently being blocked by SpamCop. > > http://www.spamcop.net/w3m?action=checkblock&ip=203.96.152.177 > > Anybody got any comments? These email problems have been > ongoing over the last few weeks so I suspect the server > (smtp1.paradise.net.nz) has been on the list for some time. > > > > > > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 08 Nov '05

08 Nov '05

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 various NZIX route servers (http://nzix.net/) 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 at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- OBJECT BELOW CREATED: aut-num: AS24183 as-name: NZRR-AS24183 descr: DTS1 descr: WIX peering at '202.7.0.143' descr: see Citylink RT job #3580 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24183 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: milton(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051109 source: NZRR

1 0

Update: Systems Administration Miniconf, linux.conf.au 2006.
by Simon Lyall 07 Nov '05

07 Nov '05

An update and 2nd Call for papers. The Systems Administration Miniconf will be part of the linux.conf.au conference to be held in Dunedin, New Zealand in January 2006 . We have had a good response to our first call for papers and have accepted several great presentations. In addition we have several others submitted after the early deadline or which didn't quite make the first cut. Please see http://sysadmin.miniconf.org/program.html for our draft programme or http://sysadmin.miniconf.org/presentations.html for more details on the accepted presentations. A reminder that we are still accepting proposals for presentations until at least the 18th of November. Presentations can be lightning talks or full presentations between 30 and 120 minutes. See: http://sysadmin.miniconf.org/cfp.html for details. Topics for presentations could include (but are not limited to) Samba, Databases, Backups, Firewalls, AAA, Troubleshooting, Buying Decisions, VPN, Virtual machines (Xen, UML, VMware), Monitoring Software, Web/Mail/LDAP/etc Server software, Wikis, PHP, Spam and Virus Filtering, VOIP, Trouble Ticket System, Best Practices, New Developments, Clustering/High Availability , Automated Installs, Automated configuration, Packaging Local Software. Speakers should assume that members of the audience have at least a couple of years experience in Unix/Linux administration. Format of Presentations ----------------------- Presentations of between 30 and 120 minutes (including questions) or Lightning Talks of 5-10 minutes. Submitting talks ---------------- Please note that in order to give a presentation you must be signed up for the main linux.conf.au conference. In order to submit a talk please see our Call for Presentations web page at: http://sysadmin.miniconf.org/cfp.html Submissions (or any questions) should be sent to: contact @ sysadmin.miniconf.org. Dates and Deadlines ------------------- 18 Nov 2005 - Deadline for Submissions Contact and Questions --------------------- Please see our website at http://sysadmin.miniconf.org/ for more information on the miniconf and presenting at it. If you have any questions please feel free to email the organisers at: contact @ sysadmin.miniconf.org

1 0

Spammers Again (pricecutter.co.nz/brands4less.co.nz)
by Craig Whitmore 07 Nov '05

07 Nov '05

People have been talking about this company lately... pricecutter.co.nz/brands4less.co.nz strike again and sends out their new batch of blatent spams today Recieved a load of spam this afternoon to email addresses which have not been used for over 7 years old. (The info on their website says they've only been running since 2005) pricecutter/brands4less registered to John Kyle (Cannot find any company owned by him) Calypso Records (cannot find any company called that) Address: 68 Lincoln Road, Henderson (This is The Lincoln Road Bible Chapel ) (I live 2 mins away and I checked !) Phone Number: 09 828 7890 (invalid number) (invalid exchange) Email: zxd(a)xtra.co.nz (when you email it you get back saying "Your email gas been removed. This is an automated message please do not reply." (same with Looks like same people as fitnessgear.co.nz with very similar style ads and invalid domain contacts and same hosting/ip address!! Be aware of this company.. (Search for brands4less.co.nz on google) I've also emailed their kliksend.com about this spam (or are they the same people and ignore me) Also.. can Domainz contact this customer of theirs and get some valid details for their domain as they are breaking Domainz's T&C and also I believe the DNC's for having false details. Thanks Craig Talking for Myself

1 0

Short notice of webcast
by Richard Naylor 05 Nov '05

05 Nov '05

Evening All, The following webcasts will take place this week at rather short notice (friday night). I doubt there will be huge traffic, but better warned...... On Monday and Tuesday, we will be streaming the 2 Opening ceremonies of Parliament, live from the grounds. (There will be cameras inside as well, just we'll be outside) The links for the streams are on http://www.r2.co.nz/20051107 Rich

1 0

Re: [nznog] DNS Servers and peering
by Webmaster 04 Nov '05

04 Nov '05

That'll teach me for being naive. I take it you meant that they are unrelated. R. >>> Joe Abley <jabley(a)isc.org> 11/05/05 4:10 PM >>> > Apologies if I appear pedagogical :-) _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

DNS Servers and peering
by Webmaster 04 Nov '05

04 Nov '05

A naive question: With the limiting of recursion (which appears to be a Good Thing) does it make it more (or less) important to have good network diversity (hint:peering) ? Or does it not matter? Richard >>> "Simon Allard" <simon.allard(a)staff.ihug.co.nz> 11/04/05 8:00 PM >>> Rob is correct (as always, Hi Rob!) There has been a plee on the ISP jungle drum network, to limit recursive DNS servers to protect the internet from evil doers. IHUG will be following very shortly, will post on here and give some notice before limiting the use of 203.109.252.42/43. Cheers, Simon Allard IHUG > -----Original Message----- > From: Rob Thomas [mailto:robt(a)cymru.com] > Sent: Friday, 4 November 2005 7:39 p.m. > To: NZNOG List > Subject: Re: [nznog] Inspire Net name servers > > Hi, team. > > ] http://www.theregister.co.uk/2005/10/24/dns_security_survey/ > > Might I also suggest: > > <http://www.dyndns.com/about/company/notify/archives/the_dangers_of_open _r > ecursive_dns.html> > > Thanks, > Rob. > -- > Rob Thomas > Team Cymru > http://www.cymru.com/ > ASSERT(coffee != empty); > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

4 4

Google Oddness
by Mark Foster 04 Nov '05

04 Nov '05

; <<>> DiG 9.2.1 <<>> www.google.com A ;; global options: printcmd ;; connection timed out; no servers could be reached ns1.google.com through ns4.google.com are as follows: ns1.google.com. IN A 216.239.32.10 ns2.google.com. IN A 216.239.34.10 ns3.google.com. IN A 216.239.36.10 ns4.google.com. IN A 216.239.38.10 I can't get to any of those. Wonder if 216.239/16 has dissapeared off the net? traceroute to 216.239.32.10 (216.239.32.10), 30 hops max, 38 byte packets 1 akl-colo1.helix.net.nz (202.50.176.78) 42.880 ms 0.222 ms 0.171 ms 2 202-49-59-254.level48.net (202.49.59.254) 0.450 ms 0.354 ms 0.324 ms 3 qsi2.ape.net.nz (192.203.154.29) 2.005 ms 0.662 ms 0.853 ms 4 gateway3-acc-skyt.qsi.net.nz (202.89.128.91) 26.475 ms * 4.674 ms 5 Mercury-Quicksilver-FE-1-0-0-402-ar1.akl1.gblx.net (203.192.179.9) 4.059 ms 3.245 ms 3.954 ms 6 po0-0.gw2.sjc1.asianetcom.net (202.147.50.130) 156.300 ms 155.490 ms 158.930 ms 7 72.14.197.37 (72.14.197.37) 156.797 ms 159.034 ms 158.760 ms 8 * * * Problem exists from both QSI and GGI... Mark.

4 3

Inspire Net name servers
by Mark Seward 03 Nov '05

03 Nov '05

ns1.inspire.net.nz (203.114.128.1), and ns2.inspire.net.nz (203.114.128.2) now accept recursive and cached queries from Inspire Net customers only. Queries for domains that ns1 and ns2 are authoritative for are unaffected. Mark Seward Inspire Net Ltd.

7 9

Re: [nznog] Inspire Net name servers
by Simon Allard 03 Nov '05

03 Nov '05

Rob is correct (as always, Hi Rob!) There has been a plee on the ISP jungle drum network, to limit recursive DNS servers to protect the internet from evil doers. IHUG will be following very shortly, will post on here and give some notice before limiting the use of 203.109.252.42/43. Cheers, Simon Allard IHUG > -----Original Message----- > From: Rob Thomas [mailto:robt(a)cymru.com] > Sent: Friday, 4 November 2005 7:39 p.m. > To: NZNOG List > Subject: Re: [nznog] Inspire Net name servers > > Hi, team. > > ] http://www.theregister.co.uk/2005/10/24/dns_security_survey/ > > Might I also suggest: > > <http://www.dyndns.com/about/company/notify/archives/the_dangers_of_open _r > ecursive_dns.html> > > Thanks, > Rob. > -- > Rob Thomas > Team Cymru > http://www.cymru.com/ > ASSERT(coffee != empty); > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Re: [nznog] Google Oddness
by Lesley Walker 02 Nov '05

02 Nov '05

> Google Groups has fallen over now. And it's back. LW.

1 0

Re: [nznog] Google Oddness
by Lesley Walker 02 Nov '05

02 Nov '05

Google Groups has fallen over now. ----- Original Message Follows ----- > On 03/11/05, Mark Foster <blakjak(a)blakjak.net> wrote: > > > > I can't get to any of those. Wonder if 216.239/16 has > > dissapeared off the net? > > > Seems to be a widespread problem at google - gmail was > down as well but coming up now.... > -- > Ian McDonald > http://wand.net.nz/~iam4 > WAND Network Research Group > University of Waikato > New Zealand > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Update to Telecom Xtra DNS servers
by Ted Grenfell 02 Nov '05

02 Nov '05

As part of our ongoing DNS service improvements, Telecom is making some changes to it's DNS servers which will affect some non-Telecom customers. The following Xtra name servers will in future only accept queries from Non-Telecom customers for domains that the name servers are authoritative for. Recursive queries for other domains (e.g. www.google.com) will no longer work. * dnsh1.xtra.co.nz ( 202.27.184.3 ) also known as alien.xtra.co.nz * dnsh2.xtra.co.nz ( 202.27.184.5 ) also known as terminator.xtra.co.nz We will be phasing in these changes from November 15th over a period of several weeks and you may wish to alert your help desks to check the DNS settings of users having problems after that. Currently Xtra operates the following recursive DNS services: * dnsc1.xtra.co.nz ( 202.27.158.40 ) * dnsc2.xtra.co.nz ( 202.27.156.72 ) We are happy for external people to query those IP's for DNS troubleshooting and similar purposes but they should not be directly configured into machines. Please note these IP's may change from time to time and external access may be limited or withdrawn without prior warning (especially in cases of abuse). Regards, -- Ted Grenfell, ISP Performance Manager, IS Online Services, Telecom NZ Ltd Mob: +64 274 435 455; DDI: +64 9359 5854; Fax: +64 9377 0781; Pager: +64 2611 1445 ICQ: 191891; MSN Messenger: cameleon @ xtra.co.nz Level 11, 8 Hereford St, Private Bag 92028, Auckland CBD, New Zealand "today was so quiet, you could hear a packet drop" - Tom Liston, ISC Handler's Diary This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.

9 11

Re: [nznog] Update to Telecom Xtra DNS servers
by Ted Grenfell 01 Nov '05

01 Nov '05

There are stats but we do not have a view on the exact numbers of people who have configured alien and terminator as their DNS. There will be some and they will be impacted in some way from recursion being disabled. Hence the heads up. Regards, Ted Grenfell ISP Performance Manager IS Online Services T 09 359 5854 F 09 377 0781 M 0274 435 455 E ted.grenfell(a)telecom.co.nz W www.telecom.co.nz Level 11, Telecom House, 8 Hereford St, Private Bag 92028, Auckland, New Zealand ________________________________ "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002." -----Original Message----- From: Brian Gibbons [mailto:brian(a)outersite.co.nz] Sent: Wednesday, 2 November 2005 1:46 p.m. To: Joe Abley Cc: Ted Grenfell; NZNOG Subject: Re: [nznog] Update to Telecom Xtra DNS servers >From: "Joe Abley" <jabley(a)isc.org> > Unless Xtra's planned configuration is particularly unusual, >I would imagine they would return answers from the cache >where they exist, return authoritative answers in the case of >queries that they have authoritative data for, and otherwise >return a referral to the root. "no answers" is the usual "not here" reply (like ns1.ihug.co.nz) And therein lies the problem. For a non Xtra user, that has Xtra DNS servers hard coded, 90% of DNS requests will probably work because Xtra's servers have much of the nz internet namespace in their cache, (or the servers are authorititive) The IP address 202.27.184.3 is a virus, it seems have spread into the configurations of many NZ computers, I think it is one of those "it just works" scenarios and computer technicians have used it as a default fix for many "wierd" DNS issues. Once Xtra disable recursion for non Xtra customers, those same techncians will be challenged with trying to diagnose a very intermittent "page can not be displayed" fault. Ted, if we assume this change is being made because there are a significant number of requests (relative to the size of your user base) coming from non Xtra IP addresses, then we would have to assume that a significant number of users (that have dumb client resolvers) are going to be affected. Are there any statistics available from your name servers on the scale of this issue (Like is it 10% non Xtra requests?) Cheers BG

1 0

Re: [nznog] Update to Telecom Xtra DNS servers
by Ted Grenfell 01 Nov '05

01 Nov '05

All IP's mentioned in my previous email are still accepting queries. Nothing has yet been implemented as we wanted to ensure advance notice was given so I'm not sure why you were getting 440's sorry. Regards, Ted Grenfell ISP Performance Manager IS Online Services T 09 359 5854 F 09 377 0781 M 0274 435 455 E ted.grenfell(a)telecom.co.nz W www.telecom.co.nz Level 11, Telecom House, 8 Hereford St, Private Bag 92028, Auckland, New Zealand ________________________________ "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002." -----Original Message----- From: Regan Murphy [mailto:regan.murphy(a)oasystems.co.nz] Sent: Wednesday, 2 November 2005 10:19 a.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Update to Telecom Xtra DNS servers >>What action will those servers take when they receive a request from a non Xtra IP? I forgot to switch the forwarded on one of my dns servers away from xtra when I changed ISPs and last week (or the previous week?) I couldn't resolve any non-xtra/telecom queries.. I just got request denied (440?) errors. I have since fixed my forwarder entry but I would suggest that the change was already made (or maybe the change was made and it was subsequently rolled back in favour of a public notice) -- Regan _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

2 1

Re: [nznog] Update to Telecom Xtra DNS servers
by Regan Murphy 01 Nov '05

01 Nov '05

>>What action will those servers take when they receive a request from a non Xtra IP? I forgot to switch the forwarded on one of my dns servers away from xtra when I changed ISPs and last week (or the previous week?) I couldn't resolve any non-xtra/telecom queries.. I just got request denied (440?) errors. I have since fixed my forwarder entry but I would suggest that the change was already made (or maybe the change was made and it was subsequently rolled back in favour of a public notice) -- Regan

1 0

Re: [nznog] Update to Telecom Xtra DNS servers
by Ted Grenfell 01 Nov '05

01 Nov '05

Most likely your option 3 Brian. There can be expected that there will be some customers who'se interweb thingy appears to die on them. Hence our advance notice. -----Original Message----- From: Brian Gibbons [mailto:brian(a)outersite.co.nz] Sent: Wednesday, 2 November 2005 9:19 a.m. To: Ted Grenfell; NZNOG Subject: Re: [nznog] Update to Telecom Xtra DNS servers >From: "Ted Grenfell" <Ted.Grenfell(a)telecom.co.nz> > The following Xtra name servers will in future only accept queries >from Non-Telecom customers for domains that the name servers are > authoritative for. > * dnsh1.xtra.co.nz ( 202.27.184.3 ) also known as alien.xtra.co.nz > * dnsh2.xtra.co.nz ( 202.27.184.5 ) also known as terminator.xtra.co.nz What action will those servers take when they receive a request from a non Xtra IP? Will they : 1. Quietly discard the request (as in, blocked by a front end firewall) 2. Return a referal to another DNS server e.g. .co.nz etc. 3. Return "invalid domain name" Cheers BG Regards, Ted Grenfell ISP Performance Manager IS Online Services T 09 359 5854 F 09 377 0781 M 0274 435 455 E ted.grenfell(a)telecom.co.nz W www.telecom.co.nz Level 11, Telecom House, 8 Hereford St, Private Bag 92028, Auckland, New Zealand ________________________________ "This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002."

1 0

Re: [nznog] Melbourne Cup Streaming
by Webmaster 31 Oct '05

31 Oct '05

We are carrying audio on National Radio at 5pm: www.radionz.co.nz regards, Richard Hulse >>> "Regan Murphy" <regan.murphy(a)oasystems.co.nz> 1/11/2005 15:06 >>> Are there any localised streams for the Melbourne Cup race? -- Regan _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

1 0

Melbourne Cup Streaming
by Regan Murphy 31 Oct '05

31 Oct '05

Are there any localised streams for the Melbourne Cup race? -- Regan

1 0

The New Zealand Network Operators' Group
by Donald Neal 31 Oct '05

31 Oct '05

The New Zealand Network Operators' Group The New Zealand Network Operators' Group (NZNOG) has no king, president or formal membership. It consists of the subscribers to this mailing list, which anyone is free to join. Conference Our next conference is to be held in Wellington on 22-24 March, 2006. That's the week before the scheduled ICANN meeting. See http://www.nznog.org/ for more information. The call for presentations officially closes today, so please contact me off list if you'd like to present and haven't already indicated your interest. Other Meetings See http://auckland.thursdaynightcurry.com/ or http://wellington.thursdaynightcurry.com/ if you live in or near Auckland or Wellington. Operators' Contact List See http://www.usenet.net.nz/noc/ for operational contact details for most New Zealand ISP's. These are intended for use by other network operators, not by most customers. Internet Exchanges See http://nzix.net/ for details of exchanges in operation, and some information on others under construction. About This Mailing List This list has around 850 addresses subscribed. You may only post to the list from a subscribed address. A number of people subscribe addresses which do not receive email purely to allow posting from them. You may choose to receive postings as they come in, or just to receive daily "digests". See the bottom of the page http://list.waikato.ac.nz/mailman/listinfo/nznog/ to change the form in which you receive postings. The NZNOG mailing list is provided through a server at The University of Waikato, and is administered by employees of Alcatel NZ Ltd, Citylink and Telecom. None of these organisations, nor any administrator, is responsible for its content. NZNOG Mailing List Acceptable Use Policy The NZNOG mailing list exists to provide a forum for the exchange of technical information and the discussion of implementation issues that require cooperation among New Zealand network service providers. In order to continue to provide a useful forum for discussion of relevant technical issues, users of the list are asked to respect the following guidelines. 1. Discussion will focus on Internet operational and technical issues. 2. Discussion related to meetings of network service providers is appropriate. 3. Discussion unrelated to these topics is not appropriate. 4. Postings to multiple mailing lists are discouraged. 5. Postings that include foul language, character assassination, and lack of respect for other participants are unacceptable. 6. Blatant product or service marketing is unacceptable. 7. Postings of a political, philosophical or legal nature are discouraged. 8. Postings to the list should be in ASCII or MIME encoded as text/plain. Attachments should not be sent to the list. To present a document, a suitable URL may be referred to. For documents of general interest, the use of proprietary file formats is discouraged. 9. Breaches of list etiquette should be dealt with privately with the offending list user, and should not result in complaints being sent to the list. 10. A person repeatedly breaching list etiquette shall receive warnings from the list administrator. A further breach after the second such warning within thirty days shall result in the offender being unsubscribed from the list. Other action may also be taken to block postings to the list by the offender. Any such unsubscription is to be immediately announced to the list. Mailing List Archives A full archive is available at http://list.waikato.ac.nz/pipermail/nznog/ Any message sent to the list will be archived and made available on the web automatically. Changes are not made to the archive on request, though the administrators remain happy to assist the Office of the Privacy Commissioner should any complaint be laid with that office. One way to search the archive is to use google and prefix your search With site:list.waikato.ac.nz . Subscribing to the List See http://list.waikato.ac.nz/mailman/listinfo/nznog to subscribe. Donald Neal NZNOG Mailing List Owner/Administrator/Muggins This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 30 Oct '05

30 Oct '05

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 various NZIX route servers (http://nzix.net/) 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 at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS64549 descr: advertised to AS9439 by Executive Government Support - AS64549 members: 202.68.87.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: network.manager(a)egs.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051027 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64549 descr: advertised to AS9439 by Executive Government Support - AS64549 members: 202.68.87.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: network.manager(a)egs.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051031 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 30 Oct '05

30 Oct '05

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 various NZIX route servers (http://nzix.net/) 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 at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route: 202.154.128.0/19 descr: Route for Actrix - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mikej(a)connections.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040809 source: NZRR REPLACED BY: route: 202.154.128.0/19 descr: Route for Actrix Networks - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: noc(a)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051031 source: NZRR --- PREVIOUS OBJECT: route: 203.96.16.0/20 descr: Route for Actrix - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mikej(a)connections.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040809 source: NZRR REPLACED BY: route: 203.96.16.0/20 descr: Route for Actrix Networks - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: noc(a)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051031 source: NZRR --- PREVIOUS OBJECT: route: 203.96.48.0/20 descr: Route for Actrix - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: mikej(a)connections.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20040809 source: NZRR REPLACED BY: route: 203.96.48.0/20 descr: Route for Actrix Networks - AS9872 origin: AS9872 notify: rpsl-admin(a)nzix.net notify: noc(a)actrix.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051031 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 30 Oct '05

30 Oct '05

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 various NZIX route servers (http://nzix.net/) 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 at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9889 descr: advertised to AS9439 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051028 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9889 descr: advertised to AS9439 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051031 source: NZRR

1 0

MX2 with SPF
by Joel van Velden 29 Oct '05

29 Oct '05

Hi all I've been having a problem lately of getting far too much spoofed email being sent with my email address directly to our secondary mx which tries delivering it to our primary which 550's it (unknown user) and thus I get the bounce. To solve this I thought about doing the SPF thing for our domains, but this wouldn't solve the above problem unless the secondary mx does SPF as well. Because of various reasons we are using an ISPs seconday mx server for our domains, and thus have no control of that servers configuation. What i'm really asking is, does anybody know of someone selling a secondary mx service with SPF enabled? Cheers Joel van Velden

3 2

Notification of NZRR Database changes
by NZRR Database Notifications 27 Oct '05

27 Oct '05

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 various NZIX route servers (http://nzix.net/) 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 at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.155.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050721 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051028 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 27 Oct '05

27 Oct '05

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 various NZIX route servers (http://nzix.net/) 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 at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9889 descr: advertised to AS9439 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.155.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050721 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9889 descr: advertised to AS9439 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051028 source: NZRR

1 0

NZNOG 2006 - October Update.
by Simon Lyall 26 Oct '05

26 Oct '05

1. Dates. The conference is now less than 5 months away, from 22 March to 24 March, just before the Wellington ICANN meeting Call for Papers close next week, if you wish to have your talk given full consideration then please send us something before then. Squeezing in after that date will be much harder. http://www.nznog.org/cfp.html Even if you only send us a brief description then your presentation will still be considered. 2. Sponsorship. We wish to apologise to those people who have emailed us and not heard back. Due to various factors we have not got back to you yet, this is being worked on and should hopefully be sorted out soon. :( 3. General. We are in the process of finalizing venues for the main conference, dinners and the like. Most of it is looking fairly promising if not always as cheap as we would hope. We have had several good talk proposals, however there is still some room in the programme especially for lightning talks. Wednesday is looking more and more like becoming a full or half day of normal conference. Finally if you have any general, off the wall or other ideas please email us now as things will start being settled soon. We have had a couple of good suggestions already. -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 0

Re: [nznog] Voip response
by chris＠archnetnz.com 26 Oct '05

26 Oct '05

Anyone want to tell him, or can I???? Callplus, own iTalk and slingshot.. so yes, they most likly do use the same ISDN's as iTalk... $9.95 a month is quite a good deal for an Auckland number, I would just like a Wellington number.. but who knows when that will be avilable... > Sipserve doesn't use the same PRI's, they have their own, provided by > callplus (afaik). > > The standard italk prefix of 974 is assigned to callplus in all area codes > except 06, where it is taken by TelstraClear. > > iTalk told everyone in September that it would be ready in 2 or 3 months, > yet people are still sending typical "where the hell is it" emails/forum > posts, and also have the nerve to go "oh btw, we want to pay less." > > People are assholes. > > > ________________________________________ > From: Barry Murphy > Sent: Thursday, 27 October 2005 4:20 p.m. > To: will(a)excom.net.nz > Subject: [nznog] Voip response > > Hi, > > Many of you (over 30 people) were interested in a response to my VoIP > DDI's question to the NZNog. I should have responded earlier but I was > hoping more providers would email me back, plus I've been on holiday the > last week (wahoo!). > > Well unfortunately I only had 2, unless I missed any, but it would seem > italk.co.nz and sipserve.co.nz are the only 2 providers and with number > ranges in 09 & 04. > > Italk - well they not yet selling 04 numbers from what I understand, they > working on the billing platform still. I'm currently using their 09 > service and it's great, call quality is perfect, fax over IP works, prices > aren't bad. > > Sipserve - these guys say they doing 04, however I know someone that > emailed them a week ago to get some and they still haven't + their support > is a bit slow and their system doesn't support fax over IP. > > One other thing to think about is sipserve don't offer free Auckland > dialing, this costs 0.05c p/m I believe, plus their DDI ranges are > delivered over the same PRI's as the slingshot italk service. > > Well that's it, if anyone has any further details, please advise. > > Thanks > Kindest Regards > Barry Murphy > > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

2 1

Re: [nznog] Voip response
by Will Steele 26 Oct '05

26 Oct '05

Both of you misread what I said - I said Sipserve. Barry said Sipserve used the same PRI's as slingshot/italk/callplus, which, I apologize if I'm wrong, but I'm pretty sure that that is not the case. And as I said, they said 2 or 3 months, so give them that at least :) Will -----Original Message----- From: chris(a)archnetnz.com [mailto:chris(a)archnetnz.com] Sent: Thursday, 27 October 2005 5:00 p.m. To: Will Steele Subject: Re: [nznog] Voip response Anyone want to tell him, or can I???? Callplus, own iTalk and slingshot.. so yes, they most likly do use the same ISDN's as iTalk... $9.95 a month is quite a good deal for an Auckland number, I would just like a Wellington number.. but who knows when that will be avilable... > Sipserve doesn't use the same PRI's, they have their own, provided by > callplus (afaik). > > The standard italk prefix of 974 is assigned to callplus in all area codes > except 06, where it is taken by TelstraClear. > > iTalk told everyone in September that it would be ready in 2 or 3 months, > yet people are still sending typical "where the hell is it" emails/forum > posts, and also have the nerve to go "oh btw, we want to pay less." > > People are assholes. > > > ________________________________________ > From: Barry Murphy > Sent: Thursday, 27 October 2005 4:20 p.m. > To: will(a)excom.net.nz > Subject: [nznog] Voip response > > Hi, > > Many of you (over 30 people) were interested in a response to my VoIP > DDI's question to the NZNog. I should have responded earlier but I was > hoping more providers would email me back, plus I've been on holiday the > last week (wahoo!). > > Well unfortunately I only had 2, unless I missed any, but it would seem > italk.co.nz and sipserve.co.nz are the only 2 providers and with number > ranges in 09 & 04. > > Italk - well they not yet selling 04 numbers from what I understand, they > working on the billing platform still. I'm currently using their 09 > service and it's great, call quality is perfect, fax over IP works, prices > aren't bad. > > Sipserve - these guys say they doing 04, however I know someone that > emailed them a week ago to get some and they still haven't + their support > is a bit slow and their system doesn't support fax over IP. > > One other thing to think about is sipserve don't offer free Auckland > dialing, this costs 0.05c p/m I believe, plus their DDI ranges are > delivered over the same PRI's as the slingshot italk service. > > Well that's it, if anyone has any further details, please advise. > > Thanks > Kindest Regards > Barry Murphy > > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog >

1 0

Re: [nznog] Voip response
by Will Steele 26 Oct '05

26 Oct '05

Sipserve doesn't use the same PRI's, they have their own, provided by callplus (afaik). The standard italk prefix of 974 is assigned to callplus in all area codes except 06, where it is taken by TelstraClear. iTalk told everyone in September that it would be ready in 2 or 3 months, yet people are still sending typical "where the hell is it" emails/forum posts, and also have the nerve to go "oh btw, we want to pay less." People are assholes. ________________________________________ From: Barry Murphy Sent: Thursday, 27 October 2005 4:20 p.m. To: will(a)excom.net.nz Subject: [nznog] Voip response Hi, Many of you (over 30 people) were interested in a response to my VoIP DDI's question to the NZNog. I should have responded earlier but I was hoping more providers would email me back, plus I've been on holiday the last week (wahoo!). Well unfortunately I only had 2, unless I missed any, but it would seem italk.co.nz and sipserve.co.nz are the only 2 providers and with number ranges in 09 & 04. Italk - well they not yet selling 04 numbers from what I understand, they working on the billing platform still. I'm currently using their 09 service and it's great, call quality is perfect, fax over IP works, prices aren't bad. Sipserve - these guys say they doing 04, however I know someone that emailed them a week ago to get some and they still haven't + their support is a bit slow and their system doesn't support fax over IP. One other thing to think about is sipserve don't offer free Auckland dialing, this costs 0.05c p/m I believe, plus their DDI ranges are delivered over the same PRI's as the slingshot italk service. Well that's it, if anyone has any further details, please advise. Thanks Kindest Regards Barry Murphy

1 0

Voip response
by barry＠unix.co.nz 26 Oct '05

26 Oct '05

Hi, Many of you (over 30 people) were interested in a response to my VoIP DDI's question to the NZNog. I should have responded earlier but I was hoping more providers would email me back, plus I've been on holiday the last week (wahoo!). Well unfortunately I only had 2, unless I missed any, but it would seem italk.co.nz and sipserve.co.nz are the only 2 providers and with number ranges in 09 & 04. Italk - well they not yet selling 04 numbers from what I understand, they working on the billing platform still. I'm currently using their 09 service and it's great, call quality is perfect, fax over IP works, prices aren't bad. Sipserve - these guys say they doing 04, however I know someone that emailed them a week ago to get some and they still haven't + their support is a bit slow and their system doesn't support fax over IP. One other thing to think about is sipserve don't offer free Auckland dialing, this costs 0.05c p/m I believe, plus their DDI ranges are delivered over the same PRI's as the slingshot italk service. Well that's it, if anyone has any further details, please advise. Thanks Kindest Regards Barry Murphy

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 26 Oct '05

26 Oct '05

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 various NZIX route servers (http://nzix.net/) 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 at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS64549 descr: advertised to AS9439 by Executive Government Support - AS64549 members: 202.36.205.128/27^27-29, 202.68.87.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: network.manager(a)egs.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050905 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64549 descr: advertised to AS9439 by Executive Government Support - AS64549 members: 202.68.87.64/27^27-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: network.manager(a)egs.govt.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051027 source: NZRR

1 0