- NZNOG - lists.nznog.org

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

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. --- OBJECT BELOW CREATED: aut-num: AS24181 as-name: NZRR-AS24181 descr: TheLoop descr: WIX peering at '202.7.0.140' descr: see Citylink RT job #3454 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS24181 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: geoffs(a)nayland.school.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051027 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS24181 descr: Route set advertised to AS9439 by TheLoop - AS24181 members: 202.49.20.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: geoffs(a)nayland.school.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051027 source: NZRR

1 0

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

25 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:AS64609 descr: advertised to AS9439 by WIXanycast - AS64609 members: 202.7.6.0/23^23-29, 202.7.4.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: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050624 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64609 descr: advertised to AS9439 by WIXanycast - AS64609 members: 202.7.6.0/23^23-29, 202.7.4.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: asjl(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051026 source: NZRR

1 0

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

24 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:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - AS17746 members: 60.234.0.0/16^16-29, 203.99.0.0/19^19-29, 203.86.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 202.175.128.0/21^21-29, 210.54.56.0/21^21-29, 202.27.140.0/22^22-29, 202.49.92.0/22^22-29, 202.49.244.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.27.76.0/23^23-29, 202.49.90.0/23^23-29, 210.54.142.0/23^23-29, 202.14.83.0/24^24-29, 202.27.250.0/24^24-29, 202.36.170.0/24^24-29, 202.36.198.0/24^24-29, 202.36.227.0/24^24-29, 202.36.233.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.106.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.89.154.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 218.101.56.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-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)orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051010 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Ltd - AS17746 members: 60.234.0.0/16^16-29, 203.99.0.0/19^19-29, 203.86.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 202.175.128.0/21^21-29, 210.54.56.0/21^21-29, 202.27.140.0/22^22-29, 202.49.92.0/22^22-29, 202.49.244.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.27.76.0/23^23-29, 202.49.90.0/23^23-29, 210.54.142.0/23^23-29, 192.88.99.0/24^24-29, 202.14.83.0/24^24-29, 202.27.250.0/24^24-29, 202.36.170.0/24^24-29, 202.36.198.0/24^24-29, 202.36.227.0/24^24-29, 202.36.233.0/24^24-29, 202.37.19.0/24^24-29, 202.37.173.0/24^24-29, 202.37.194.0/24^24-29, 202.49.106.0/24^24-29, 202.49.187.0/24^24-29, 202.49.233.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.89.154.0/24^24-29, 210.54.12.0/24^24-29, 210.55.1.0/24^24-29, 210.55.8.0/24^24-29, 210.55.199.0/24^24-29, 218.101.56.0/24^24-29, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-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)orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051025 source: NZRR

1 0

New phish for Ebay
by Drew Broadley 23 Oct '05

23 Oct '05

It suggests you have a product that someone is interested in, and requests you to login to Ebay. It's quite comical as it mentions at the top "Your registered name is included to show this message originated from eBay. Learn more.", yet my 'registered' name isn't anywhere in the message. Second comical part, is the hosting produces a http://home.ro/ popup advert. Not the best i've seen but the idea is quite different. Just a heads up. - Drew

2 1

IP multicast redundancy support
by Roger Hicks 21 Oct '05

21 Oct '05

Does anyone have knowledge of a device for supporting IP multicast redundacy; arbitrating between multiple producers so that only one IP stream is being output I'm not sure of the correct terminology (or even if such a device exists) but it should have 2 or more inputs and multicast out one of the inputs. If that input goes away, it should switch to another input. Pls email me directly Thanks for your help Roger

1 0

Re: [nznog] Anyone know anything about fitnessgear.co.nz ?
by Regan Murphy 21 Oct '05

21 Oct '05

from returns page: http://www.fitnessgear.co.nz/page.aspx?code=returns Returns can delivered to the following address during normal business hours: FitnessGear.co.nz Product Returns, C\- Concept Fitness 39 Sir William Ave, East Tamaki Auckland search on concept fitness: http://www.fitforever.co.nz/ -----Original Message----- From: Craig Whitmore [mailto:lennon(a)orcon.net.nz] Sent: Friday, 21 October 2005 10:24 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Anyone know anything about fitnessgear.co.nz ? Hi there Does anyone have any information about fitnessgear.co.nz? I can't find the company on Companies Offfice (Can't even find the registered owner anywhere) Whois details gives invalid phone number Number on Website is a call centre and all they can give me is an email address to email and can't help me any further they say. Website gives me no help, no legal company name or anything. When ordering no GST Number, and if you choose to send in a Cheque it gives no details where to send it to And.. they sent 1000's of advertising spams this morning with 1/2 of them to invalid email accounts/addresses to lots of .NZ email addresses. Thanks Craig

5 4

Anyone know anything about fitnessgear.co.nz ?
by Craig Whitmore 20 Oct '05

20 Oct '05

Hi there Does anyone have any information about fitnessgear.co.nz? I can't find the company on Companies Offfice (Can't even find the registered owner anywhere) Whois details gives invalid phone number Number on Website is a call centre and all they can give me is an email address to email and can't help me any further they say. Website gives me no help, no legal company name or anything. When ordering no GST Number, and if you choose to send in a Cheque it gives no details where to send it to And.. they sent 1000's of advertising spams this morning with 1/2 of them to invalid email accounts/addresses to lots of .NZ email addresses. Thanks Craig

2 1

Re: [nznog] um, whats wrong with whois?
by Tim John 20 Oct '05

20 Oct '05

Hi Andy, I posed the same question to NZRS the other day and they have confirmed that 'working as intended' means the WhoIs service is operating normally. The issue with the 404 error is due to limiting restrictions enforced by the Registry on received WhoIs requests and the effect it is having on Domainz, means they are exceeding these restrictions in a particular timeframe. Again, it's worth pointing out that this is the Public WhoIs Interface and anyone using it is subject to the same restrictions. NZRS - please feel free to shoot me down if this is the wrong interpretation .... Tim -----Original Message----- From: Andy Linton [mailto:asjl(a)citylink.co.nz] Sent: Friday, 21 October 2005 11:55 a.m. To: nznog(a)list.waikato.ac.nz Subject: Re: [nznog] um, whats wrong with whois? David Zanetti wrote: > On Thu, 2005-10-20 at 11:53 +1300, Simon Byrnand wrote: > > >>I'm getting the same 440 error doing lookups through the Domainz >>website.... surely they count as a registrar ? Very annoying... > > > Working as intended. Would it be possible from someone at NZRS to clarify what "Working as intended" means? Thanks, andy _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

4 3

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

20 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:AS64544 descr: advertised to AS9439 by Ecentric - AS64544 members: 202.135.231.0/28^28-29, 202.135.231.32/28^28-29, 202.135.231.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: noc(a)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050928 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64544 descr: advertised to AS9439 by Ecentric - AS64544 members: 210.48.103.144/28^28-29, 202.126.87.128/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)citylink.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051021 source: NZRR

1 0