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
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
>>
>>
>
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
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
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
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
Quick work around for those that need it is to use smtpr.xtra.co.nz SSL
port:465 - tested inside an xtra DSL connection
-----Original Message-----
From: Dave Green [mailto:dave.green(a)paradise.net.nz]
Sent: Friday, 21 October 2005 11:08 a.m.
To: nznog(a)list.waikato.ac.nz
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
Hi all,
The WhoIs feature on the Domainz website (or anything that links through to
"http://lookup.domainz.net.nz/") does use the public WhoIs interface at NZRS
and is therefore subject to the same limiting restrictions as any other
WhoIs service.
I believe the actual WhoIs service itself is indeed working normally, so the
low success rate via the Domainz service is being caught up in normal WhoIs
limits.
Thanks,
Tim
-----Original Message-----
From: Simon Byrnand [mailto:simon(a)igrin.co.nz]
Sent: Thursday, 20 October 2005 11:53 a.m.
To: nznog(a)list.waikato.ac.nz
Subject: Re: [nznog] um, whats wrong with whois?
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
_______________________________________________
NZNOG mailing list
NZNOG(a)list.waikato.ac.nz
http://list.waikato.ac.nz/mailman/listinfo/nznog
