- NZNOG - lists.nznog.org

Notification of NZRR Database changes
by NZRR Database Notifications 07 Jun '06

07 Jun '06

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:AS17492 descr: Route set advertised to AS9560 by Vector Communications - AS17492 members: 202.126.192.0/20^20-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: matthew.oram(a)vectornetworks.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050518 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17492 descr: advertised to AS9560 by Vector Communications - AS17492 members: 202.126.192.0/20^20-29, 202.0.151.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: Patrick.Balmer(a)vector.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060608 source: NZRR

1 0

Telecom BRI
by Sam Banks 06 Jun '06

06 Jun '06

Hi Guys Does anyone know the default settings for Telecom BRI ISDN lines. Point to multipoint or Point to point? TE or NT? TX and RX gain? Thanks Sam -- A good friend will help you move, a really good friend will help you move a body.

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 05 Jun '06

05 Jun '06

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:AS2687 descr: advertised to AS9560 by AT&T Global Network Services - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 202.12.105.0/24^24-29, 202.21.128.0/24^24-29, 202.27.160.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.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: david.lister(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051223 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS2687 descr: advertised to AS9560 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.175.128.0/21^21-29, 202.14.20.0/22^22-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.14.82.0/23^23-29, 202.36.68.0/23^23-29, 202.36.198.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.84.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.76.0/24^24-29, 202.27.140.0/24^24-29, 202.27.160.0/24^24-29, 202.27.250.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.36.233.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.55.5.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: david.lister(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060606 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 05 Jun '06

05 Jun '06

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:AS2687 descr: advertised to AS9439 by AT&T Global Network Services - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.36.68.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 202.12.105.0/24^24-29, 202.21.128.0/24^24-29, 202.27.160.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.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: david.lister(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051223 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS2687 descr: advertised to AS9439 by AT&T - AS2687 members: 202.46.160.0/20^20-29, 202.126.80.0/21^21-29, 202.160.112.0/21^21-29, 202.175.128.0/21^21-29, 202.14.20.0/22^22-29, 202.36.192.0/22^22-29, 152.158.254.0/23^23-29, 202.14.82.0/23^23-29, 202.36.68.0/23^23-29, 202.36.198.0/23^23-29, 202.135.48.0/23^23-29, 203.163.70.0/23^23-29, 192.203.216.0/24^24-29, 202.12.105.0/24^24-29, 202.14.84.0/24^24-29, 202.14.252.0/24^24-29, 202.21.128.0/24^24-29, 202.27.76.0/24^24-29, 202.27.140.0/24^24-29, 202.27.160.0/24^24-29, 202.27.250.0/24^24-29, 202.36.29.0/24^24-29, 202.36.80.0/24^24-29, 202.36.233.0/24^24-29, 202.37.254.0/24^24-29, 202.49.144.0/24^24-29, 202.50.137.0/24^24-29, 202.135.20.0/24^24-29, 202.135.34.0/24^24-29, 202.135.38.0/24^24-29, 202.135.62.0/24^24-29, 202.135.64.0/24^24-29, 202.135.85.0/24^24-29, 202.135.107.0/24^24-29, 202.135.111.0/24^24-29, 202.135.112.0/24^24-29, 202.135.116.0/24^24-29, 202.135.142.0/24^24-29, 202.135.146.0/24^24-29, 202.135.182.0/24^24-29, 202.135.185.0/24^24-29, 202.135.190.0/24^24-29, 202.135.192.0/24^24-29, 202.135.231.0/24^24-29, 202.135.234.0/24^24-29, 203.57.145.0/24^24-29, 203.163.68.0/24^24-29, 203.163.86.0/24^24-29, 203.163.94.0/24^24-29, 203.163.98.0/24^24-29, 203.196.101.0/24^24-29, 203.196.119.0/24^24-29, 203.196.121.0/24^24-29, 210.55.5.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: david.lister(a)ap.att.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060606 source: NZRR

1 0

Strange increase/decrease in mail rejection stats
by Simon 05 Jun '06

05 Jun '06

Hi There, I have noticed that since XTRA moved to their new mail platform, that we have had a steady increase in rejected email from fepXX.xtra.co.nz (mainly rejected due to invalid from' domain name). However, as of this morning at about 1pm, the rejected rate dropped right back to minimal again. Is someone at XTRA allowed to let us know if there have been mail system changes at their end? - and if there is any impact beyond the above? Just checking as its a bit strange to see a graph do that without getting all "OK, what do i need to check now..". Cheers Simon

1 0

Re: [nznog] What is this?
by Webmaster 03 Jun '06

03 Jun '06

Luxury. We used to live in a paper bag... I remember using a 300 bps modem to connect to bulletin boards way back when. R >>> shane hobson <shane(a)liteup.co.nz> 2/06/2006 19:33 >>> I used to use Pacnet on a 1200/75 modem on a regular basis. That would have been late 80's from memory. Shane Bill Walker wrote: > Ian McDonald wrote: > >>> In which case it was half the Internet - and if all we had was 14K for >>> the whole country - well, say no more. >>> >>> Its debatable if that really was an Internet connection in the modern >>> sense. >>> >>> >>> >> Well I was using it for NNTP, SMTP, FTP on the Waikato link when it >> was 2.4K and then 4.8K and it seemed like the Internet to me then.... >> >> > I remember a 1200bps dial up modem my dad had.... > > _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

6 5

Re: [nznog] What is this?
by Jeremy Strachan 02 Jun '06

02 Jun '06

In which case it was half the Internet - and if all we had was 14K for the whole country - well, say no more. Its debatable if that really was an Internet connection in the modern sense. 14K poses a significant restriction on what was actually possible, even back then. and yes - it is 14K each way - because a leased line is two pairs (four wires), not two wires like a home user has with a dial-up modem. It's a full duplex link, and yes we (cough) have moved along way in nearly 20 years, broadband may be faster on occasions. And not detecting a cariier - it can't detect the carrier signal from the modem at the other end - because both should see each others carrier. -----Original Message----- From: Perry Lorier [mailto:perry(a)coders.net] Sent: Friday, 2 June 2006 4:59 p.m. To: Jeremy Strachan Subject: Re: [nznog] What is this? [offlist so as not to give the game away] > ah, so young ... Its pre-Internet .. > Not quite, it was the modem used out of Waikato for New Zealands Internet connection around 1989ish. I think that means it's not "Pre Internet", it /was/ the Internet!

6 6

What is this?
by Perry Lorier 01 Jun '06

01 Jun '06

http://www.wlug.org.nz/archive/history/ Anyone guess what this modem was last used for? and when/where? We powered it on, it still works :)

5 5

Re: [nznog] What is this?
by Jeremy Strachan 01 Jun '06

01 Jun '06

2400, 4800, 9600, and yes even 14.4K was possible, and 19.2K. It probably ran over leased (conditioned) dedicated lines. It looks like a 1987 date on the back to me ... It is probably both large and heavy. Jeremy -----Original Message----- From: Joseph Miller [mailto:joseph(a)digiweb.net.nz] Sent: Friday, 2 June 2006 4:58 p.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] What is this? It can't be that old - it's a whole 14.4k!

1 0

Re: [nznog] What is this?
by Jeremy Strachan 01 Jun '06

01 Jun '06

ah, so young ... Its pre-Internet .. -----Original Message----- From: Perry Lorier [mailto:perry(a)coders.net] Sent: Friday, 2 June 2006 4:52 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] What is this? http://www.wlug.org.nz/archive/history/ Anyone guess what this modem was last used for? and when/where? We powered it on, it still works :) _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

3 2

Notification of NZRR Database changes
by NZRR Database Notifications 01 Jun '06

01 Jun '06

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:AS10022 descr: advertised to AS9560 by Datacom - AS10022 members: 202.175.128.0/21^21-29, 202.14.20.0/22^22-29, 202.36.198.0/23^23-29, 192.203.216.0/24^24-29, 202.14.83.0/24^24-29, 202.27.76.0/24^24-29, 202.27.140.0/24^24-29, 202.27.143.0/24^24-29, 202.27.250.0/24^24-29, 202.36.233.0/24^24-29, 210.55.5.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: idc(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060210 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS10022 descr: advertised to AS9560 by Datacom - AS10022 members: 202.175.128.0/21^21-29, 202.14.20.0/22^22-29, 202.14.82.0/23^23-29, 202.36.198.0/23^23-29, 192.203.216.0/24^24-29, 202.14.84.0/24^24-29, 202.27.76.0/24^24-29, 202.27.140.0/24^24-29, 202.27.143.0/24^24-29, 202.27.250.0/24^24-29, 202.36.233.0/24^24-29, 210.55.5.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: idc(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060602 source: NZRR

1 0

[RIR] Deprecation of ip6.int Scheduled for June 1, 2006
by bmanning＠vacation.karoshi.com 31 May '06

31 May '06

On Thu, Mar 02, 2006 at 09:19:56AM -0500, Member Services wrote: > In August 2005, RFC 4159 Deprecation of ip6.int was published as Best > Current Practice. This RFC noted that maintenance of ip6.int is no > longer required and that the Regional Internet Registries adopt a > schedule for cessation of ip6.int. All the RIRs have agreed to deprecate > ip6.int on June 1, 2006. Further note that ARIN no longer modifies any > of the zones it administers under ip6.int effective December 7, 2005. > > Ginny Listman > Director of Engineering > American Registry for Internet Numbers and: On Tue, 16 May 2006 11:09:10 +0200, Andrei Robachevsky wrote: > Below is the proposed plan of ip6.int deprecation. Could you please > check if it is detailed enough to be properly coordinated, or if it > misses something. > > Andrei > > ip6.int deprecation plan > ------------------------- > > Advance Work: > > Contact Bill Manning at bmanning(a)vacation.karoshi.com and > hostmaster(a)ep.net before the 25th of May and ask him to schedule the > following: > > o June 1st 12:00 GMT: Remove all delegations within the 2.ip6.int zone. > > RIR Plan (common) > > o May 30th 12:00 GMT: Drop TTL on authoritative NS records within the > ip6.int zones to 3600. > > o June 1st 12:00 GMT: All delegations within the ip6.int zone are > removed. No RIR Action needed, other than checking. > > o June 1st 13:00 GMT - 23:59 GMT: All RIR's remove their respective > ip6.int zones from their servers. ........ while i noted the following: not all the zones or data in ip6.int are being removed.... so no, i am not changing the TTLs. the delegations that the RIR's have asked to be removed are scheduled for automatic removal. I will check on the process when i wake up roughly 3.5 hours later. I will be glad to send you email at that time to confirm removal. --bill ....... that being said, the RIR requested delegations have been removed from the IP6.INT zone. what remains is: # dig 2.ip6.int. axfr @::1 ; <<>> DiG 9.3.2 <<>> 2.ip6.int. axfr @::1 ; (1 server found) ;; global options: printcmd 2.ip6.int. 86400 IN SOA dot.ep.net. hostmaster.ep.net. 1999061700 10800 900 604800 129600 2.ip6.int. 86400 IN NS z.ip6.int. 2.ip6.int. 86400 IN NS dot.ep.net. 2.ip6.int. 86400 IN NS flag.ep.net. 0.0.1.0.0.2.ip6.int. 86400 IN NS z.ip6.int. 0.0.1.0.0.2.ip6.int. 86400 IN NS dot.ep.net. 0.0.1.0.0.2.ip6.int. 86400 IN NS flag.ep.net. 1.0.1.0.0.2.ip6.int. 86400 IN NS z.ip6.int. 1.0.1.0.0.2.ip6.int. 86400 IN NS dot.ep.net. 1.0.1.0.0.2.ip6.int. 86400 IN NS flag.ep.net. 2.0.0.2.ip6.int. 86400 IN NS z.ip6.int. 2.0.0.2.ip6.int. 86400 IN NS dot.ep.net. 2.0.0.2.ip6.int. 86400 IN NS flag.ep.net. 2.ip6.int. 86400 IN SOA dot.ep.net. hostmaster.ep.net. 1999061700 10800 900 604800 129600 ;; Query time: 4 msec ;; SERVER: ::1#53(::1) ;; WHEN: Thu Jun 1 06:44:20 2006 ;; XFR size: 14 records (messages 14) --bill

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 31 May '06

31 May '06

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:AS18353 descr: Route set advertised to AS9439 by HDS - AS18353 members: 202.55.96.176/28^28-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: kenneth.liew(a)hdsnz.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051006 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS18353 descr: advertised to AS9439 by Revera - AS18353 members: 202.55.99.0/24^24-29, 202.55.96.176/28^28-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: Marc.Nienkemper(a)revera.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060601 source: NZRR

1 0

FW: GGIS Service Message : Major
by Paul Adshead 31 May '06

31 May '06

FYI -----Original Message----- From: noc(a)global-gateway.net.nz [mailto:noc(a)global-gateway.net.nz] Sent: Thursday, 1 June 2006 00:28 To: global-gateway outage contacts Subject: GGIS Service Message : Major GGIS Backbone Update Global-Gateway Internet is currently experiencing service disruption which began at 21:40 hrs, 31/05/06date You are likely to experience major international congestion of your service until this problem is resolved. A cable fault has been identified in the USA near San Francisco. Currently, we are have no expected time for restoration. GGIS apologises for any inconvenience to you or your customers, and an update will follow within 2 hours. Logged by Andrew Murray on Thu Jun 1 00:27:59 2006

3 2

Police Hoax Email
by Keith Davidson 30 May '06

30 May '06

Just a heads up for anyone not aware of this... Keith Davidson www.police.govt.nz/news/release/2445.html Hoax police email 10:03am 31 May 2006 A hoax email is circulating within New Zealand which purports to be a notification from NZ Police. The email has this subject line - "Notification from Police New_Zealand" The email is clearly a hoax but is causing some concern in the public with callers contacting police for clarification. The email suggests that recipients are "under suspicion of financial machination." It then asks receivers to fill in details and fax or email details. Police are investigating the email which does contain a trojan virus. The virus will be filtered out so long as computers have anti-virus software on their machines. Members of the public who are receiving the email with the subject line - "Notification from Police New_Zealand" - should simply delete it and do not need to contact Police about the matter. ENDS

1 0

wireline.co.nz domain
by Grant Zanetti 30 May '06

30 May '06

Can anyone at telecom tell me why they're sending emails from this domain (wireline.co.nz) when it has no useful DNS? Where is my mail system supposed to send bounces etc?

1 0

Podcasting Heads Up
by Webmaster 29 May '06

29 May '06

Operators should be aware that due to increased demand on our podcasting service, and the number of requests we've had to increase the quality of the files, we'll be increasing the data rates of all files offered from our US mirror. At the moment all US files have the same names as NZ hosted files, but are actually lower rates. Over the next 2 weeks this will change, with the US server becoming a full mirror. The data rates of files will double (from 24k to 48k) to match those hosted in NZ. We've been able to do this because we have extra capacity in the US and can serve the extra traffic at no additional cost to us. At present NZ bound traffic from the US server sits at 10-15 Mb/s during the day. Local operators who do not peer with our NZ servers will see an increase in international inbound traffic (about double) from the US mirror over the next two weeks. After that you should allow for an increase of 10-15% per week - our current growth rate. Those who peer with our servers in New Zealand are not affected by this change. regards, Richard Hulse Radio NZ

1 0

[Fwd: APNIC ip6.int services to end 1 June 2006]
by Andy Linton 29 May '06

29 May '06

Not that this isn't because the IPv6 camp are giving up and going home. (:-) andy -------- Original Message -------- Subject: APNIC ip6.int services to end 1 June 2006 Date: Mon, 29 May 2006 21:31:42 +1000 From: sanjaya(a)apnic.net To: asjl(a)citylink.co.nz Dear colleagues, APNIC will cease all ip6.int reverse delegation services at approximately 10:00 UTC+10 (00:00 UTC) on 1 June 2006. At that time, APNIC will withdraw the delegations for the following sub-domains under 1.0.0.2.ip6.int: 2.0.1.0.0.2.ip6.int 3.0.1.0.0.2.ip6.int c.0.1.0.0.2.ip6.int d.0.1.0.0.2.ip6.int e.0.1.0.0.2.ip6.int f.0.1.0.0.2.ip6.int 4.4.1.0.0.2.ip6.int 5.4.1.0.0.2.ip6.int 8.1.0.0.2.ip6.int 9.1.0.0.2.ip6.int a.1.0.0.2.ip6.int All ip6.int delegations within these sub-domains will then cease to be recognised by most DNS resolvers (although cached delegation information may take some time to expire). APNIC will back-up all whois objects associated with these sub-domains and will continue to monitor DNS traffic during this period to review behaviour. However, as the IETF has formally deprecated ip6.int for reverse-DNS, re-delegation is not expected to occur. Regards, Sanjaya ______________________________________________________________________ Technical Services Manager <sanjaya(a)apnic.net> APNIC ph +61 7 3858 3100 http://www.apnic.net fx +61 7 3858 3199 ______________________________________________________________________

3 2

(no subject)
by Russell STREET 25 May '06

25 May '06

Hello.. . TelstraClear hosts this NZ root name server replica on its infrastructure. We are physically moving the servers that run this name server this weekend. This will cause an outage to ns4.dns.net.nz at around 6AM Saturday 27th May 2006 for around 2 minutes, when we migrate the routing for the name server from one site to the new site. Russell (TelstraClear IS Operations)

1 0

Re: [nznog] Cell Tax
by Mark Seward 25 May '06

25 May '06

Interesting numbers. After a few weeks of bad performance on an Internet feed I look after I was drawn back to an issue I thought was long buried. This circuit was dropping 4-5% of its traffic at well below advertised capacity. The delivery method was ethernet over ATM/AAL5 (RFC1483). The usual suspects were rounded up and shot (duplex and error counters, purple switches, the cleaning lady). The next question was overhead for cell tax and encapsulation. 12% seems to be the allowance by our supplier. IIRC this is the same as was used 10 years ago for ATM VCs delivered directly to routers (no ethernet involved); nanog has a few dusty posts about this number. It seems this is no longer enough. Perhaps average packet sizes have changed since then if 12% was ever a reasonable number. In the end our supplier ramped overhead to about 20% and the pipe has performed nicely since. For an ethernet service, I don't understand why they don't simply provision the VC (VBR) as large as the customer bearer can handle and let the end devices do the shaping. Michael's numbers including AAL5 padding give this new figure some context: Upstream: cell tax = 14.84% (18.09% AAL5) Downstream: cell tax = 18.35% (23.43% AAL5) Is anyone aware of a recent study of packet size distribution on Internet traffic? CAIDA have some information from the AIX in 1999, NLANR from '97, and Sprint do a semi-regular dump from their ipmon project. http://www.caida.org/analysis/AIX/plen_hist http://www.nlanr.net/NA/Learn/packetsizes.html http://ipmon.sprint.com/packstat/packetoverview.php >From netflow stats on this link, I see a similar story with 64, 576 and 1536B being the points of most interest. The percentage of 1536B packets (~25) I think is larger now than previously. Has anyone had similar frustrations with PVC dimensioning? Does anyone else still use ATM? :) Mark. On 5/23/06, Michael Newbery < Michael.Newbery(a)team.telstraclear.co.nz> wrote: > > Prompted by Mark Seward, we have had a look at the cell tax incurred for > our > customers, in those cases where we are unfortunate enough to have to > transit > an ATM pipe. Which has not been the usual case on our network but becomes > interesting for things like UBS. > > This enables us to answer the question: for a pipe of x bps sufficient to > carry pure IP, how much bigger must the ATM PVC be to carry the same load? > > > IP_bw = x > ATM_bw = ceiling(x/48)*53 > Diff = ATM_bw - IP_bw > Cell_tax = Diff/IP_bw > > For a sample SAMP, we calculate the mean cell tax as > (sum(ceiling( SAMP/48)*53) - sum(SAMP))/sum(SAMP) > > Looking at a 24 hour sample, we get: > Upstream: cell tax = 14.84% > Downstream: cell tax = 18.35% > > I understand that this is somewhat at variance with the standard > provisioning rules applied by another provider. > -- > Michael Newbery IP Architect TelstraClear Limited > Tel: +64-4-920 3102 Mobile: +64-29-920 3102 Fax: +64-4-920 3361 > > > _______________________________________________ > NZNOG mailing list > NZNOG(a)list.waikato.ac.nz > http://list.waikato.ac.nz/mailman/listinfo/nznog > >

2 1

InternetNZ Internet Governance Positions
by Keith Davidson 24 May '06

24 May '06

Pardon the intrusion and slightly off topic subject: Interested in Internet governance? InternetNZ is recruiting directors to sit on the Board of its subsidiary company, New Zealand Domain Name Registry Ltd (trading as .nz Registry Services or "NZRS"); and members to sit on the .nz Oversight Committee ("NZOC"), which has stewardship of the .nz domain name space. These positions provide an exciting opportunity to contribute to the good governance of the .nz domain name space. Company directors and those with general governance skills are encouraged to apply for the appropriate positions. The retiring incumbents are eligible for reappointment. Complete descriptions and application details for both roles can be found online at www.internetnz.net.nz/vacancy. More information on the Office of the Domain Name Commissioner can be found at www.dnc.org.nz; and about the registry company at www.nzrs.net.nz. Applications by email to vacancy(a)internetnz.net.nz are invited from suitably qualified people, and close at midnight on Saturday 3 June. Please follow the links above for further details. If you are aware of anyone who you feel would be appropriate for one of the vacancies, we would be most grateful if you could forward this information to them. Furthermore, it is coming up to AGM time for InternetNZ and we are always on the lookout for enthusiastic people to serve on our Council and various committees and working groups. Links to further details on these positions are at www.internetnz.net.nz/vacancy. Any successful recruitment from a connection with NZNOG will result in a reward of provision of beer to all associated. Regards Keith Davidson Executive Director - InternetNZ

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 24 May '06

24 May '06

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:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060523 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060525 source: NZRR

1 0

Xtra mail issues to AOL.com
by Drew Broadley 24 May '06

24 May '06

Could someone on Xtra's side please contact me offlist in regards to this. In the last four plus days this has happened and mail coming from AOL to Xtra is fine. -----Original Message----- From: "Mail Administrator"<Postmaster(a)xtra.co.nz> Sent: 25/05/06 8:54:57 a.m. To: "goldenfleece(a)clear.net.nz"<goldenfleece(a)clear.net.nz> Subject: Mail System Error - Returned Mail This is a system generated message. Please DO NOT REPLY. Your message was not delivered for the following reason: Your message was not delivered because the destination computer was not reachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely there is a network problem that prevented delivery, but it is also possible that the computer is turned off, or does not have a mail system running right now. Your message was not delivered within 4 days and 0 hours. Host aol.com is not responding. The following recipients did not receive this message: <wooluk(a)aol.com> For more information on why this message wasn't delivered, and an explanati [Message truncated. Tap Edit->Mark for Download to get remaining portion.]

1 1

for those who have spare time today and aren't here.....
by Richard Naylor 22 May '06

22 May '06

http://www.r2.co.nz/20060524/

2 1

Sorbs - Further Notification
by Bruce Harding 22 May '06

22 May '06

For those using Sorbs for any sort of blocking, you may have trouble receiving mail from Inspire Net now that they have chosen to block our 2 primary Mail servers. -- Bruce Harding Inspire Net Ltd Phone : 06 357 8559 Fax : 06 353 1154 Mobile : 021 519 024

3 2

Re: [nznog] DNS lookup for IPs of healthalliance.co.nz
by Clement Ashwal 22 May '06

22 May '06

Thanks for all your inputs guys. Since 2:15pm the nslookup for the URLs and also to all the SMTP servers hosted by Healthalliance have started to work by itself without anybody having to do any changes. I did get in touch with the Healthalliance techs and they seemed to have done nothing at all. Quite mysterious I must say. Hope it continues to work without any disruptions. Clement Ashwal Sr Network Analyst The University of Auckland + 6493737599 x 87993 -----Original Message----- From: jfp [mailto:jfp(a)clearfield.com] Sent: Tuesday, 23 May 2006 1:42 p.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] DNS lookup for IPs of healthalliance.co.nz Well it looks like ns1.healthalliance.co.nz is down. dig www.healthalliance.co.nz @210.54.1.142 works dig www.healthalliance.co.nz @210.54.1.143 fails. given the the reverse DNS for 210.54.1.143 and 210.54.1.142 is also on those servers, you're going to get timeouts galore. ns1.healthalliance.co.nz. 86400 IN A 210.54.1.143 ns2.healthalliance.co.nz. 86400 IN A 210.54.1.142 jfp. ------------------------------------------------------------------------ Jean-Francois Pirus <jfp(a)clearfield.com> Senior Software Engineer Phone (+64-9) 358 2081 Clearfield Software Ltd Fax (+64-9) 358 2083 4th Floor 8-10 Whitaker Place Mob (+64-21) 640 779 P O Box 3901 Auckland, New Zealand ------------------------------------------------------------------------ _______________________________________________ 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 22 May '06

22 May '06

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:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29, 203.97.5.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060522 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060523 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 22 May '06

22 May '06

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:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29, 203.97.5.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060522 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060523 source: NZRR

1 0

Cell Tax
by Michael Newbery 22 May '06

22 May '06

Prompted by Mark Seward, we have had a look at the cell tax incurred for our customers, in those cases where we are unfortunate enough to have to transit an ATM pipe. Which has not been the usual case on our network but becomes interesting for things like UBS. This enables us to answer the question: for a pipe of x bps sufficient to carry pure IP, how much bigger must the ATM PVC be to carry the same load? IP_bw = x ATM_bw = ceiling(x/48)*53 Diff = ATM_bw - IP_bw Cell_tax = Diff/IP_bw For a sample SAMP, we calculate the mean cell tax as (sum(ceiling( SAMP/48)*53) - sum(SAMP))/sum(SAMP) Looking at a 24 hour sample, we get: Upstream: cell tax = 14.84% Downstream: cell tax = 18.35% I understand that this is somewhat at variance with the standard provisioning rules applied by another provider. -- Michael Newbery IP Architect TelstraClear Limited Tel: +64-4-920 3102 Mobile: +64-29-920 3102 Fax: +64-4-920 3361

1 0

DNS lookup for IPs of healthalliance.co.nz
by Clement Ashwal 22 May '06

22 May '06

Hi, If somebody could throw some light on this issue would very much appreciate. We are having problems resolving few of the following URLs from our DNS servers at the University. www.countiesmanukaudhb.org.nz <http://www.countiesmanukaudhb.org.nz/> webmail.middlemore.co.nz www.waitematahealth.co.nz <http://www.waitematahealth.co.nz/> www.healthalliance.co.nz and others. All these names are registered with Healthalliance. There have been no changes to our DNS whatsoever and the reverse-lookups are working fine. Clement Ashwal Sr Network Analyst - ITSS The University of Auckland Private Bag 92019 Auckland New Zealand Phone + 64 9 3737599 x 87993 CAUTION - This message may contain privileged and confidential information intended only for the use of the addressee named above. If you are not the intended recipient of this message you are hereby notified that any use, dissemination, distribution or reproduction of this message is prohibited. If you have received this message in error please notify the sender immediately.

6 5

SORBS still listing Telecom static IPs as dynamic...
by Paul Adshead 22 May '06

22 May '06

It appears that SORBS are atill listing Telecom static IP ranges (- which my address is in,) as dynamic ranges. Wasn't this in the process of being fixed weeks/months ago? Does anyone have any ideas on how long this is going to be until it's resolved? The whole SORBS situation over the past months is becoming a total joke, with mail admins I know turning off their use of SORBS - there is just far far far too many false positives... :-( Paul. -----Original Message----- From: System Administrator Sent: Thursday, 18 May 2006 15:58 To: <customer> Subject: Undeliverable:RE: <mail subject> Your message did not reach some or all of the intended recipients. Subject: RE: <mail subject> Sent: 18/05/2006 15:58 The following recipient(s) could not be reached: Robert Reid on 18/05/2006 15:58 You do not have permission to send to this recipient. For assistance, contact your system administrator. <mailserver.mycompany.co.nz #5.7.1 smtp;554 5.7.1 Rejected 210.55.xx.xxx is a dynamic IP (see: http://www.au.sorbs.net/faq/dul.shtml for more information)>

13 21

IPv6 allocation and APNIC
by Brendon Wyber 22 May '06

22 May '06

Hi, Anyone had experience with getting a range of IPv6 numbers allocated to them through APNIC? Does NZ have the equivalent of a NIR (National Internet Registry) set up for allocation of IPv6? Cheers Brendon ========================================= Brendon Wyber, Wide Area Network Consultant, IT Department, University of Canterbury, Private Bag 4800, Christchurch, New Zealand. Phone: +64 3 364 2336 Fax: +64 3 364 2332 email: brendon.wyber(a)canterbury.ac.nz

3 2

IHUG Peering policy
by Simon Allard 22 May '06

22 May '06

Hi NZNOG :-) IHUG is changing its peering policy for peering over WIX and APE. We will no longer be directly peering with our current peers but will continue to peer with the route reflectors. Customers of IHUG who require APE/WIX peering directly will not be affected by this policy. This change is not because we don't like peering; it's just our way of trying to make our network simpler to manage. We are aware that some isp's are not huge fans of the route reflectors and prefer direct peering. We have heard all the arguments about why direct peering is much better than the "evil route reflectors of doom", but we personally have had no problems with them and they have proven to be reliable. If you have any questions, please contact me off list. Thank you :-) Simon Allard Ihug Limited P +64 9 962 9827 M +64 21 456 412 E simon.allard(a)staff.ihug.co.nz

2 1

Notification of NZRR Database changes
by NZRR Database Notifications 21 May '06

21 May '06

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:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29, 203.97.5.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060505 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29, 203.97.5.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060522 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 21 May '06

21 May '06

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:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29, 203.97.5.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060505 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.50.208.0/20^20-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 202.50.200.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.50.52.0/22^22-29, 202.50.196.0/22^22-29, 202.59.4.0/22^22-29, 202.37.86.0/23^23-29, 202.49.80.0/23^23-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.36.226.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.0/24^24-29, 203.97.5.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-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060522 source: NZRR

1 0

Re: [nznog] Routing question
by Justin Cook 21 May '06

21 May '06

Thanks to everyone who responded, particularly JSR. All sorted and working great.

1 0

Routing question
by Justin Cook 21 May '06

21 May '06

Quick question from a routing noob: I've just acquired 210.48.96.88/30. The two IP addresses in the block are intended for a couple of vmware instances. We're not using anything nice like a Cisco router, just a Linksys stand-in for now. It has some basic static routing capabilities. I had a short conversation with Iconz support but I'm not feeling very confident about the result. I've been instructed (or rather I said "this is what we came up with" and I got a vague "yes") to add the following entry to the routing table (where 202.37.231.84 is the existing IP that we're using as an external address): Destination: 210.48.96.88 Subnet: 255.255.255.252 Gateway: 202.37.231.84 Interface: Local It's the gateway bit we're unsure of - won't this cause a loop? My mate is concerned that it's not going to work as it needs to be on the same subnet. Cheers Justin

3 3

Notification of NZRR Database changes
by NZRR Database Notifications 21 May '06

21 May '06

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:AS7657 descr: advertised to AS9560 by ihug - AS7657 members: 124.168.0.0/16^16-29, 203.59.0.0/16^16-29, 203.109.128.0/17^17-29, 203.118.128.0/17^17-29, 203.173.128.0/17^17-29, 203.206.0.0/17^17-29, 203.214.0.0/17^17-29, 210.84.0.0/18^18-29, 202.161.0.0/19^19-29, 203.96.192.0/19^19-29, 203.158.32.0/19^19-29, 203.166.224.0/19^19-29, 203.173.0.0/19^19-29, 203.206.128.0/19^19-29, 203.206.224.0/19^19-29, 203.214.128.0/19^19-29, 203.217.32.0/19^19-29, 203.217.64.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.137.96.0/20^20-29, 203.173.32.0/20^20-29, 203.190.192.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 202.129.80.0/21^21-29, 202.129.96.0/21^21-29, 203.173.48.0/21^21-29, 203.206.168.0/21^21-29, 203.206.176.0/21^21-29, 203.215.0.0/21^21-29, 203.217.0.0/21^21-29, 203.217.16.0/21^21-29, 210.55.248.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.49.240.0/22^22-29, 202.50.188.0/22^22-29, 202.129.68.0/22^22-29, 202.129.76.0/22^22-29, 202.129.108.0/22^22-29, 202.129.116.0/22^22-29, 202.129.120.0/22^22-29, 203.14.168.0/22^22-29, 203.55.228.0/22^22-29, 203.57.140.0/22^22-29, 203.62.212.0/22^22-29, 203.173.56.0/22^22-29, 203.206.164.0/22^22-29, 203.206.184.0/22^22-29, 203.206.192.0/22^22-29, 203.206.204.0/22^22-29, 203.206.220.0/22^22-29, 203.215.8.0/22^22-29, 203.217.12.0/22^22-29, 203.217.28.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 202.128.110.0/23^23-29, 202.129.72.0/23^23-29, 202.129.88.0/23^23-29, 202.129.92.0/23^23-29, 202.129.106.0/23^23-29, 202.129.114.0/23^23-29, 203.7.196.0/23^23-29, 203.8.92.0/23^23-29, 203.14.174.0/23^23-29, 203.17.62.0/23^23-29, 203.21.74.0/23^23-29, 203.29.86.0/23^23-29, 203.55.140.0/23^23-29, 203.56.30.0/23^23-29, 203.56.62.0/23^23-29, 203.57.10.0/23^23-29, 203.57.136.0/23^23-29, 203.173.60.0/23^23-29, 203.206.162.0/23^23-29, 203.206.188.0/23^23-29, 203.206.202.0/23^23-29, 203.206.208.0/23^23-29, 203.206.218.0/23^23-29, 203.215.14.0/23^23-29, 203.215.18.0/23^23-29, 203.217.10.0/23^23-29, 210.55.202.0/23^23-29, 192.107.113.0/24^24-29, 192.188.107.0/24^24-29, 198.32.71.0/24^24-29, 199.98.84.0/24^24-29, 202.7.6.0/24^24-29, 202.12.87.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.46.0/24^24-29, 202.36.174.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 202.128.109.0/24^24-29, 202.129.67.0/24^24-29, 202.129.91.0/24^24-29, 202.129.94.0/24^24-29, 202.129.104.0/24^24-29, 202.129.112.0/24^24-29, 202.129.125.0/24^24-29, 202.129.126.0/24^24-29, 202.169.97.0/24^24-29, 202.176.0.0/24^24-29, 203.0.12.0/24^24-29, 203.0.84.0/24^24-29, 203.0.139.0/24^24-29, 203.0.178.0/24^24-29, 203.1.24.0/24^24-29, 203.1.78.0/24^24-29, 203.2.199.0/24^24-29, 203.3.127.0/24^24-29, 203.4.173.0/24^24-29, 203.5.184.0/24^24-29, 203.7.155.0/24^24-29, 203.7.173.0/24^24-29, 203.8.161.0/24^24-29, 203.8.219.0/24^24-29, 203.12.1.0/24^24-29, 203.12.15.0/24^24-29, 203.12.44.0/24^24-29, 203.12.236.0/24^24-29, 203.14.172.0/24^24-29, 203.14.182.0/24^24-29, 203.15.111.0/24^24-29, 203.15.129.0/24^24-29, 203.16.34.0/24^24-29, 203.17.60.0/24^24-29, 203.17.194.0/24^24-29, 203.17.249.0/24^24-29, 203.17.251.0/24^24-29, 203.18.85.0/24^24-29, 203.18.140.0/24^24-29, 203.19.70.0/24^24-29, 203.20.82.0/24^24-29, 203.20.88.0/24^24-29, 203.20.116.0/24^24-29, 203.20.132.0/24^24-29, 203.21.5.0/24^24-29, 203.21.105.0/24^24-29, 203.22.19.0/24^24-29, 203.22.96.0/24^24-29, 203.23.7.0/24^24-29, 203.24.50.0/24^24-29, 203.24.189.0/24^24-29, 203.25.109.0/24^24-29, 203.25.144.0/24^24-29, 203.25.197.0/24^24-29, 203.26.32.0/24^24-29, 203.26.86.0/24^24-29, 203.26.92.0/24^24-29, 203.26.128.0/24^24-29, 203.27.58.0/24^24-29, 203.27.60.0/24^24-29, 203.27.89.0/24^24-29, 203.27.201.0/24^24-29, 203.28.157.0/24^24-29, 203.28.174.0/24^24-29, 203.29.221.0/24^24-29, 203.30.181.0/24^24-29, 203.30.194.0/24^24-29, 203.31.13.0/24^24-29, 203.31.96.0/24^24-29, 203.31.141.0/24^24-29, 203.34.95.0/24^24-29, 203.55.151.0/24^24-29, 203.56.243.0/24^24-29, 203.57.134.0/24^24-29, 203.61.76.0/24^24-29, 203.102.166.0/24^24-29, 203.108.77.0/24^24-29, 203.112.114.0/24^24-29, 203.173.63.0/24^24-29, 203.206.161.0/24^24-29, 203.206.190.0/24^24-29, 203.206.196.0/24^24-29, 203.206.198.0/24^24-29, 203.206.201.0/24^24-29, 203.206.213.0/24^24-29, 203.206.214.0/24^24-29, 203.206.217.0/24^24-29, 203.215.12.0/24^24-29, 203.215.17.0/24^24-29, 203.215.20.0/24^24-29, 210.8.138.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060403 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS7657 descr: advertised to AS9560 by IHUG - AS7657 members: 124.168.0.0/16^16-29, 203.59.0.0/16^16-29, 203.109.128.0/17^17-29, 203.118.128.0/17^17-29, 203.173.128.0/17^17-29, 203.206.0.0/17^17-29, 203.214.0.0/17^17-29, 210.84.0.0/18^18-29, 202.161.0.0/19^19-29, 203.96.192.0/19^19-29, 203.158.32.0/19^19-29, 203.166.224.0/19^19-29, 203.173.0.0/19^19-29, 203.206.128.0/19^19-29, 203.206.224.0/19^19-29, 203.214.128.0/19^19-29, 203.217.32.0/19^19-29, 203.217.64.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.137.96.0/20^20-29, 203.173.32.0/20^20-29, 203.190.192.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 202.129.80.0/21^21-29, 202.129.96.0/21^21-29, 203.173.48.0/21^21-29, 203.206.168.0/21^21-29, 203.206.176.0/21^21-29, 203.215.0.0/21^21-29, 203.217.0.0/21^21-29, 203.217.16.0/21^21-29, 210.55.248.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.49.240.0/22^22-29, 202.50.188.0/22^22-29, 202.129.68.0/22^22-29, 202.129.76.0/22^22-29, 202.129.108.0/22^22-29, 202.129.116.0/22^22-29, 202.129.120.0/22^22-29, 203.14.168.0/22^22-29, 203.55.228.0/22^22-29, 203.57.140.0/22^22-29, 203.62.212.0/22^22-29, 203.173.56.0/22^22-29, 203.206.164.0/22^22-29, 203.206.184.0/22^22-29, 203.206.192.0/22^22-29, 203.206.204.0/22^22-29, 203.206.220.0/22^22-29, 203.215.8.0/22^22-29, 203.217.12.0/22^22-29, 203.217.28.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 202.128.110.0/23^23-29, 202.129.72.0/23^23-29, 202.129.88.0/23^23-29, 202.129.92.0/23^23-29, 202.129.106.0/23^23-29, 202.129.114.0/23^23-29, 203.7.196.0/23^23-29, 203.8.92.0/23^23-29, 203.14.174.0/23^23-29, 203.17.62.0/23^23-29, 203.21.74.0/23^23-29, 203.29.86.0/23^23-29, 203.55.140.0/23^23-29, 203.56.30.0/23^23-29, 203.56.62.0/23^23-29, 203.57.10.0/23^23-29, 203.57.136.0/23^23-29, 203.173.60.0/23^23-29, 203.206.162.0/23^23-29, 203.206.188.0/23^23-29, 203.206.202.0/23^23-29, 203.206.208.0/23^23-29, 203.206.218.0/23^23-29, 203.215.14.0/23^23-29, 203.215.18.0/23^23-29, 203.215.20.0/23^23-29, 203.217.10.0/23^23-29, 210.55.202.0/23^23-29, 192.107.113.0/24^24-29, 192.188.107.0/24^24-29, 198.32.71.0/24^24-29, 199.98.84.0/24^24-29, 202.7.6.0/24^24-29, 202.12.87.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.46.0/24^24-29, 202.36.174.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 202.128.109.0/24^24-29, 202.129.67.0/24^24-29, 202.129.91.0/24^24-29, 202.129.94.0/24^24-29, 202.129.104.0/24^24-29, 202.129.112.0/24^24-29, 202.129.125.0/24^24-29, 202.129.126.0/24^24-29, 202.169.97.0/24^24-29, 202.176.0.0/24^24-29, 203.0.12.0/24^24-29, 203.0.84.0/24^24-29, 203.0.139.0/24^24-29, 203.0.178.0/24^24-29, 203.1.24.0/24^24-29, 203.1.78.0/24^24-29, 203.2.199.0/24^24-29, 203.3.127.0/24^24-29, 203.4.173.0/24^24-29, 203.5.184.0/24^24-29, 203.7.155.0/24^24-29, 203.7.173.0/24^24-29, 203.8.161.0/24^24-29, 203.8.219.0/24^24-29, 203.12.1.0/24^24-29, 203.12.15.0/24^24-29, 203.12.44.0/24^24-29, 203.12.236.0/24^24-29, 203.14.172.0/24^24-29, 203.14.182.0/24^24-29, 203.15.111.0/24^24-29, 203.15.129.0/24^24-29, 203.16.34.0/24^24-29, 203.17.60.0/24^24-29, 203.17.194.0/24^24-29, 203.17.249.0/24^24-29, 203.17.251.0/24^24-29, 203.18.85.0/24^24-29, 203.18.140.0/24^24-29, 203.19.70.0/24^24-29, 203.20.82.0/24^24-29, 203.20.88.0/24^24-29, 203.20.116.0/24^24-29, 203.20.132.0/24^24-29, 203.21.5.0/24^24-29, 203.21.105.0/24^24-29, 203.22.19.0/24^24-29, 203.22.96.0/24^24-29, 203.23.7.0/24^24-29, 203.24.50.0/24^24-29, 203.24.189.0/24^24-29, 203.25.109.0/24^24-29, 203.25.144.0/24^24-29, 203.25.197.0/24^24-29, 203.26.32.0/24^24-29, 203.26.86.0/24^24-29, 203.26.92.0/24^24-29, 203.26.128.0/24^24-29, 203.27.58.0/24^24-29, 203.27.60.0/24^24-29, 203.27.89.0/24^24-29, 203.27.201.0/24^24-29, 203.28.157.0/24^24-29, 203.28.174.0/24^24-29, 203.29.221.0/24^24-29, 203.30.181.0/24^24-29, 203.30.194.0/24^24-29, 203.31.13.0/24^24-29, 203.31.96.0/24^24-29, 203.31.141.0/24^24-29, 203.34.95.0/24^24-29, 203.55.151.0/24^24-29, 203.56.243.0/24^24-29, 203.57.134.0/24^24-29, 203.61.76.0/24^24-29, 203.102.166.0/24^24-29, 203.108.77.0/24^24-29, 203.112.114.0/24^24-29, 203.173.63.0/24^24-29, 203.206.161.0/24^24-29, 203.206.190.0/24^24-29, 203.206.196.0/24^24-29, 203.206.198.0/24^24-29, 203.206.201.0/24^24-29, 203.206.213.0/24^24-29, 203.206.214.0/24^24-29, 203.206.217.0/24^24-29, 203.215.12.0/24^24-29, 203.215.17.0/24^24-29, 210.8.138.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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: pshem.k(a)staff.ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060522 source: NZRR --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by Ihug Ltd - AS7657 members: 124.168.0.0/16^16-29, 203.59.0.0/16^16-29, 203.109.128.0/17^17-29, 203.118.128.0/17^17-29, 203.173.128.0/17^17-29, 203.206.0.0/17^17-29, 203.214.0.0/17^17-29, 210.84.0.0/18^18-29, 202.161.0.0/19^19-29, 203.96.192.0/19^19-29, 203.158.32.0/19^19-29, 203.166.224.0/19^19-29, 203.173.0.0/19^19-29, 203.206.128.0/19^19-29, 203.206.224.0/19^19-29, 203.214.128.0/19^19-29, 203.217.32.0/19^19-29, 203.217.64.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.137.96.0/20^20-29, 203.173.32.0/20^20-29, 203.190.192.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 202.129.80.0/21^21-29, 202.129.96.0/21^21-29, 203.173.48.0/21^21-29, 203.206.168.0/21^21-29, 203.206.176.0/21^21-29, 203.215.0.0/21^21-29, 203.217.0.0/21^21-29, 203.217.16.0/21^21-29, 210.55.248.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.49.240.0/22^22-29, 202.50.188.0/22^22-29, 202.129.68.0/22^22-29, 202.129.76.0/22^22-29, 202.129.108.0/22^22-29, 202.129.116.0/22^22-29, 202.129.120.0/22^22-29, 203.14.168.0/22^22-29, 203.55.228.0/22^22-29, 203.57.140.0/22^22-29, 203.62.212.0/22^22-29, 203.173.56.0/22^22-29, 203.206.164.0/22^22-29, 203.206.184.0/22^22-29, 203.206.192.0/22^22-29, 203.206.204.0/22^22-29, 203.206.220.0/22^22-29, 203.215.8.0/22^22-29, 203.217.12.0/22^22-29, 203.217.28.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 202.128.110.0/23^23-29, 202.129.72.0/23^23-29, 202.129.88.0/23^23-29, 202.129.92.0/23^23-29, 202.129.106.0/23^23-29, 202.129.114.0/23^23-29, 203.7.196.0/23^23-29, 203.8.92.0/23^23-29, 203.14.174.0/23^23-29, 203.17.62.0/23^23-29, 203.21.74.0/23^23-29, 203.29.86.0/23^23-29, 203.55.140.0/23^23-29, 203.56.30.0/23^23-29, 203.56.62.0/23^23-29, 203.57.10.0/23^23-29, 203.57.136.0/23^23-29, 203.173.60.0/23^23-29, 203.206.162.0/23^23-29, 203.206.188.0/23^23-29, 203.206.202.0/23^23-29, 203.206.208.0/23^23-29, 203.206.218.0/23^23-29, 203.215.14.0/23^23-29, 203.215.18.0/23^23-29, 203.217.10.0/23^23-29, 210.55.202.0/23^23-29, 192.107.113.0/24^24-29, 192.188.107.0/24^24-29, 198.32.71.0/24^24-29, 199.98.84.0/24^24-29, 202.7.6.0/24^24-29, 202.12.87.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.46.0/24^24-29, 202.36.174.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 202.128.109.0/24^24-29, 202.129.67.0/24^24-29, 202.129.91.0/24^24-29, 202.129.94.0/24^24-29, 202.129.104.0/24^24-29, 202.129.112.0/24^24-29, 202.129.125.0/24^24-29, 202.129.126.0/24^24-29, 202.169.97.0/24^24-29, 202.176.0.0/24^24-29, 203.0.12.0/24^24-29, 203.0.84.0/24^24-29, 203.0.139.0/24^24-29, 203.0.178.0/24^24-29, 203.1.24.0/24^24-29, 203.1.78.0/24^24-29, 203.2.199.0/24^24-29, 203.3.127.0/24^24-29, 203.4.173.0/24^24-29, 203.5.184.0/24^24-29, 203.7.155.0/24^24-29, 203.7.173.0/24^24-29, 203.8.161.0/24^24-29, 203.8.219.0/24^24-29, 203.12.1.0/24^24-29, 203.12.15.0/24^24-29, 203.12.44.0/24^24-29, 203.12.236.0/24^24-29, 203.14.172.0/24^24-29, 203.14.182.0/24^24-29, 203.15.111.0/24^24-29, 203.15.129.0/24^24-29, 203.16.34.0/24^24-29, 203.17.60.0/24^24-29, 203.17.194.0/24^24-29, 203.17.249.0/24^24-29, 203.17.251.0/24^24-29, 203.18.85.0/24^24-29, 203.18.140.0/24^24-29, 203.19.70.0/24^24-29, 203.20.82.0/24^24-29, 203.20.88.0/24^24-29, 203.20.116.0/24^24-29, 203.20.132.0/24^24-29, 203.21.5.0/24^24-29, 203.21.105.0/24^24-29, 203.22.19.0/24^24-29, 203.22.96.0/24^24-29, 203.23.7.0/24^24-29, 203.24.50.0/24^24-29, 203.24.189.0/24^24-29, 203.25.109.0/24^24-29, 203.25.144.0/24^24-29, 203.25.197.0/24^24-29, 203.26.32.0/24^24-29, 203.26.86.0/24^24-29, 203.26.92.0/24^24-29, 203.26.128.0/24^24-29, 203.27.58.0/24^24-29, 203.27.60.0/24^24-29, 203.27.89.0/24^24-29, 203.27.201.0/24^24-29, 203.28.157.0/24^24-29, 203.28.174.0/24^24-29, 203.29.221.0/24^24-29, 203.30.181.0/24^24-29, 203.30.194.0/24^24-29, 203.31.13.0/24^24-29, 203.31.96.0/24^24-29, 203.31.141.0/24^24-29, 203.34.95.0/24^24-29, 203.55.151.0/24^24-29, 203.56.243.0/24^24-29, 203.57.134.0/24^24-29, 203.61.76.0/24^24-29, 203.102.166.0/24^24-29, 203.108.77.0/24^24-29, 203.112.114.0/24^24-29, 203.173.63.0/24^24-29, 203.206.161.0/24^24-29, 203.206.190.0/24^24-29, 203.206.196.0/24^24-29, 203.206.198.0/24^24-29, 203.206.201.0/24^24-29, 203.206.213.0/24^24-29, 203.206.214.0/24^24-29, 203.206.217.0/24^24-29, 203.215.12.0/24^24-29, 203.215.17.0/24^24-29, 203.215.20.0/24^24-29, 210.8.138.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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)ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060403 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS7657 descr: advertised to AS9439 by IHUG - AS7657 members: 124.168.0.0/16^16-29, 203.59.0.0/16^16-29, 203.109.128.0/17^17-29, 203.118.128.0/17^17-29, 203.173.128.0/17^17-29, 203.206.0.0/17^17-29, 203.214.0.0/17^17-29, 210.84.0.0/18^18-29, 202.161.0.0/19^19-29, 203.96.192.0/19^19-29, 203.158.32.0/19^19-29, 203.166.224.0/19^19-29, 203.173.0.0/19^19-29, 203.206.128.0/19^19-29, 203.206.224.0/19^19-29, 203.214.128.0/19^19-29, 203.217.32.0/19^19-29, 203.217.64.0/19^19-29, 202.36.16.0/20^20-29, 202.46.160.0/20^20-29, 202.137.96.0/20^20-29, 203.173.32.0/20^20-29, 203.190.192.0/20^20-29, 202.49.64.0/21^21-29, 202.126.80.0/21^21-29, 202.129.80.0/21^21-29, 202.129.96.0/21^21-29, 203.173.48.0/21^21-29, 203.206.168.0/21^21-29, 203.206.176.0/21^21-29, 203.215.0.0/21^21-29, 203.217.0.0/21^21-29, 203.217.16.0/21^21-29, 210.55.248.0/21^21-29, 198.48.0.0/22^22-29, 202.8.44.0/22^22-29, 202.49.240.0/22^22-29, 202.50.188.0/22^22-29, 202.129.68.0/22^22-29, 202.129.76.0/22^22-29, 202.129.108.0/22^22-29, 202.129.116.0/22^22-29, 202.129.120.0/22^22-29, 203.14.168.0/22^22-29, 203.55.228.0/22^22-29, 203.57.140.0/22^22-29, 203.62.212.0/22^22-29, 203.173.56.0/22^22-29, 203.206.164.0/22^22-29, 203.206.184.0/22^22-29, 203.206.192.0/22^22-29, 203.206.204.0/22^22-29, 203.206.220.0/22^22-29, 203.215.8.0/22^22-29, 203.217.12.0/22^22-29, 203.217.28.0/22^22-29, 202.21.136.0/23^23-29, 202.36.94.0/23^23-29, 202.36.230.0/23^23-29, 202.49.46.0/23^23-29, 202.49.88.0/23^23-29, 202.49.148.0/23^23-29, 202.49.176.0/23^23-29, 202.49.180.0/23^23-29, 202.61.2.0/23^23-29, 202.128.110.0/23^23-29, 202.129.72.0/23^23-29, 202.129.88.0/23^23-29, 202.129.92.0/23^23-29, 202.129.106.0/23^23-29, 202.129.114.0/23^23-29, 203.7.196.0/23^23-29, 203.8.92.0/23^23-29, 203.14.174.0/23^23-29, 203.17.62.0/23^23-29, 203.21.74.0/23^23-29, 203.29.86.0/23^23-29, 203.55.140.0/23^23-29, 203.56.30.0/23^23-29, 203.56.62.0/23^23-29, 203.57.10.0/23^23-29, 203.57.136.0/23^23-29, 203.173.60.0/23^23-29, 203.206.162.0/23^23-29, 203.206.188.0/23^23-29, 203.206.202.0/23^23-29, 203.206.208.0/23^23-29, 203.206.218.0/23^23-29, 203.215.14.0/23^23-29, 203.215.18.0/23^23-29, 203.215.20.0/23^23-29, 203.217.10.0/23^23-29, 210.55.202.0/23^23-29, 192.107.113.0/24^24-29, 192.188.107.0/24^24-29, 198.32.71.0/24^24-29, 199.98.84.0/24^24-29, 202.7.6.0/24^24-29, 202.12.87.0/24^24-29, 202.21.130.0/24^24-29, 202.36.44.0/24^24-29, 202.36.46.0/24^24-29, 202.36.174.0/24^24-29, 202.37.182.0/24^24-29, 202.49.33.0/24^24-29, 202.49.59.0/24^24-29, 202.49.63.0/24^24-29, 202.49.140.0/24^24-29, 202.49.144.0/24^24-29, 202.49.178.0/24^24-29, 202.49.186.0/24^24-29, 202.49.249.0/24^24-29, 202.50.84.0/24^24-29, 202.50.103.0/24^24-29, 202.50.255.0/24^24-29, 202.128.109.0/24^24-29, 202.129.67.0/24^24-29, 202.129.91.0/24^24-29, 202.129.94.0/24^24-29, 202.129.104.0/24^24-29, 202.129.112.0/24^24-29, 202.129.125.0/24^24-29, 202.129.126.0/24^24-29, 202.169.97.0/24^24-29, 202.176.0.0/24^24-29, 203.0.12.0/24^24-29, 203.0.84.0/24^24-29, 203.0.139.0/24^24-29, 203.0.178.0/24^24-29, 203.1.24.0/24^24-29, 203.1.78.0/24^24-29, 203.2.199.0/24^24-29, 203.3.127.0/24^24-29, 203.4.173.0/24^24-29, 203.5.184.0/24^24-29, 203.7.155.0/24^24-29, 203.7.173.0/24^24-29, 203.8.161.0/24^24-29, 203.8.219.0/24^24-29, 203.12.1.0/24^24-29, 203.12.15.0/24^24-29, 203.12.44.0/24^24-29, 203.12.236.0/24^24-29, 203.14.172.0/24^24-29, 203.14.182.0/24^24-29, 203.15.111.0/24^24-29, 203.15.129.0/24^24-29, 203.16.34.0/24^24-29, 203.17.60.0/24^24-29, 203.17.194.0/24^24-29, 203.17.249.0/24^24-29, 203.17.251.0/24^24-29, 203.18.85.0/24^24-29, 203.18.140.0/24^24-29, 203.19.70.0/24^24-29, 203.20.82.0/24^24-29, 203.20.88.0/24^24-29, 203.20.116.0/24^24-29, 203.20.132.0/24^24-29, 203.21.5.0/24^24-29, 203.21.105.0/24^24-29, 203.22.19.0/24^24-29, 203.22.96.0/24^24-29, 203.23.7.0/24^24-29, 203.24.50.0/24^24-29, 203.24.189.0/24^24-29, 203.25.109.0/24^24-29, 203.25.144.0/24^24-29, 203.25.197.0/24^24-29, 203.26.32.0/24^24-29, 203.26.86.0/24^24-29, 203.26.92.0/24^24-29, 203.26.128.0/24^24-29, 203.27.58.0/24^24-29, 203.27.60.0/24^24-29, 203.27.89.0/24^24-29, 203.27.201.0/24^24-29, 203.28.157.0/24^24-29, 203.28.174.0/24^24-29, 203.29.221.0/24^24-29, 203.30.181.0/24^24-29, 203.30.194.0/24^24-29, 203.31.13.0/24^24-29, 203.31.96.0/24^24-29, 203.31.141.0/24^24-29, 203.34.95.0/24^24-29, 203.55.151.0/24^24-29, 203.56.243.0/24^24-29, 203.57.134.0/24^24-29, 203.61.76.0/24^24-29, 203.102.166.0/24^24-29, 203.108.77.0/24^24-29, 203.112.114.0/24^24-29, 203.173.63.0/24^24-29, 203.206.161.0/24^24-29, 203.206.190.0/24^24-29, 203.206.196.0/24^24-29, 203.206.198.0/24^24-29, 203.206.201.0/24^24-29, 203.206.213.0/24^24-29, 203.206.214.0/24^24-29, 203.206.217.0/24^24-29, 203.215.12.0/24^24-29, 203.215.17.0/24^24-29, 210.8.138.0/24^24-29, 210.55.110.0/24^24-29, 210.55.184.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: pshem.k(a)staff.ihug.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060522 source: NZRR

1 0

Are there any blakjak.net mail admins on this list?
by Juha Saarinen 20 May '06

20 May '06

The subject of the message is: Re: [nznog] SORBS still causing serious problems... The address to which the message has not yet been delivered is: blakjak(a)blakjak.net Delay reason: SMTP error from remote mail server after RCPT TO:<blakjak(a)blakjak.net>: host mx.blakjak.net [202.50.176.75]: 451 Dynamic IP Addresses See: http://www.sorbs.net/lookup.shtml?xxx.xxx.xxx.xxx "Does this not go back to people using the dnsBL the wrong way... (!) People who choose to use them to _drop_ mail need to instead be using them to _score_ mail... Surely people who are losing mission-critical services due to this should instead be petitioning relevant ISPs to change their dnsBL practises?" Yes yes! I agree! On a more serious note, even Outblaze bounces messages now based on the wrong SORBS listing. @#(*)^$@!!! -- Juha Saarinen www.geekzone.co.nz/juha www.computerworld.co.nz

2 2

E mails
by suzanne gerrard 20 May '06

20 May '06

3 2

Ihug Mail Admin?
by Erin Salmon - Unleash 20 May '06

20 May '06

Hi, If there are any Ihug Mail Admins floating around on the list would you be so good as to put your hand up? One of your customers is sending out thousands of promo newsletters with several images attached. It has been running since Friday and a number of our clients are already facing several hundred dollar excess usage charges from our good friends at Telecom from downloading it all. They have stupidly put the addresses in the CC field, and I believe the problem may be that some of the CC field recipients are running MS Exchange 2000. There is a bug if it is configured for open relaying which resends emails to the list of addresses if there are more than a certain number. I recall having this issue a year or two ago, but Im a bit hazy on the details, and Im not a mail guru myself. The KB seems to be taking this convenient moment to throw an error when I try to search it. If I recall correctly, SP3 for Exchange 2000 fixed the problem, so with any luck there would only be only server in the recipient list with the problem and we can stamp it out. If anyone recalls this Exchange issue, Id appreciate a steer too. Cheers, Erin Salmon Managing Director Unleash Technology Solutions <http://www.unleash.net.nz/> Phone: +64 3 365 1273 Mobile: +64 21 877 913 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.392 / Virus Database: 268.6.1/344 - Release Date: 19/05/2006

3 3

Static IP in a hurry ?
by Richard Naylor 19 May '06

19 May '06

Anyone from Xtra online tonight ? I have one of your customers who needs a static IP number in a hurry. A family member has died and they're webcasting the tangi. We've had 3 number changes in as many minutes. - They'll pay. Rich

1 1

SORBS still causing serious problems...
by Kris Angerano 19 May '06

19 May '06

Heya NZ guys. I work for an ISP out in Oregon US (EasyStreet). And we have recently been hit hard by the mistakes at SORBS. They have mistakenly added our 209.x static group as a dynamic IP range and blocked them all. This has been happening for 5 days now. We have submitted tickets to Matthew and his crew describing the problem and we even gave him our entire Dynamic and Static IP Blocks. To no avail, our RT ticket sits there untouched and the problem is unresolved. RT 77734, 76636 The worse part is we use SORBS, so initially we couldn't even receive some of our own customers email. Since then we have whitelisted our own IP block to solve that problem. But that isn't even a band aid. I called Matthew yesterday and he explained to me about his current 'troubles' so I didn't give him a hard time about our ticket. But this is getting ridiculous. A significant part of our 209.x block is business customers with their own mail servers. They are getting frustrated and we may start to lose business because of this. If anyone cares or has their eyes open out there, we need some help please! Thanks, Kris A

5 5

Re: [nznog] SORBS still listing Telecom static IPs as dynamic...
by Donald Neal 18 May '06

18 May '06

> > > > Please don't use American English. Won't someone please think of the > > children! > > > > American English, thats an oxymoron isnt it ? > I have no doubt of the relevance of most of this thread, but it seems to have now run its course. - Donald Neal List Asministrator Donald Neal |"Email is not to be used to pass on Support Engineer |information or data. It should be NGN Operations |used only for company business." Integration & Services Division +----------------------------------- Alcatel NZ Ltd - Telecom's network operations manager 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] SORBS still listing Telecom static IPs as dynamic...
by Scott Weeks 18 May '06

18 May '06

----- Original Message Follows ----- From: "Jamie Riden" <jamesr(a)europe.com> > > No other blacklist operates like - or generates the hate > > - that S(ORBS) does. > > Actually, I've seen people say that and worse about every > single blacklist including SBL, which is probably the most > conservative one, all the way back to the MAPS original. They all say that if you're not a spammer, you have to pay LOTS of money to people they tell you to pay to be delisted? http://www.au.sorbs.net/faq/spamdb.shtml "Third and finally, if you are really not a spammer, or you are truly reformed, de-listing is relatively easy. You donate US$50 to a charity or trust approved by, and not connected with, SORBS for each spam received related to the listing. This is referred to as the SORBS 'fine'." scott

5 4

Re: [nznog] SORBS still listing Telecom static IPs as dynamic...
by Jeremy Strachan 18 May '06

18 May '06

My view is SORBS is a crock of shit, as was ORBS. If the day ends in "y" they block it ... Its called all care - no responsibility... They will blacklist entire (static) IP ranges with no warning, and no realistic way of removing the block, and treat everyone like s..t. The process is inherently flawed, because of the way static ranges end up on their list without reasonable checks. If they blocked a single IP address - then fine, its their wholesale and cavalier attitude to blocking entire ranges that is the root cause of the problem I have with S(ORBS), and why they are hated so much by people like me. No other blacklist operates like - or generates the hate - that S(ORBS) does. If they vanished tommorrow, the world would be a better place. Jeremy -----Original Message----- From: Tony Wicks [mailto:tony(a)prophecy.net.nz] Sent: Thursday, 18 May 2006 7:06 p.m. Cc: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] SORBS still listing Telecom static IPs as dynamic... >> > One would wonder why any sane mail admin wouldnt pull data from as > many sources as possible when deciding on how to score spam. > Sure, but surely there has to be some measure of accuracy involved ? I mean SORBS is about as accurate as choosing every even IP address on Monday and public holidays, every odd one on every other day. It's just not even close to being what it is supposed to be billed as. _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

3 2

ANZ Phish
by Joseph Miller 16 May '06

16 May '06

Just a heads-up: I just got sent a phishing scam email for the ANZ... Subject is ANZ Account Security Measures, included link ends up at: http://www.sunrise.cc/bbs/anz.php Relevant parts of the header as follows: Received: from [210.205.6.77] (helo=web-77.blueweb.co.kr) by exorsus.net with esmtp (Exim 4.52) id 1FgAyH-0006MQ-Oq for joff(a)XXXXXXXX.com; Wed, 17 May 2006 13:37:15 +1200 Received: (from apache(a)localhost) by web-77.blueweb.co.kr (8.11.6/8.11.6) id k4H1avJ20690; Wed, 17 May 2006 10:36:57 +0900 Date: Wed, 17 May 2006 10:36:57 +0900 Message-Id: <200605170136.k4H1avJ20690(a)web-77.blueweb.co.kr> To: joff(a)XXXXXXXXXXX.com Subject: ANZ Account Security Measures From: <service(a)anz.com> Reply-To: service(a)anz.com -- Thanks, Joseph Miller Application Developer _________________________________________ http://www.digiweb.co.nz Webhosting, Dedicated Servers, E-commerce Phone: (64 3) 351 6713 PLEASE NOTE: The information contained in this email message and any attached files may be confidential and subject to privilege. The views expressed may not necessarily be the official view of Digiweb New Zealand Limited. All technical advice and opinions are offered on a 'no-liability' basis. If you are not the intended recipient, you are notified that any use, disclosure or copying of this email is unauthorised. If you have received this email in error, please notify us immediately by reply email and delete the original. Thank you.

1 0

Xtra Nationwide outage?
by Tristram Cheer 15 May '06

15 May '06

Anybody know anything about this? I got phones ringing off the hook from people saying xtra's got a nationwide outage right now. Rat got their cable again? -- ----------------------- Tristram Cheer UberNetworks Level 1 2a Vine St Whangarei 0101 M:021-715-823 W:09-438-5472 F:09-438-5473

6 6

Xtra on Spamcop now.
by Chris Hodgetts 14 May '06

14 May '06

May 15 11:12:35 caitlin postfix/smtpd[20038]: NOQUEUE: reject: RCPT from fep03.xtra.co.nz[210.54.141.243]: 554 Service unavailable; Client host [210.54.141.243] blocked using bl.spamcop.net; Blocked - see http://www.spamcop.net/bl.shtml?210.54.141.243; from=<someuser(a)xtra.co.nz> to=<user(a)domainname.com> proto=ESMTP helo=<fep03.xtra.co.nz> May 15 11:12:35 caitlin postfix/smtpd[20038]: disconnect from fep03.xtra.co.nz[210.54.141.243]

6 5

Re: [nznog] Xtra on Spamcop now.
by Ted Grenfell 14 May '06

14 May '06

So a particular customer of ours is having all email from you marked up as spam? Kind Regards, Ted Grenfell ISP Performance Manager T +64 9 359 5854 (extn 93254) F +64 9 377 0781 M +64 27 443 5455 E ted.grenfell(a)telecom.co.nz W www.telecom.co.nz Level 11, Telecom House, 8 Hereford Street, Private Bag 92028, Auckland CBD, 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: Joseph Miller [mailto:joseph(a)digiweb.net.nz] > Sent: Monday, 15 May 2006 11:47 a.m. > To: Ted Grenfell; nznog(a)list.waikato.ac.nz > Subject: Re: [nznog] Xtra on Spamcop now. > > Ted Grenfell wrote on 15/05/06 11:35: > > What IP addresses are you sending to Joseph? > Sending to mta.xtra.co.nz (210.54.141.1) > > > Any logs you can flick through? > I'll get our mail admin to dig up some SMTP delivery logs when he gets a > spare second, and we've got > someone who's going to send us some mail headers from a junked mail > > > What exactly do you mean by "Junked"? > All the mail is being put in the xtra customer's Junk mail folder > > > > > -- > Thanks, > Joseph Miller > Application Developer > _________________________________________ > http://www.digiweb.co.nz > Webhosting, Dedicated Servers, E-commerce > Phone: (64 3) 351 6713 > > PLEASE NOTE: The information contained in this email message and any > attached files may be > confidential and subject to privilege. The views expressed may not > necessarily be the official view > of Digiweb New Zealand Limited. All technical advice and opinions are > offered on a 'no-liability' > basis. If you are not the intended recipient, you are notified that any > use, disclosure or copying > of this email is unauthorised. If you have received this email in error, > please notify us > immediately by reply email and delete the original. Thank you.

3 2