Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
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.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9439:RS-ROUTES:AS42
descr: advertised to AS9439 by Packet Clearing House - AS42
members: 192.36.148.0/24^24-29,
194.146.106.0/24^24-29,
194.146.107.0/24^24-29,
194.146.108.0/24^24-29,
199.7.77.0/24^24-29,
199.7.64.0/24^24-29,
204.61.210.0/24^24-29,
204.61.210.0/23^23-29,
204.61.212.0/23^23-29,
204.61.216.0/23^23-29
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: scg(a)pch.net
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20050219
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS42
descr: advertised to AS9439 by PCH - AS42
members: 74.80.64.0/18^18-29,
199.249.112.0/20^20-29,
203.119.88.0/23^23-29,
204.61.216.0/23^23-29,
198.49.1.0/24^24-29,
198.182.167.0/24^24-29,
199.4.137.0/24^24-29,
199.7.64.0/24^24-29,
199.7.77.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: jonny(a)pch.net
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100715
source: NZRR
------------------------------------------------------------
Root Zone DNSSEC Deployment
Technical Status Update 2010-07-14
This is the eleventh of a series of technical status updates intended
to inform a technical audience on progress in signing the root zone
of the DNS.
RESOURCES
Details of the project, including documentation published to date,
can be found at <http://www.root-dnssec.org/>.
We'd like to hear from you. If you have feedback for us, please
send it to rootsign(a)icann.org.
KSK CEREMONY 2 COMPLETE
The second KSK ceremony for the root zone was completed this week
in El Segundo, CA, USA. The Ceremony Administrator was Mehmet Akcin.
The second production Key Signing Request (KSR) generated by VeriSign
has now been processed by ICANN using the root zone KSK generated
in KSK Ceremony 1, and the resulting Signed Key Response (SKR) has
been accepted by VeriSign. This SKR contains signatures for Q4 2010,
for use between 2010-10-01 and 2010-12-31.
Audit materials relating to both the first and second ceremonies
will be published today at <http://www.iana.org/dnssec/>.
FULL PRODUCTION SIGNED ROOT ZONE
The transition from Deliberately-Unvalidatable Root Zone (DURZ) to
production signed root zone is scheduled take place on 2010-07-15
within a maintenance window which begins at 1930 UTC and ends at
2330 UTC. This is the usual window for the generation and distribution
of root zones with SOA serials ending in 01.
PLANNED DEPLOYMENT SCHEDULE
Already completed:
2010-01-27: L starts to serve DURZ
2010-02-10: A starts to serve DURZ
2010-03-03: M, I start to serve DURZ
2010-03-24: D, K, E start to serve DURZ
2010-04-14: B, H, C, G, F start to serve DURZ
2010-05-05: J starts to serve DURZ
2010-06-16: First Key Signing Key (KSK) Ceremony
2010-07-12: Second Key Signing Key (KSK) Ceremony
To come:
2010-07-15: Distribution of validatable, production, signed root
zone; publication of root zone trust anchor
(Please note that this schedule is tentative and subject to change
based on testing results or other unforeseen factors.)
Hello NZNOG...
As most of you will know, I sold Orcon and have been on leave from the industry for 3 years.
I am looking at getting back into the IT game, and so have started lurking on NZNOG again.
One of the first things I would like to do is get set up again as a domain name registrar with the DNC.
I don't have the technical capability myself, so If there is anyone on list who has the technical skills to build me a fully automated registry system along the likes of www.domains4less.co.nz or www.registerdirect.co.nz then could you please contact me.
Another option would be for me to purchase the code from an existing registrar and potentially have them host a service on my own brand with my own nameservers etc.
In addition:
- I am actively seeking domain / hosting / telco / voip / IT services companies to acquire, so please let me know if you hear anything, or have a company you wish to sell
- I currently have zero staff, so am looking to hire the right people to help me grow something new. If you are a technical person looking for a job and you are able to do "ISP setup stuff" like configure nameservers, apply for IP ranges, set up domain name registration systems, set up mail-servers, configure retail and wholesale hosting platforms, fiddle with VOIP and networking hardware etc, or you are a good web-applications programmer then please contact me if you would like to talk about a job.
Kind regards,
Seeby Woodhouse
Voyager Internet Ltd: email: seeby(a)voyager.co.nz website: http://www.voyager.co.nz
mobile: +64 21 366 666
P O Box 137-272, Parnell, Auckland, New Zealand
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
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.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9560:RS-ROUTES6:AS9503
descr: Route set advertised to AS9560 by FX Networks - AS9503
mp-members: 2402:6000:0:0:0:0:0:0/32^32-64,
2404:3800:0:0:0:0:0:0/32^32-64,
2001:DCE:0:0:0:0:0:0/32^32-64,
2001:DCE:E000:0:0:0:0:0/48^48-64,
2001:DF0:4A:0:0:0:0:0/48^48-64,
2404:1800:0:0:0:0:0:0/32^32-64,
2001:4530:0:0:0:0:0:0/32^32-64,
2400:B400:0:0:0:0:0:0/32^32-64,
2404:130:0:0:0:0:0:0/32^32-64,
2403:E00:0:0:0:0:0:0/32^32-64
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: tim(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100712
source: NZRR
REPLACED BY:
route-set: AS9560:RS-ROUTES6:AS9503
descr: Route set advertised to AS9560 by FX Networks - AS9503
mp-members: 2402:6000:0:0:0:0:0:0/32^32-64,
2404:3800:0:0:0:0:0:0/32^32-64,
2001:DCE:0:0:0:0:0:0/32^32-64,
2001:DCE:E000:0:0:0:0:0/48^48-64,
2001:DF0:4A:0:0:0:0:0/48^48-64,
2404:1800:0:0:0:0:0:0/32^32-64,
2001:4530:0:0:0:0:0:0/32^32-64,
2400:B400:0:0:0:0:0:0/32^32-64,
2404:130:0:0:0:0:0:0/32^32-64,
2403:E00:0:0:0:0:0:0/32^32-64,
2400:1200:0:0:0:0:0:0/32^32-64
admin-c: RPA1-NZRR
tech-c: RPA1-NZRR
notify: rpsl-admin(a)nzix.net
notify: nznog(a)list.waikato.ac.nz
notify: tim(a)fx.net.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100713
source: NZRR
------------------------------------------------------------
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
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.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9439:RS-ROUTES:AS10022
descr: advertised to AS9439 by Datacom Systems (Wellington) Limited - AS10022
members: 202.175.142.0/23^23-29,
192.203.216.0/24^24-29,
202.27.77.0/24^24-29,
202.36.12.0/24^24-29,
202.36.198.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: matthewda(a)datacom.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20090224
source: NZRR
REPLACED BY:
route-set: AS9439:RS-ROUTES:AS10022
descr: advertised to AS9439 by Datacom Systems Ltd. - AS10022
members: 202.175.142.0/23^23-29,
192.88.190.0/24^24-29,
192.203.216.0/24^24-29,
202.27.77.0/24^24-29,
202.36.12.0/24^24-29,
202.36.198.0/24^24-29,
202.49.216.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: tusharp(a)datacom.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100713
source: NZRR
------------------------------------------------------------
Dear Colleague,
This is to notify you that one or more objects in which you are
designated for notification have been modified in the NZRR routing
registry database.
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.
Diagnostic output:
------------------------------------------------------------
---
PREVIOUS OBJECT:
route-set: AS9281:RS-ROUTES:AS38477
descr: advertised to AS9281 by Unleash - AS38477
members: 116.90.128.0/20^20-29,
113.130.120.0/22^22-29,
131.203.134.0/23^23-29,
202.6.116.0/23^23-29,
131.203.133.0/24^24-29,
192.138.251.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)unleash.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100504
source: NZRR
REPLACED BY:
route-set: AS9281:RS-ROUTES:AS38477
descr: advertised to AS9281 by Unleash - AS38477
members: 116.90.128.0/20^20-29,
113.130.120.0/22^22-29,
182.50.160.0/22^22-29,
202.6.116.0/23^23-29,
192.138.251.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)unleash.co.nz
mnt-by: MAINT-NZRR-NZ
changed: rpsl-admin(a)nzix.net 20100712
source: NZRR
------------------------------------------------------------
