- NZNOG - lists.nznog.org

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

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:AS18400 descr: Route set advertised to AS9439 by Xtreme - AS18400 members: 218.101.2.0/23^23-29, 203.167.235.0/24^24-29, 218.101.4.0/24^24-29, 218.101.8.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: support(a)xtreme.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050818 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS18400 descr: advertised to AS9439 by Xtreme Networks Limited - AS18400 members: 203.171.32.0/20^20-29, 218.101.2.0/23^23-29, 202.36.162.0/24^24-29, 203.167.235.0/24^24-29, 218.101.4.0/24^24-29, 218.101.8.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: soa(a)xtreme.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051021 source: NZRR

1 0

Re: [nznog] xtra
by VeNoMouS 20 Oct '05

20 Oct '05

if you really need to pump the email out setup a smtp for xtra.co.nz to mta5-rme.xtra.co.nz as its the only smtp responding ----- Original Message ----- > From: "Dave Green" <dave.green(a)paradise.net.nz> > To: <nznog(a)list.waikato.ac.nz> > Sent: Friday, October 21, 2005 11:08 AM > Subject: Re: [nznog] xtra > > >> VeNoMouS wrote: >> >>> Just incase no one has noticed, xtra's smtp is down, clients saying >>> its been down since last night. >> >> Hard not to really. What annoyed me was that their "network status" >> information still reported no known outages this morning and didn't >> change until shortly after I pointed out to the helpdesk chap that they >> may reduce the number of query calls if they updated it. >> >> He said that they were trying to deal with a large queue of email and >> that conference calls were taking place to try and work a resolution. >> >> Dave >> >> _______________________________________________ >> NZNOG mailing list >> NZNOG(a)list.waikato.ac.nz >> http://list.waikato.ac.nz/mailman/listinfo/nznog >> >> >

6 6

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. --- OBJECT BELOW CREATED: aut-num: AS23959 as-name: NZRR-AS23959 descr: DTS descr: WIX peering at '202.7.0.143' descr: see Citylink RT job #3531 admin-c: RPA1-NZRR tech-c: RPA1-NZRR import: from AS9439 accept ANY AND NOT fltr-bogons export: to AS9439 announce AS23959 notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: milton(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051021 source: NZRR --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS23959 descr: Route set advertised to AS9439 by DTS - AS23959 members: 202.20.0.0/21^21-29, 202.68.80.0/21^21-29, 202.68.88.0/22^22-29, 202.36.204.0/23^23-29, 202.68.92.0/23^23-29, 192.100.53.0/24^24-29, 192.173.17.0/24^24-29, 202.36.137.0/24^24-29, 202.36.173.0/24^24-29, 202.37.197.0/24^24-29, 202.46.190.0/24^24-29, 202.49.158.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: milton(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051021 source: NZRR

1 0

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. --- OBJECT BELOW DELETED: route-set: AS9439:RS-ROUTES:AS23959 descr: Route set advertised to AS9439 by DTS - AS23959 members: 202.20.0.0/21^21-29, 202.68.80.0/21^21-29, 202.68.88.0/22^22-29, 202.36.204.0/23^23-29, 202.68.92.0/23^23-29, 192.100.53.0/24^24-29, 192.173.17.0/24^24-29, 202.36.137.0/24^24-29, 202.36.173.0/24^24-29, 202.37.197.0/24^24-29, 202.46.190.0/24^24-29, 202.49.158.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: milton(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051021 source: NZRR

1 0

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. --- OBJECT BELOW CREATED: route-set: AS9439:RS-ROUTES:AS23959 descr: Route set advertised to AS9439 by DTS - AS23959 members: 202.20.0.0/21^21-29, 202.68.80.0/21^21-29, 202.68.88.0/22^22-29, 202.36.204.0/23^23-29, 202.68.92.0/23^23-29, 192.100.53.0/24^24-29, 192.173.17.0/24^24-29, 202.36.137.0/24^24-29, 202.36.173.0/24^24-29, 202.37.197.0/24^24-29, 202.46.190.0/24^24-29, 202.49.158.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: milton(a)dts.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051021 source: NZRR

1 0

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

20 Oct '05

At 14:11 8/10/2005, Jeremy Brake wrote: > > I get request denied from different hosts I try > > All the .nz domain suffix > > > > version: 1.23.0 > > query_datetime: 2005-10-08T13:34:36+13:00 > > domain_name: xtra.co.nz > > query_status: 440 Request Denied > > % > > % > > > > Regards > > Dan > > > > _______________________________________________ > > NZNOG mailing list > > NZNOG(a)list.waikato.ac.nz > > http://list.waikato.ac.nz/mailman/listinfo/nznog > > >This is normal behaviour. When the .nz servers are under load, requests >not coming from registrars are dropped. Either run the whois from a >registrar website (or dnc.org.nz) or wait an hour or 2 and try again, and >it should work fine. :) I'm getting the same 440 error doing lookups through the Domainz website.... surely they count as a registrar ? Very annoying... Regards, Simon

6 6