Nexus GSLB supports RFC 5936 AXFR zone transfers, allowing you to configure secondary (slave) nameservers that pull a copy of the zone. Secondary servers provide:
Nexus GSLB supports two encrypted DNS transports:
When Nexus GSLB is the authoritative nameserver for a zone, standard ACME challenge methods break down:
Nexus GSLB includes a built-in HTTP redirect service that lets you redirect traffic for any hostname in your zone to a target URL, with optional path and query string preservation. This is the same type of feature NS1 calls “Redirect Manager” — rules…
A routing schedule redirects a service to a different pool during a UTC time-of-day window — "between 08:00–18:00 UTC weekdays, route to pool A; otherwise fall back to the service's default pool." It's evaluated fresh on every DNS query against the ser...
Real-User Measurement (RUM) routing answers DNS queries with the pool member that is fastest for the actual user asking — measured from real visitors' browsers, not from your cluster's health probes. It captures last-mile, ISP peering, and CDN effects ...
Nobody else in the GSLB space routes on carbon. ESG procurement questionnaires increasingly ask "does your infrastructure account for carbon intensity?" — with Nexus, the honest answer is yes, and it's a one-line filter-chain step, not a research proje...
This guide walks through configuring Nexus GSLB to inject and withdraw BGP routes based on health check results. It covers three common deployment scenarios, peer configuration examples for FRR (Linux) and Cisco IOS, and troubleshooting steps.
Nexus can continuously export each service's effective zone to a big-cloud DNS provider and keep it in sync. You run Nexus and a provider secondary at the same time. This gives you two things: