Home Domain Names Internet Resolution Technical Requirements (IP Network)

Internet Resolution

Regional Internet Resolution Service (RIRS)

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

Technical Requirements

(IP Network)

In order to connect a RIRS node to an IP network, 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 for production traffic, and one for system management functions, both with full IPv4 transit capabilities). The partner must provide a /30 (or /31) for the point-to-point (production) interface addressing. An eBGP adjacency must be formed between Verisign’s RIRS server and the adjacent partner router across the production interface. Via eBGP, Verisign will advertise a subset of the prefixes contained within the AS-GTLD IRR object, as well as the /28 noted below. The partner router will advertise a single default route toward Verisign’s RIRS server via eBGP. The partner must provide a /28 for management services, which Verisign will advertise via the eBGP session mentioned above. The partner must provide a /29 for management interface addressing. Verisign will configure a static default route toward the partner’s router.	The partner must provide two discrete connections (one for production traffic, and one for system management functions, both with full IPv6 transit capabilities). The partner must provide a /126 for the point-to-point (production) interface addressing. An eBGP adjacency must be formed between Verisign’s RIRS server and the adjacent partner router across the production interface. Via eBGP, Verisign will advertise a subset of the prefixes contained within the AS-GTLD IRR object, as well as the /64 noted below. The partner router will advertise a single default route toward Verisign’s RIRS server via eBGP. The partner must provide a /64 for management services, which Verisign will advertise via the eBGP session mentioned above. The partner must provide a /64 for management interface addressing. Verisign will configure a static default route toward the partner’s router.

IPV4

IPV6

The partner must provide two discrete connections (one for production traffic, and one for system management functions, both with full IPv4 transit capabilities).
The partner must provide a /30 (or /31) for the point-to-point (production) interface addressing.
An eBGP adjacency must be formed between Verisign’s RIRS server and the adjacent partner router across the production interface.
Via eBGP, Verisign will advertise a subset of the prefixes contained within the AS-GTLD IRR object, as well as the /28 noted below.
The partner router will advertise a single default route toward Verisign’s RIRS server via eBGP.
The partner must provide a /28 for management services, which Verisign will advertise via the eBGP session mentioned above.
The partner must provide a /29 for management interface addressing. Verisign will configure a static default route toward the partner’s router.

The partner must provide two discrete connections (one for production traffic, and one for system management functions, both with full IPv6 transit capabilities).
The partner must provide a /126 for the point-to-point (production) interface addressing.
An eBGP adjacency must be formed between Verisign’s RIRS server and the adjacent partner router across the production interface.
Via eBGP, Verisign will advertise a subset of the prefixes contained within the AS-GTLD IRR object, as well as the /64 noted below.
The partner router will advertise a single default route toward Verisign’s RIRS server via eBGP.
The partner must provide a /64 for management services, which Verisign will advertise via the eBGP session mentioned above.
The partner must provide a /64 for management interface addressing. Verisign will configure a static default route toward the partner’s router.

Configuration Requirements:

Verisign will run BGP with the hosting network across the production interface.

Verisign will expect to receive a single default route via BGP.

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