Platform/Networking/DNS

Authoritative DNS on regional anycast.

Fast, resilient name resolution served from in-region anycast — with API management and DNSSEC when you need it.

AnycastAPI-managedDNSSEC

Talk to us All Networking

Capabilities

Names, resolved properly

Enterprise-grade DNS and traffic management for reliability, performance and control at every scale.

Regional anycast

Queries answer from the nearest point of presence in the Gulf.

Answers close to users →

API & console

Zones and records managed programmatically or by hand.

Zones as code →

DNSSEC

Signed zones for domains where integrity matters.

Responses you can trust →

Health-based routing

Failover records that follow your load balancer health checks.

Failover at the resolver →

Geo & weighted routing

Steer users by geography or split traffic by weight for migrations.

Traffic where you want it →

Fast propagation

Changes go live in seconds across all nodes.

No waiting on TTLs →

Zone import & transfer

AXFR import and BIND-compatible export make moves painless.

Arrive without downtime →

Query analytics

Per-zone query volumes and top records, visible.

DNS stops being blind →

Access-scoped changes

Per-zone permissions with a full change log.

Who changed what, answered →

DDoS-resilient by design

Anycast absorbs floods that would take out a unicast resolver.

Built to stay answering →

Resilient by designBuilt to continue, even when hardware fails.

Predictable performanceConsistent I/O for the apps that matter.

Efficient at scaleOne flat fee. Scale without waste.

Backed by humansReal experts. Real support. Every time.

Compare the zones

Public, private, or traffic-managed

The same anycast platform behind each — the difference is who can resolve the names and how clever the answers get.

ProductionEdgeComing soon

ZONE 01Most common

Public Zones

Authoritative, anycast

Authoritative DNS for your public domains served from in-region anycast, with API-managed records and optional DNSSEC.

Best for

Public domainsRegistrar migrationsMail & service records

Where it runs

Dubai AZ1Dubai AZ2RiyadhBahrainMumbaiSingaporeAbu DhabiMilanFrankfurtNairobi

Plans

ZonesAnycast authoritative · API recordsSign in →Zones PlusDNSSEC · change history · role-based accessSign in →CustomAny zone count and query volumeSign in →

ZONE 02

Private Zones

Names inside the estate

Internal resolution scoped to your virtual networks, so service discovery works without exposing internal names to the internet.

Best for

Service discoveryInternal platformsSplit-horizon estates

Where it runs

Dubai AZ1Dubai AZ2RiyadhBahrainMumbaiAbu DhabiFrankfurtNairobi

Plans

Private ZonesVPC-scoped resolution · API recordsSign in →Private Zones PlusSplit-horizon · conditional forwardingSign in →CustomAny forwarding and split-horizon designSign in →

ZONE 03

Traffic Management

Answers that adapt

Health-checked and geo-aware responses that route users to the healthiest or nearest endpoint, and away from a failing one.

Best for

Active-passive failoverMulti-region routingMaintenance switching

Where it runs

Dubai AZ1RiyadhBahrainMumbaiDubai AZ2Nairobi

Plans

TrafficHealth checks · failover recordsSign in →Traffic PlusGeo routing · weighted pools · alertingSign in →CustomAny routing policy and health-check designSign in →

Two ways to run it

Self-managed records, or managed DNS

Both are inside the fee and both are anycast. The difference is who owns the record set.

Self-managedYou hold the records

Your team manages zones and records through the console, API or pipeline, with change history on every edit.

✓API and Terraform-driven records

✓Role-based access per zone

✓Every change attributed and reversible

Best for teams already automating DNS.

Managed DNSWe hold the records

Network Operations owns the zone data, change process and health-check design, with your approval on each change.

✓Reviewed change process

✓Failover policies designed and tested

✓Expiry and delegation monitored

Best when DNS has caused an outage before.

Who decides, who runs it

What each group gets from DNS

Four groups shape a cloud decision. Pick the one you belong to — the platform reads differently from each seat.

“An outage class we no longer own”

Name resolution is accountable and in-region rather than bundled free with whoever sold the domain.

GovernedSovereignPredictable

FAQs

Where is DNS served from?

Regional anycast nodes, so resolution happens close to your users rather than across an ocean.

Do you support DNSSEC?

Yes, on the Plus plans — signing and key rotation are managed for you.

Can we manage records in Terraform?

Yes. Zones and records are fully API-driven with role-based access per zone.

Can DNS fail over automatically?

Yes — Traffic Management adds health-checked records that steer users away from a failing endpoint.

Is query volume charged?

No. Queries sit inside the flat fee; there is no per-million-query meter.

How is the flat fee different from public cloud pricing?

Everything inside the plan you opt for is included — no additional charge for the components that make it up. Public clouds meter each component on consumption, so the bill moves with usage. Here the plan is reserved for you and the figure you agreed is the figure you pay.

How do limits and quotas work?

Quotas are yours to shape — carve capacity per team or project and delegate inside it. Hard ceilings are a conversation, not a wall; the estate re-baselines at thresholds you approve.

Can security services be included in my plan?

Yes. Endpoint security, firewalls and WAF are scoped into the same flat fee when you add them — one figure, no separate security invoice.

Better together