May 2007 - NZNOG - lists.nznog.org

Link-bonding scheduler on Allied Telesyn boxes
by Matthew Poole 23 May '07

23 May '07

Hi Does anyone happen to know the link-bonding scheduling method used by AT 9812T and Switchblade 2008 boxes? We've seen _reduced_ performance with link bonding on these systems when connecting them to Linux boxes, and were wondering if there's a particular scheduling method that should be enabled on the Linux end. -- Matthew Poole "Don't use force. Get a bigger hammer."

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 22 May '07

22 May '07

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, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.199.208.0/21^21-29, 210.54.56.0/21^21-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.36.170.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.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.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, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.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: ricky.tipper(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070502 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS17746 descr: advertised to AS9560 by Orcon Internet Limited - AS17746 members: 60.234.0.0/16^16-29, 156.62.0.0/16^16-29, 202.150.96.0/19^19-29, 203.99.0.0/19^19-29, 203.96.192.0/20^20-29, 219.88.128.0/20^20-29, 219.88.240.0/20^20-29, 116.199.208.0/21^21-29, 210.54.56.0/21^21-29, 202.127.8.0/22^22-29, 210.54.148.0/22^22-29, 210.55.12.0/22^22-29, 202.37.82.0/23^23-29, 202.36.170.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.187.0/24^24-29, 202.49.233.0/24^24-29, 202.49.246.0/24^24-29, 202.50.167.0/24^24-29, 202.50.246.0/24^24-29, 202.174.160.0/24^24-29, 203.86.200.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, 202.27.188.128/25^25-29, 210.55.0.0/25^25-29, 210.55.180.128/26^26-29, 210.55.193.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: ricky.tipper(a)team.orcon.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070522 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 21 May '07

21 May '07

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: AS9560:RS-ROUTES:AS17649 descr: Route set advertised to AS9560 by DMZGlobal Ltd - AS17649 members: 203.144.40.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: john.pawson(a)dmzglobal.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070521 source: NZRR

1 0

.co.uk zone changes.
by Andy Davidson 18 May '07

18 May '07

Hi, How long does it take for changes to the .co.nz domains take to be reflected in whois and dns ? I am not native to the region, so don't have existing experience with this. A client of mine registered a .nz domain for a project of theirs through melbourneit. I changed the dns servers on their site, and it said that the change has been submitted, but 'dig ns theirdomain @202.46.190.130' still shows the original nameservers, as does whois. Any clues ? cheers -a

7 7

Notification of NZRR Database changes
by NZRR Database Notifications 17 May '07

17 May '07

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:AS10022 descr: advertised to AS9560 by Datacom Systems Auckland - AS10022 members: 202.36.8.0/21^21-29, 202.175.128.0/21^21-29, 202.14.20.0/22^22-29, 202.14.82.0/23^23-29, 202.36.198.0/23^23-29, 192.203.216.0/24^24-29, 202.14.84.0/24^24-29, 202.27.76.0/24^24-29, 202.27.140.0/24^24-29, 202.27.143.0/24^24-29, 202.27.250.0/24^24-29, 202.36.233.0/24^24-29, 210.55.5.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: idc(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060807 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS10022 descr: advertised to AS9560 by Datacom Systems - AS10022 members: 202.36.8.0/21^21-29, 202.175.128.0/21^21-29, 202.14.20.0/22^22-29, 202.14.82.0/23^23-29, 202.36.198.0/23^23-29, 192.188.185.0/24^24-29, 192.203.216.0/24^24-29, 202.14.84.0/24^24-29, 202.27.76.0/24^24-29, 202.27.140.0/24^24-29, 202.27.143.0/24^24-29, 202.27.250.0/24^24-29, 202.36.233.0/24^24-29, 202.175.137.0/24^24-29, 202.175.138.0/24^24-29, 210.55.5.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: nigelm(a)datacom.co.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070517 source: NZRR

1 0

[Fwd: Security Survey]
by Philip Smith 14 May '07

14 May '07

Forwarded on behalf of Danny McPherson. (And apologies for any duplicates!) -------- Original Message -------- Subject: Security Survey Date: Mon, 14 May 2007 15:55:00 -0600 From: Danny McPherson <danny(a)tcb.net> Folks, It's time for the Infrastructure Security Survey again! If you're willing to complete the survey please go here to receive a token (which will be mailed to you with a URL for response input): https://sec-survey.tcb.net/index.php?sid=1 You can find the previous editions of the survey report here: http://www.tcb.net/ISP_Security_Report-2H2005.pdf http://www.tcb.net/2006-WISR.pdf If you have any questions, comments or concerns please let me know. Thanks in advance! -danny danny(a)tcb.net

1 0

TelstraClear DSL AKL-CHC
by Russell Tester 14 May '07

14 May '07

We have a customer experiencing problems since around mid-day Friday with their Auckland site talking to their Christchurch site via TCL on net DSL. The problem appears to be with the AKL site that can also not reach a number of our other DSL fed TCL customers in CHC, yet all other internet access appears to be fine. Whilst we have a TCL tech visiting the ALK site (some time), I'm interested if anyone else has encountered similar issues? Also if someone in ALK on TCL on net DSL could reply with a trace to 203.97.49.85 id appreciate this. Cheers, Russell Tester ServerWorks Ltd

2 3

Re: [nznog] Whois Server
by Ewen McNeill 14 May '07

14 May '07

In message <007701c795ac$c9249580$966e000a(a)craigcdaacab45>, "Craig Spiers" write s: >I've been doing whois lookups against whois.srs.net.nz for a few domains we >host at work, mainly to look at the billed until date. However, small >problem.. query 10 domains and suddenly they block you. There is an automatic blacklist which is triggered by a rate of recent requests from the same IP address (and/or netblock). Querying, eg, 10 domains a day isn't a problem (I regularly do this by hand in the course of my work), but querying 10 domains one after another, with no delay, from a script is likely to trigger the blacklist. After a quiet period (some hours?) the IP will fall back out of the automatic blacklist. (I believe there's also a manual blacklist for particularly troublesome offenders.) If your queries are not time critical (and it sounds like from later posts to NZNOG they're not), I'd suggest slowing your queries down so that you're only doing, eg a dozen queries an hour. (I'm assuming given the choice of forum that you have a legitimate reason for doing this. Illegitimate purposes are likely to get you permanently blacklisted anyway.) It may also be helpful to know that at least some registrars provide a customer-usable interface to the whois XML interface bulk query for the domains belonging to you that are registered through them. Which may be an easier way to get the information that you want. Ewen

1 0

Whois Server
by Craig Spiers 13 May '07

13 May '07

Hi All, I've been doing whois lookups against whois.srs.net.nz for a few domains we host at work, mainly to look at the billed until date. However, small problem.. query 10 domains and suddenly they block you. Has anyone else come across this? if so who do you talk to to get the limit increased? Cheers, Craig - Solarix

5 5

Re: [nznog] Whois Server
by Craig Spiers 13 May '07

13 May '07

yeah, i didnt think they would be.. any idea what the limit is set to? I dont mind say querying 1 domain every hour (extreme limit) but time is not critical with what im using it for. Just want to update billed until date in our database every month or so. I dont care if it takes all month to run over ~ 200 domains, as long as there's a date in there :) Cheers _____ From: Tim John - Domainz [mailto:tim.john(a)domainz.net.nz] Sent: Monday, May 14, 2007 10:26 AM To: Craig Spiers Subject: RE: [nznog] Whois Server Hi Craig, If you use the public whois or the lookup utility on the DNC site, there is a rate limit applied if a certain number of queries are attempted in a short space of time. If you happen to be an authorised Registrar, then you should connect via the XML gateway where rate limiting is not applied (or at least it's set a lot higher). I don't think the NZRS are interested in a conversation to increase this threshold on the public site. Been there, done it, got the T-shirt ! Tim From: Craig Spiers [mailto:craig(a)spiers.gen.nz] Sent: Monday, 14 May 2007 10:20 a.m. To: 'nznog' Subject: [nznog] Whois Server Hi All, I've been doing whois lookups against whois.srs.net.nz for a few domains we host at work, mainly to look at the billed until date. However, small problem.. query 10 domains and suddenly they block you. Has anyone else come across this? if so who do you talk to to get the limit increased? Cheers, Craig - Solarix

1 0