- NZNOG - lists.nznog.org

2day Peering
by John Johnston 27 Nov '05

27 Nov '05

Guys, The 2day and ICONZ networks have been combined as of last Friday and as such you will be receiving the 2day prefix announcements via ICONZ currently. Anyone that had a peer with 2day and not ICONZ, and wish to peer direct with ICONZ please drop me an email with your details. Peering with 192.203.154.80 and 81 with be reestablished using AS4770 at a later date. Regards John Johnston ICONZ New Zealand Limited DDI: +64 9 977 3500 FAX: +64 9 977 3535 Mobile: 021 277 5692 Email: john.johnston(a)iconz.net 0800 THE NET www.iconz.net

3 3

UberNetworks
by Tristram J. Cheer 24 Nov '05

24 Nov '05

To the NZNOG list UberNetworks is a new WISP operating in Whangarei, our wireless network has just entered its live trails with a small client base. Currently we are operating in the 202.49.132.0/27 range and wish to post details of our operation on the list, contact details are as follows P.O Box 5083 Phone: 09-438-5472 Fax: 09-438-5473 NOC E-mail: noc(a)ubernet.co.nz NOC 24 Hour phone: 021715823 Since we don't currently have an AS(We are in trails after all) so our details have not been sent to http://usenet.net.nz/noc/ at this point We have the ability to peer at APE and invite interested parties to contact peering(a)ubernet.co.nz if you are interested in peering. Above internet services we have some clients with hosted dedicated servers so I invite all companies peering at APE to get in touch Now that the formal stuff is out of the way I have a favor to ask from the list: Does anybody have a server sitting on a APE connection that they would be willing to allow us to download and upload a 10mbit file to for throughput testing on Monday the 28th? FTP access suits us best, would only need it for the day and the file is random data from /dev/null, if anyone does can they contact me via tristram(a)ubernet.co.nz or via my mobile listed below And just to make sure its on topic there is some beer for anyone able to grant us the above request Cheers ------------------------------------- Tristram Cheer UberNetworks T:(09)438-5472 F:(09)438-5473 M:(021)715-823

4 3

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

24 Nov '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:AS24005 descr: Route set advertised to AS9560 by SafeNZ - AS24005 members: 202.137.240.0/21^21-29, 203.98.6.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: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050909 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24005 descr: advertised to AS9560 by SafeNZ Networks Limited - AS24005 members: 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.98.6.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: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051125 source: NZRR

1 0

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

24 Nov '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:AS24005 descr: advertised to AS9439 by safenz networks limited - AS24005 members: 203.98.6.0/24^24-29, 203.97.68.0/28^28-29, 219.88.140.0/24^24-29, 60.234.32.0/23^23-29, 202.137.240.0/21^21-29, 202.50.252.0/24^24-29, 203.167.254.0/24^24-29, 203.167.255.0/24^24-29, 203.97.6.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: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20050420 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24005 descr: advertised to AS9439 by SafeNZ Networks Limited - AS24005 members: 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.98.6.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: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051125 source: NZRR

1 0

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

24 Nov '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:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051117 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9889 descr: advertised to AS9560 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051125 source: NZRR

1 0

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

24 Nov '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:AS9889 descr: advertised to AS9439 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051117 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9889 descr: advertised to AS9439 by Maxnet - AS9889 members: 202.89.32.0/19^19-29, 203.89.160.0/19^19-29, 210.55.100.0/22^22-29, 210.55.104.0/22^22-29, 192.138.251.0/24^24-29, 202.6.5.0/24^24-29, 202.27.204.0/24^24-29, 202.36.70.0/24^24-29, 202.36.227.0/24^24-29, 202.37.72.0/24^24-29, 202.37.181.0/24^24-29, 202.49.141.0/24^24-29, 202.150.102.0/24^24-29, 203.97.42.0/24^24-29, 210.54.13.0/24^24-29, 210.54.142.0/24^24-29, 210.55.169.0/24^24-29, 210.55.214.0/24^24-29, 210.55.230.0/24^24-29, 203.167.219.56/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: david.fox(a)maxnet.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20051125 source: NZRR

1 0

Re: [nznog] DNS serving IPs outside controlled range
by Brendan Murray 23 Nov '05

23 Nov '05

