- NZNOG - lists.nznog.org

Re: [nznog] [Fwd: Re: NZNOG '06 videos]
by Richard Naylor 28 Oct '06

28 Oct '06

>On Thu, 2006-10-12 at 18:29 +1300, Jeremy Naylor wrote: >>Hey guys, >>Just a quick note to let you know that the videos for the talks at NZNOG >>'06 are now available. >>Sorry for the delay with them. >>They're at: http://www.r2.co.nz/20060323 > >Is there any easy way to download them without resorting to using >mplayer -dumpstream? If theres enough interest or demand, I put a copy onto an HTTP server. See if theres interest on nznog. Rich

1 0

Fwd: The Postel Network Operator's Scholarship
by Joe Abley 27 Oct '06

27 Oct '06

Begin forwarded message: > From: Joe Abley <jabley(a)ca.afilias.info> > Date: 13 October 2006 10:30:13 EDT (CA) > To: nanog-announce(a)nanog.org > Subject: The Postel Network Operator's Scholarship > > The Internet Society (ISOC) a 501c(3) corporation (http:// > www.isoc.org/isoc/general/trustees/incorp.shtml) has agreed to > accept a restricted donation from an anonymous source to be known as > the "Postel Network Operator's Scholarship." > > The Scholarship will be awarded annually to a recipient selected by a > "Selection Committee" consisting of a representative of the then > serving Board of ARIN (The American Registry of Internet Numbers - > http://www.arin.net) and a representative of the then serving > Steering Committee of NANOG (The North American Network Operator's > Group - http://www.nanog.org) > > The award is intended to enable a deserving network operator who > would not otherwise be able to attend the Joint Meeting to do so, and > whose attendance at the Joint Meeting will continue to build on the > legacy of Jon's lifetime contribution to the Internet. > > The Selection Committee will develop an open and public application > process, and will "whimsically" select the annual recipient > exclusively in response to the question: "What Would Jon Do?" if he > were asked to select a recipient. There are no criteria or > restrictions or other requirements, including but not limited to > nationality, location, age, or gender. > > The scholarship will cover the costs of travel from the recipient's > home city to the Joint Meeting. It will also cover the costs of > Hotel accommodation at the Conference Hotel. It will include a daily > stipend for food, beverages, and incidentals. It is expected that > the attendence fee for the meetings will be waived by ARIN and NANOG. > > The membership of the Selection Committee shall not be changed except > in the event that the membership of either the Board (in the case of > ARIN) or the Steering Committee (in the case of NANOG) ceases to be > based on the popular vote of the community each serve; in which case > the member whose process changes will be replaced by a similar body > that is based on the popular vote of the community that was served by > the ineligible member, and which will be appointed at the sole > discretion of the Board of Trustees of the Internet Society, and > under the same terms as the initial Selection Committee. > > At its option, the Internet Society may increase or decrease the > number of recipients each year based on the current state of the > Scholarship Fund, and the variable costs of travel and accommodation. >

1 0

Re: [nznog] Moving DNS providers - best practice.
by Peter Mott 26 Oct '06

26 Oct '06

On 27/10/2006, at 3:23 PM, Mark Foster wrote: > Ask them do a whois on the domain, and then point out that if they are > carrying Authoritive NS records for a domain which the rootservers are > pointing elsewhere - whois tells you this - they are breaking the DNS. One could also encourage folks to use different name servers for caching and not allow recursion on their authoritative servers. That way if they claim to be authoritative and they are no longer, nobody cares. I seem to remember having a discussion about this very thing with a large provider about 6 years ago and they were not interested in any form of co-operation that would prevent client internet experience being broken when a change of delegation took place. They didn't have the capacity to understand the problem let alone a resolve to solve it. I wonder if anything has changed :-) regards Peter Mott -/-

2 1

Re: [nznog] Moving DNS providers - best practice.
by Mark Foster 26 Oct '06

26 Oct '06

On Fri, 27 Oct 2006, Peter Mott wrote: > On 27/10/2006, at 3:23 PM, Mark Foster wrote: > >> Ask them do a whois on the domain, and then point out that if they are >> carrying Authoritive NS records for a domain which the rootservers are >> pointing elsewhere - whois tells you this - they are breaking the DNS. > > One could also encourage folks to use different name servers for caching and > not allow recursion on their authoritative servers. That way if they claim > to be authoritative and they are no longer, nobody cares. > > I seem to remember having a discussion about this very thing with a large > provider about 6 years ago and they were not interested in any form of > co-operation that would prevent client internet experience being broken when > a change of delegation took place. They didn't have the capacity to > understand the problem let alone a resolve to solve it. I wonder if anything > has changed :-) Actually a possible 'reason' for this just occurred to me. If you're buying a DNS hosting service from an ISP, does the ISP have the right to cancel said hosting service without authority from the customer? This, I believe, has been a cited reason _not_ to remove legacy DNS (despite what the registry says) for at least one provider i've heard of before now. It makes the issue one of customer-provider liason - and one of monetary/commercial significance - instead of dns/operational significance. I favour the latter. But there may be a valid point here... Mark.

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 25 Oct '06

25 Oct '06

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: advertised to AS9560 by SafeNZ Networks Limited - AS24005 members: 202.56.32.0/20^20-29, 202.56.48.0/21^21-29, 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 20060217 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24005 descr: advertised to AS9560 by SafeNZ Networks - AS24005 members: 202.56.32.0/20^20-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.167.254.0/23^23-29, 202.50.252.0/24^24-29, 203.97.6.0/24^24-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 20061026 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 25 Oct '06

25 Oct '06

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: 202.56.32.0/20^20-29, 202.56.48.0/21^21-29, 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 20060217 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24005 descr: advertised to AS9439 by SafeNZ Networks - AS24005 members: 202.56.32.0/20^20-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.167.254.0/23^23-29, 202.50.252.0/24^24-29, 203.97.6.0/24^24-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 20061026 source: NZRR

1 0

Network Specialist - position available at the National Library Wellington
by Patrick Mchale 25 Oct '06

25 Oct '06

We currently have a position available for a Network Specialist at the National Library of New Zealand, Wellington Vacancy Number: NL1881 http://www.jobs.govt.nz/jobs/viewjob.aspx?OpportunityID=31009 for more details of the National Library http://www.natlib.govt.nz/en/about/2working.html Regards Patrick McHale Network Specialist National Library of New Zealand

1 0

OT Slingshot activations/admin request
by Barry Murphy 23 Oct '06

23 Oct '06

Hi There, First off sorry for the offtopic post, though I'm drinking beer and offering beer to someone that can help me from Slingshot activations / admin. For some odd reason my Italk number fell off the face of slingshot (perhaps it's in fiji or been sold without knowing) since Saturday afternoon. No one till now has been able to help and it's causing issues for people trying to contact me and for me in general. Please reply offlist if you can assist, beer offerings. Cheers Barry -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

