BGP Peering

Peering with F-Root

ISC has deployed numerous F-Root nameserver nodes, using an anycast routing setup.

These nodes are usually deployed at Internet Exchange Points (IXPs), and network operators are welcome to peer with us at IXPs to improve their access to the Root Server System.

Peering Policy

F-Root operates an open peering policy, however we do not peer with networks that are not present in PeeringDB, or whose records are not maintained.

F-Root reserves the right to discontinue peering with networks whose listed contacts do not respond appropriately to reports of network abuse, or those that do not follow the technical guidelines for propagation of the F-Root IP networks, as described below.

Contact Information
Peering requests
NOC e-mail (preferred over phone calls)
NOC phone +1 650 423 1310 (emergencies only)
Peering Locations and Details

We keep our PeeringDB records current with our up-to-date locations and peering details.

To see the list of F-Root locations, you can find ISC’s organization record here in PeeringDB (or search for “Internet Systems Consortium”).

On the right hand side you’ll see a long list of “Networks”, including all F-Root locations.

Finding common IXPs

Wherever available, F-root nodes peer with the routeservers at each IXP at which we are present. If a network operator feels the need to set up direct BGP sessions, we are happy to peer directly.

In order to find IXPs at which you cuould peer with F-Root, be aware that F-Root uses a different peering ASN at each location. As such the well known peerfinder tool will not find the intersections.

Instead, we have written and published a Python tool named pdb-intersect that you can install and run. It essentially starts at the organization level and drills down from there.

Once installed, it’s run simply by:

pdb-intersect <your-asn> 3557

It will output ASN and IP info for each common interconnection point.

Routing Policy

Networks that filter based on Routing Registry objects should use AS-FROOT (RaDB) as the filter object. (The local peering ASN usually has an AS<asn>:AS-SET record, but since it’s not exporting anything, that’s of no use.)

ISC operates a few Global Nodes for the F-Root service at core locations. Global nodes advertise and 2001:500:2e::/47 into the default-free zone via Tier 1 transit operators. We do not exchange these prefixes with peers.

The majority of F-Root nodes are Local Nodes that are intended to serve the local community. Local nodes advertise the more specific prefixes and 2001:500:2f::/48 to peers, and set the well-known community NO_EXPORT.

All peers are required to ensure that they do not announce our prefixes into the default-free zone. If this requires the use of alternative BGP communities this can be arranged on request to our NOC.