Stu Fleming <stewart(a)wic.co.nz> wrote: > I have a...friend, let's say...who operates a DNS server at a small > ISP. In a few of the zone files, there are A records that resolve to IP > addresses outside of the Class C that my..friend...controls. My friend > has been told that this is "against the rules" and that it is "causing > problems". I suspect I know what's happening here. It was a particular vexation for me some time ago when I was responsible for a network, and I'm going to guess it's the same one as your ...friend.... is dealing with, and found that 3rd parties were registering IP addresses with 'my' Class B as some other domain name. i.e I 'control' 172.17.0.0/24 as example.com and someone with a host in my range has registered a domain with an external supplier as someotherexample.com using 172.17.224.0/24 ip numbers, say. I looked into it, and asked around, and found that there were no rules stopping it, and no technology. I eventually realised that the external provider was outside my range of control and had to control my clients by telling them that it was against the AUP (as it was) for them to do it this way. If you have a relationship with this other network provider then you're probably better off doing your best to help them and their clients conform to their AUP, on a strictly "getting along with people" thing. But you're doing nothing anyone can stop. > > Questions: > - is resolving an A record outwith the delegated IP range "against the > rules"? discourteous is about it once they've asked you to stop. But you've got paying customers. > - if so, is there any documentation of the rules? should be against their internal AUP and so its someone elses problem > - what potential problems could this cause to the network that contains > the IP address to which the A records point? reverse lookups for what you're hosting resolve to their network address range. Some mail services might choke More likely, (assuming its who I think it is) they're shortly going to change a lot of internal IP numbers and what you're doing might cause them headaches in that process. Not the best way to maintain a relationship. -- Brendan Murray brendan(a)wolfhoundsecurity.com The Observation Post www.wolfhoundsecurity.com 14 Centre Road Phone: +64-3-4543282 RD 2 Ocean Grove Fax: +64-3-4543285 Dunedin, New Zealand Mobile: +64-21-1153290 PGP Key = http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE89566 Key fingerprint = 6F3C 3197 8C30 47EF 4E1A 5781 5DCA D13C E895 6106

3 2

DNS serving IPs outside controlled range
by Stu Fleming 22 Nov '05

22 Nov '05

I have a...friend, let's say...who operates a DNS server at a small ISP. In a few of the zone files, there are A records that resolve to IP addresses outside of the Class C that my..friend...controls. My friend has been told that this is "against the rules" and that it is "causing problems". Questions: - is resolving an A record outwith the delegated IP range "against the rules"? - if so, is there any documentation of the rules? - what potential problems could this cause to the network that contains the IP address to which the A records point? Thanks for any advice. Regards, Stu

6 5

International problems
by robbie.gernandt＠apn.co.nz 21 Nov '05

21 Nov '05

Hi all Anybody experiencing International connection problems at the moment? I can't get to sites like google or cisco through Telecom or TelstraClear cheers Robbie Gernandt Network Consultant APN Holdings NZ Limited E-Mail: robbie.gernandt(a)apn.co.nz Mobile: (64) 21 736 086 DDI: (64) 9 373 9577 Fax: (64) 9 373 6411 ******************************************************************************** NOTICE This email and any attachments are confidential. They may contain privileged information or copyright material. If you are not an intended recipient, you should not read, copy, use or disclose the contents without authorisation and we request you contact us at once by return email. Please then delete the email and any attachments from your system. We do not accept liability in connection with computer viruses, data corruption, delay, interruption, unauthorised access or unauthorised amendment. Any views expressed in this email and any attachments do not necessarily reflect the views of the company. ********************************************************************************

5 6

FYI: GGIS Service Message : Major
by Craig Humphrey 21 Nov '05

21 Nov '05

Nice of them to let us know about it, an hour after it had been resolved... > -----Original Message----- > From: noc(a)GG [mailto:noc(a)GG] > Sent: Tuesday, November 22, 2005 1:45 PM > To: global-gateway outage contacts > Subject: GGIS Service Message : Major > > Upstream Provider Outage Notification > > Global-Gateway Internet did experience service disruption > which began at 1225. > > You would have experienced service disruption of your > international service until this problem was resolved at 1250. > > GGIS apologises for any inconvenience to you or your customers. > Logged by XXXXXXXX on Tue Nov 22 13:44:12 2005 >

1 0