Hi, NZNOG folks.
[ Apologies to those of you who have seen this post in other fora. ]
Bogon prefixes aren't the only bits of garbage one will find in the
Internet routing table. There are also bogus (unallocated, reserved,
and private) ASNs to be found therein. Please take a moment to check
my Bogus ASN Report. I have recently enhanced it a bit to include
the full path and better tracking. The report is updated hourly, and
you will find it here:
http://www.cymru.com/BGP/asnbogusrep.html
Comments and feedback are always welcome!
Thanks!
Rob.
--
Rob Thomas
http://www.cymru.com
ASSERT(coffee != empty);
-
To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz
where the body of your message reads:
unsubscribe nznog
No, it is not the reverse of newzealand.biz. Neither arbitrator ruled in
favour of the New Zealand case. With newzealand.biz the reallocation
occured by default (the respondent did not put up an argument). If you read
the arbitrator's comments, it is clear that he did not support the NZ case
at all.
The newzealand.com decision is quite consistent with the other, if just a
little more outspoken.
-----Original Message-----
From: Sue Leader [mailto:exe.dir(a)internetnz.net.nz]
Sent: Friday, 20 December 2002 11:21
To: nznog(a)list.waikato.ac.nz
Subject: Re: New Zealand found guilty of Reverse Domain Name Hijacking
Hi
Good grief - the reverse of the rather bizarre newzealand.biz ruling! It's
really nice to have a *Uniform* Dispute Resolution Policy provided by
ICANN, ne?
At 14:21 19/12/2002, you wrote:
>http://arbiter.wipo.int/domains/decisions/html/2002/d2002-0754.html
>
>Thank you for playing. Feeling stupid yet?
>
Whoever has to tell Her Majesty may well be! ;->
-
To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz
where the body of your message reads:
unsubscribe nznog
http://www.govt.nz - connecting you to New Zealand central & local government services
Any opinions expressed in this message are not necessarily those of the Ministry of Economic Development. This message and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivery to the intended recipient, be advised that you have received this message in error and that any use is strictly prohibited. Please contact the sender and delete the message and any attachment from your computer.
-
To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz
where the body of your message reads:
unsubscribe nznog
are coming out of 203.118.144.0/24 this afternoon. Unfortunately, IHUG
may have some capacity issues out of Wellington (at least, we're
currently spraying 80Mb/s into WIX, and there's only 5Mb going out
IHUG's port :-(.
Those on WIX peering with the route servers, if you could listen to
203.118.144.0/24 coming out of ASN9439, your users should get a more
direct path to the cameras.
www.wellingtonnz.com has links to the cameras, if you're interested.
-
To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz
where the body of your message reads:
unsubscribe nznog
Hi, NZNOG folks.
[ Apologies to those of you who have received this post in other fora. ]
At the behest of several requestors, we have created a new, one-way list
solely for the announcement of new IP prefix allocations to the sundry
RIRs. The posts will include the allocated prefix, allocation date, the
RIR(s) involved, and pointers to the documents we (Steve Gill, Barry
Greene, and Rob Thomas) update when such allocations are made. These
announcements will be made as we detect such allocations.
The list is moderated by Steve Gill, Barry Greene, Jared Mauch, and
Rob Thomas. It is open to anyone who wishes to subscribe. Aliases are
welcome to subscribe.
To subscribe to the list, please visit the following URL:
http://puck.nether.net/mailman/listinfo/bogon-announce
A mini-FAQ:
1. Why form yet another list? I already receive enough e-mail.
We share your pain. :) Such a list will help some folks
to automagically process, filter, or file such
announcements.
2. How do you know about new allocations from IANA to the RIRs?
We have a cronjob that diffs the list on a daily basis.
3. How soon after the allocation is made will you announce it?
In some cases our release will be coordinated with the RIR.
In other cases it will be made as soon as we detect it.
In all cases it will be made as quickly as possible.
Please note that all of the monitoring and templates will
be updated as soon as the allocation is detected.
4. What sort of message volume can I expect on the list?
Messages will only be posted to the list when new
allocations are made.
5. Does this mean you won't send these updates to several other
lists?
No. We will continue to send e-mail to a variety of lists
when allocations are made.
6. Sheesh, where do you find the time for such things? Have
you no social life?
Nope, none at all. :)
Thanks!
Steve, Barry, Jared, Rob,
your bogon-announce list administrators.
-
To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz
where the body of your message reads:
unsubscribe nznog
Has anyone else received a spam recently offering new domain names with
"illegal" characters in the domain name ?
apparently under the .bz TLD, try a host lookup on http://www.b&w.bz
--
Steve
Systems Admin, ICONZ
-
To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz
where the body of your message reads:
unsubscribe nznog
[Apologies for duplicates. I'm posting this to all the ISP Operations
List.]
Hello Everyone,
I've pushed out new versions of the ingress prefix templates. Had a
really good peer review of the list by Steve Gill. He is working on the
Junos flavored template. This review resulted in some nice tweaks and
additions to the list. You can down load the templates from:
ftp://ftp-eng.cisco.com/cons/isp/security/Ingress-Prefix-Filter-Template
s/
Here are the changes with version 1.11
+ Changes J-Root:
J.ROOT-SERVERS.NET. 192.58.128.0/24
+ Added 82.0.0.0/8 for the new RIPE-NCC allocation.
+ Added a deny for 240.0.0.0/4 le 32 and changed 224.0.0.0/3 le 32 to
224.0.0.0/4 le 32.
+ Matching and adding more DNS G-TLD servers from:
http://www.qorbit.net/documents/golden-networks
We need help refining the more specifics for the G-TLDs (see below). I
see /16s, /18s, and other big prefixes in the list. These big prefixes
worry me. It could mean that root servers administrator are not thinking
through the impact of a more specific prefix hijack and stacking several
critical servers on one segment. So, if people have the time and the
knowledge of the more specifics, please let me know.
Thanks,
Barry
aero | dns7.denic.de. | 194.246.96.0/24
aero | merapi.switch.ch. | 130.59.0.0/16
aero | ns3.knipp.de. | 194.64.105.0/24
aero | tld1.nominum.com. | 198.133.199.0/24
aero | tld2.nominum.com. | 192.100.59.0/24
biz | a.gtld.biz. | 209.173.53.0/24
biz | b.gtld.biz. | 209.173.57.0/24
biz | c.gtld.biz. | 209.173.60.0/24
biz | d.gtld.biz. | 213.86.0.0/16
biz | e.gtld.biz. | 209.173.58.0/24
biz | f.gtld.biz. | 209.173.58.0/24
coop | ns1.nic.coop. | 198.133.199.0/24
coop | ns2.nic.coop. | 192.100.59.0/24
gov edu | a3.nstld.com. | 192.5.6.0/24
gov edu | b3.nstld.com. | 192.33.14.0/24
gov edu | c3.nstld.com. | 192.26.92.0/24
gov edu | d3.nstld.com. | 192.31.80.0/24
gov edu | e3.nstld.com. | 192.12.94.0/24
gov edu | f3.nstld.com. | 192.35.51.0/24
gov edu | g3.nstld.com. | 192.42.93.0/24
gov edu | l3.nstld.com. | 192.41.162.0/24
gov edu | m3.nstld.com. | 192.55.83.0/24
info | tld1.ultradns.net. | 204.74.112.0/24
info | tld2.ultradns.net. | 204.74.113.0/24
int | ns.isi.edu. | 128.9.0.0/16
int | ns.uu.net. | 137.39.0.0/16
int | ns0.ja.net. | 128.86.0.0/16
int | ns0.ja.net. | 193.60.0.0/14
int | ns1.cs.ucl.ac.uk. | 128.16.0.0/16
int museum | ns.icann.org. | 192.0.34.0/24
mil | con1.nipr.mil. | 199.252.128.0/18
mil | con2.nipr.mil. | 199.252.128.0/18
mil | eur1.nipr.mil. | 199.252.154.0/24
mil | eur2.nipr.mil. | 199.252.128.0/18
mil | pac1.nipr.mil. | 199.252.180.0/24
mil | pac2.nipr.mil. | 199.252.155.0/24
museum | dns1.getty.edu. | 153.10.0.0/16
museum | nic.icom.org. | 195.7.64.0/19
museum | nic.museum. | 130.242.0.0/15
museum | ns-ext.vix.com. | 204.152.184.0/21
name | a10.nstld.com. | 192.5.6.0/24
name | f10.nstld.com. | 192.35.51.0/24
name | g10.nstld.com. | 192.42.93.0/24
name | l10.nstld.com. | 192.41.162.0/24
name | ns1.nic.name. | 193.109.220.0/24
name | ns3.nic.name. | 202.71.192.0/18
pro | a.iana-servers.net. | 192.0.34.0/24
pro | b.iana-servers.net. | 193.0.0.0/21
-
To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz
where the body of your message reads:
unsubscribe nznog
Hi Folks.
First up, a big thank you to Miwa, Elly and Nurani for the excellent
presentation this morning in Wellington - as an APNIC newbie, I found it
really helpful. Likewise two thumbs up to Bill Woodcock for the thought
provoking discussion in the afternoon on the mechanics and politics of
peering - those of you who haven't had a chance to listen to Bill, I
suggest you buttonhole him when he's in Auckland next week, if you feed
him beer he's sure to regale you with his doughnut theory of peering
failure :-). Lastly, an marvelous job of overcatering by the folks at
Datacom - ta muchly! Best $100 seminar I've been to in a long, long
time.
Keeping this vaguely operational, Bill has started the INOC-DBA system
http://www.pch.net/inoc-dba/
Simplistically, it means that you crank up a Cisco 7960 phone, configure
it to use Bill's server, and you get dial-an-ASN - ring an ASN, and with
any luck it'll ring on the desk of somebody who might have something
sensible to say about the ASN you just rang:
--
"One of the benefits of this network which is most frequently cited by
its users is the fact that callers are pre-screened for clue. Calls
cannot enter the network from the outside PSTN. We would like to
maintain that high ratio of signal to noise in order to keep the utility
of the network as high as possible for its users."
--
It seems to me to be a great idea, and not just because Bill has slapped
a 7960 down on my desk to try it out :-). Bill is installing the phone
at Citylink tomorrow (Tuesday) morning - anybody else interested in
testing this while Bill is in town, grab a phone and send
ASN/IP/Contact/MAC details through ASAP.
Cheers
Si
On Wed, Oct 02, 2002 at 03:22:03PM +1000, Champika Wijayatunga said:
>
> Dear APNIC Member,
>
> APNIC is pleased to announce that we are planning to have a training
> course in New Zealand on 10 December 2002 on "Effective IP
> Address Management: Asia-Pacific Policies and Procedures".
>
> The APNIC training courses are currently offered on a sponsored basis to
> APNIC members and it is subsidised for them. But non-members are also
> welcome and however, they are usually charged a slightly higher fee.
>
> Basically these charges are to recover our costs on a non-profit basis.
> Previously this training course fee has ranged from 'No charge' to
> USD75.00 (charged in local currency) depending on the location & the
> sponsorships. Training materials, Lunch and refreshments will be provided.
>
> We would like to get the input from APNIC members regarding this training.
> We greatly appreciate if you could answer the following few questions and
> send it to us. Please note that this is NOT a registration form. This
> information is considered for our evaluation purposes only.
>
> * Your name & e-mail id:
>
> * Your company / APNIC Account name:
>
> * Are you interested in attending this training? Yes/No
>
> * How many participants will attend from your organisation?
>
> * Would you like to assist us in sponsoring this training? Yes/No
> If so in which way? (ex: providing a training venue, lunch &
> refreshments for the participants etc.)
> If you are interested in sponsorships please let us know, so that we
> can update you about the sponsorship benefits.
>
> * Any suggestion for a location(city)/hotel?
>
> * Are you aware of any Internet related conference happening in New
> Zealand during December 2002 ?
>
> * Other comments
>
> Thank you for your cooperation !
>
> We look forward to hearing from you soon.
>
> Warmest Regards,
> Champika.
> _____________________________________________________________________
> Champika Wijayatunga, Training Manager <champika(a)apnic.net>
> Asia Pacific Network Information Centre phone: +61 7 3858 3100
> http://www.apnic.net fax: +61 7 3858 3199
> _____________________________________________________________________
>
>
>
>
>
>
>
>
-
To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz
where the body of your message reads:
unsubscribe nznog
> However, competitors like 2day.com are in effect disadvantaged by this,
> because they may want to offer their services as well, but they're not
> in the same position as Domainz, and don't have existing relationships
> with .nz name holders.
But surely that is at the discretion of the .nz Provider - and in this
instance (and there are reasons), 2Day.com have not signed the accreditation
agreement, so the customers are actually that of Domainz.
There are a significant number of domain names in the Registry that we
_know_ are customers of Peter Mott, although they have registered with
Domainz for their domain names. We fully expect Peter to contact his
customers if, no when Peter becomes a Registrar and try to move them from
us. This is fair competition.
I'm sure there will be many other Providers are in the same boat and will
try and entice their customers (and indeed everyone else's) away from
Domainz. Obviously, Domainz must try and introduce facilities to keep our
customers but the new marketplace is here. People now have choice.
The email distributed this morning was to name holders of domain names that
are directly billed by Domainz. How can this be spam ?
Tim
-----Original Message-----
From: Juha Saarinen [mailto:juha(a)saarinen.org]
Sent: Sunday, 8 December 2002 11:48 a.m.
To: Matt Brown
Cc: nznog(a)list.waikato.ac.nz
Subject: Re: Domainz spams entire .nz whois database
On Mon, 9 Dec 2002, Matt Brown wrote:
> Interesting to note that the individual who started this thread is now
> a competitor to Domainz.
I think it's a tricky one: it's fair to say that Domainz has an existing
relationship with .nz name holders and thus, as you say, can communicate
with its customers.
However, competitors like 2day.com are in effect disadvantaged by this,
because they may want to offer their services as well, but they're not
in the same position as Domainz, and don't have existing relationships
with .nz name holders. They'd be spamming if they were to try the same
thing, basically.
--
Juha Saarinen
-
To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz
where the body of your message reads:
unsubscribe nznog
DISCLAIMER: The content of this email is confidential and may contain
legally privileged information intended only for the individual or entity
named above. Access to this message by anyone else is unauthorised. If you
are not the intended recipient, please be advised that the use, distribution
and publication of the above information is prohibited. If you have received
this email in error, please contact Domainz by returning the email and
destroying the original. Thank you.
-
To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz
where the body of your message reads:
unsubscribe nznog
In message <000101c29e78$9888ee10$0800a8c0(a)roadshow.org>, "Steve Winter" writes:
>Was I asleep the day that someone mentioned that whois.domainz.net.nz no
>longer existed, or is it simply a temporary situation this afternoon
>that prevents me from getting anything useful from there...??...if it's
>gone, can anyone point me in the direction of an alternative for the .nz
>domain space..
whois.srs.net.nz
That talks directly to the SRS database using the SRS Registrar/Registry
protocol.
The output format is similar, but different from the Domainz one; the
format is documented at:
http://dnc.org.nz/content/srs-whois-spec.html
(A quick test suggests that the fix for the bug that Joe Abley mentioned
to me (regarding timezone formatting) has gone live.)
Last I heard whois.domainz.net.nz was eventually going to be pointed at
the whois.srs.net.nz server (because "whois.domainz.net.nz" is hardcoded
as a name into some whois clients), but AFAIK that hasn't been done yet.
It appears that whois.domainz.net.nz is just down at present, and
presumably will be back up again RSN.
Ewen
-
To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz
where the body of your message reads:
unsubscribe nznog