FYI - the Auckland node of F.ROOT-SERVERS.NET has been offline for the past couple of years due to HW failure, access issues @SkyTower, changes with our hosts (contacts and access to said data center). I am happy to report that the node is finally back online and advertising F's prefixes to the APE fabric as I type... So come and send your DNS root server queries locally instead of sending them off-shore. We are AS23710 @APE, so if you don't peer with us already, pop us a note at peering(a)isc.org. Yes, Telecom NZ, I am looking at you. Yes, you... (a guy can dream, even if it is hopeless) ;) There are many folks to thank as ISC could not do it alone including: - NZRS (Jay, Sebastian and Dave) for sponsoring the new server gear. - APNIC for sponsoring the new routers. (sorry to see the old Juniper kit go though) - Sebastian and Mike Jager for dealing with my numerous remote hands requests from the other side of the world. - The Kiwi Internet Mafia (Joe Abley, AJ, Jonny) for their support and access to their contacts to keep things moving. - Vodafone NZ and FX Networks for (now redundant) transit over IPv4 and IPv6. - Our peers at APE that have put up with us for being down so long... :) O.k., commercial over; back to serving packets again. Best Wishes - Peter -- [ plosher(a)isc.org | Senior Operations Architect | ISC | PGP E8048D08 ]
Are you advertising the F-Root (containing 192.5.5.241) to the route-servers ? (I can't see it), or direct peering only ? thanks -----Original Message----- From: Peter Losher Sent: Tuesday, December 10, 2013 2:55 PM To: nznog Subject: [nznog] ISC/F-Root has returned to APE... FYI - the Auckland node of F.ROOT-SERVERS.NET has been offline for the past couple of years due to HW failure, access issues @SkyTower, changes with our hosts (contacts and access to said data center). I am happy to report that the node is finally back online and advertising F's prefixes to the APE fabric as I type... So come and send your DNS root server queries locally instead of sending them off-shore. We are AS23710 @APE, so if you don't peer with us already, pop us a note at peering(a)isc.org. Yes, Telecom NZ, I am looking at you. Yes, you... (a guy can dream, even if it is hopeless) ;) There are many folks to thank as ISC could not do it alone including: - NZRS (Jay, Sebastian and Dave) for sponsoring the new server gear. - APNIC for sponsoring the new routers. (sorry to see the old Juniper kit go though) - Sebastian and Mike Jager for dealing with my numerous remote hands requests from the other side of the world. - The Kiwi Internet Mafia (Joe Abley, AJ, Jonny) for their support and access to their contacts to keep things moving. - Vodafone NZ and FX Networks for (now redundant) transit over IPv4 and IPv6. - Our peers at APE that have put up with us for being down so long... :) O.k., commercial over; back to serving packets again. Best Wishes - Peter -- [ plosher(a)isc.org | Senior Operations Architect | ISC | PGP E8048D08 ] _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
Same here, appears APE RS¹s aren¹t reflecting them..
rs1.ape.nzix.net-bgp> show ip bgp 192.5.5.0
BGP routing table entry for 192.5.5.0/24
Paths: (1 available, best #1, table Default-IP-Routing-Table, not
advertised to EBGP peer)
Not advertised to any peer
23710 3557, (aggregated by 23710 202.41.140.16) 192.203.154.98 from
192.203.154.98 (202.41.140.16)
Origin IGP, metric 10, localpref 100, valid, external, atomic-aggregate,
best
Community: 3557:10 no-export
Last update: Thu May 20 10:03:53 1971
-Scott
On 10/12/13 15:13, "Tony Wicks"
Are you advertising the F-Root (containing 192.5.5.241) to the route-servers ? (I can't see it), or direct peering only ?
________________________________ The content of this message and any attachments may be privileged, confidential or sensitive. Any unauthorised used is prohibited. Views expressed in this message are those of the individual sender, except where stated otherwise with appropriate authority. All pricing provided is valid at the time of writing only and due to factors such as the exchange rate, may change without notice. Sales are made subject to our Terms & Conditions, available on our website or on request. ________________________________
On 10/12/13 3:13 pm, "Tony Wicks"
Are you advertising the F-Root (containing 192.5.5.241) to the route-servers ? (I can't see it), or direct peering only ?
Thanks
It is being announce @ APE to the RS¹s . rs1.ape.nzix.net-bgp> show ip bgp neighbors 192.203.154.98 routes BGP table version is 0, local router ID is 192.203.154.1 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale, R Removed Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *> 192.5.5.0 192.203.154.98 10 0 23710 3557 I But..
rs1.ape.nzix.net-bgp> show ip bgp 192.5.5.0 BGP routing table entry for 192.5.5.0/24 Paths: (1 available, best #1, table Default-IP-Routing-Table, not advertised to EBGP peer) Not advertised to any peer 23710 3557, (aggregated by 23710 202.41.140.16) 192.203.154.98 from 192.203.154.98 (202.41.140.16) Origin IGP, metric 10, localpref 100, valid, external, atomic-aggregate, best Community: 3557:10 no-export Last update: Thu May 20 10:03:53 1971
Maybe due to the no-export
On 2013-12-09, at 21:30, Craig Whitmore
Maybe due to the no-export
Back in the day, we advertised F's service prefixes to route servers with a locally-significant community string attribute which would trigger a special export policy from the route servers (they would stamp on no-export for us). Presumably some config could be added to the APE route servers to do that, if there's not already something there that would fit the bill? Joe
On 11 Dec 2013, at 14:06, Joe Abley wrote:
Maybe due to the no-export
Back in the day, we advertised F's service prefixes to route servers with a locally-significant community string attribute which would trigger a special export policy from the route servers (they would stamp on no-export for us).
Presumably some config could be added to the APE route servers to do that, if there's not already something there that would fit the bill?
We are talking to the Citylink folks about that now (anything that was there may have been removed when the node was offline), but as we are coming up against their end of year config freeze at the end of this week, this fix may have to wait until after Jan 1st (2014). Best Wishes - Peter -- [ plosher(a)isc.org | Senior Operations Architect | ISC | PGP E8048D08 ]
participants (5)
-
Craig Whitmore -
Joe Abley -
Peter Losher -
Scott Pettit -
Tony Wicks