1 0

national bank phish
by roberth＠plain.co.nz 18 Oct '06

18 Oct '06

heads up on a recent PHISHing attack I guess others may have users complaining about the PHISH just arriving representing itself as the National Bank while the site collecting is http://www.ffmd.org/bilder/www.nbnz.co.nz/login.html We've found a live chat with the web provider for ffmd.org and mailed abuse@@b-one.net who own the IP space. Any other strategies to close an internationally hosted one like this? -Robert

6 6

Notification of NZRR Database changes
by NZRR Database Notifications 18 Oct '06

18 Oct '06

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:AS23655 descr: advertised to AS9439 by Snap Internet Limited - AS23655 members: 132.181.0.0/16^16-29, 202.124.96.0/19^19-29, 210.5.48.0/21^21-29, 203.97.28.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 203.96.112.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060724 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS23655 descr: advertised to AS9439 by Snap Internet Limited - AS23655 members: 132.181.0.0/16^16-29, 202.124.96.0/19^19-29, 203.86.192.0/20^20-29, 210.5.48.0/21^21-29, 202.49.92.0/22^22-29, 202.50.104.0/22^22-29, 202.50.124.0/22^22-29, 202.27.186.0/23^23-29, 202.36.178.0/23^23-29, 202.36.218.0/23^23-29, 202.36.220.0/23^23-29, 202.37.100.0/23^23-29, 202.37.124.0/23^23-29, 202.49.90.0/23^23-29, 202.49.120.0/23^23-29, 210.55.30.0/23^23-29, 210.55.206.0/23^23-29, 192.156.225.0/24^24-29, 202.36.170.0/24^24-29, 202.49.115.0/24^24-29, 202.49.125.0/24^24-29, 202.49.187.0/24^24-29, 202.50.117.0/24^24-29, 202.50.169.0/24^24-29, 203.96.112.0/24^24-29, 210.54.15.0/24^24-29, 210.55.4.0/24^24-29, 210.55.7.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)snap.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061019 source: NZRR

1 0