Home Domain Names Internet Resolution Technical Requirements (IXP)

Internet Resolution

Regional Internet Resolution Service (RIRS)

Connect Verisign’s mission-critical Domain Name System (DNS) services directly to your internet infrastructure

Technical Requirements

(Internet Exchange Point)

In order to connect a RIRS node to an Internet Exchange Point (IXP), the following requirements must be met:

Physical Requirements:

(1) rack unit of space

(2) 110-240VAC power feeds

(1) 250W of power

(1) 1G (fiber-optic or copper) or 10G (fiber-optic-only) connection for production DNS traffic

(1) 1G (fiber-optic or copper) or 10G (fiber-optic-only) connection for management

Connectivity Requirements:

IPV4	IPV6
The partner must provide two discrete connections (one to the IXP peering LAN for production traffic, and one with full IP transit capabilities for management functions). The partner must provide an IPv4 address on the primary IXP peering LAN. The partner must provide a /29 for management interface addressing. Verisign will configure a static default route toward the partner router over the management interface. Verisign will advertise a subset of prefixes contained within the AS-GTLD IRR object to any peers established over the IX.	The partner must provide two discrete connections (one to the IXP peering LAN for production traffic, and one with full IP transit capabilities for management functions). The partner must provide an IPv6 address on the primary IXP peering LAN. The partner must provide a /64 for management interface addressing. Verisign will configure a static default route toward the partner router over the management interface. Verisign will advertise a subset of prefixes contained within the AS-GTLD IRR object to any peers established over the IX.

IPV4

IPV6

The partner must provide two discrete connections (one to the IXP peering LAN for production traffic, and one with full IP transit capabilities for management functions).
The partner must provide an IPv4 address on the primary IXP peering LAN.
The partner must provide a /29 for management interface addressing.
Verisign will configure a static default route toward the partner router over the management interface.
Verisign will advertise a subset of prefixes contained within the AS-GTLD IRR object to any peers established over the IX.

The partner must provide two discrete connections (one to the IXP peering LAN for production traffic, and one with full IP transit capabilities for management functions).
The partner must provide an IPv6 address on the primary IXP peering LAN.
The partner must provide a /64 for management interface addressing.
Verisign will configure a static default route toward the partner router over the management interface.
Verisign will advertise a subset of prefixes contained within the AS-GTLD IRR object to any peers established over the IX.

Configuration Requirements:

Verisign will peer openly with IXP participants via the production interface.

The hosting IXP must provide full IPv4 or IPv6 (desired but not required) transit via the management interface. The hosting network will not be expected to run BGP over this interface.

Verisign will configure a static default route toward the hosting network over the management interface. This will be used for system management operations only. No production DNS traffic will transit this interface.