Services

Services

Managed DNS services for production continuity.

Web Envy DNS delivers the operational layer behind always-on websites, customer portals, ecommerce, APIs, mail routing, and multi-site infrastructure.

Service portfolio

Everything needed to keep DNS resilient.

Use Web Envy DNS as a managed backup provider, a failover automation layer, or a policy-based routing platform for global application access. Services can be adopted individually or combined into a continuity plan for critical domains.

Managed DNS Backup

Independent authoritative DNS with synchronized records, redundant nodes, and hands-on configuration support.

Failover DNS

Health checks, thresholds, alternate targets, and controlled rollback for production websites and services.

Geo Multi-Site DNS

Route traffic to the closest, fastest, or preferred environment across cloud and private infrastructure.

REST API Management

Automate record changes and integrate DNS operations with deployment, monitoring, and incident workflows.

Failover DNS routing workflow graphic
Failover workflow from DNS request through monitor checks, policy decisions, and backup route activation.
Service workflow

From DNS risk to operational resilience.

The service is designed around the practical work customers need to complete: mirror records, validate endpoints, define recovery targets, route traffic, and keep support context close when incidents happen.

  • Document the current DNS footprint and identify single-provider exposure.
  • Configure backup zones and keep critical record types synchronized.
  • Build failover policies for web, mail, API, and application endpoints.
  • Review routing state before, during, and after maintenance windows.
Use case playbooks

Designed around the scenarios that create real business risk.

Enterprise buyers want to know whether a service fits their incident model. These common playbooks show where Web Envy DNS can sit in the operating environment.

Provider outage

Primary DNS provider becomes unavailable.

Maintain an independent authoritative layer with synchronized records so DNS responses can continue while the primary provider is impaired or under maintenance.

Application outage

Primary origin stops serving production traffic.

Use health checks, failure thresholds, and backup targets to move users toward a healthy endpoint without waiting for manual DNS edits.

Regional routing

Customers should reach the right site by location.

Route users by geography or preferred region to support performance, resilience, active/active environments, or local infrastructure strategy.

Planned maintenance

Traffic needs a clean path during upgrades.

Prepare standby targets and rollback rules before maintenance so customer access remains predictable while teams patch, migrate, or replace infrastructure.

Migration

Domains move between clouds, hosts, or providers.

Control TTL strategy, mirror records, validate endpoint health, and use DNS policy to lower migration risk across important domains.

Operations

DNS changes must fit engineering workflows.

Use API-ready controls and structured tickets to connect DNS work to release processes, support escalations, and incident response.

Implementation deliverables

From setup to escalation, services are designed around real operations.

Each engagement can include the practical artifacts teams need: record review, failover policy design, monitoring configuration, API guidance, and technical support for production incidents.

DNS footprint audit

Review authoritative providers, active zones, critical records, TTL values, domain ownership, and service dependencies.

Continuity design

Define backup DNS behavior, health checks, failover thresholds, standby targets, and rollback posture before changes go live.

Validation and launch

Confirm records resolve correctly, monitors detect the right failures, and routing policy behaves as expected under test conditions.

Escalation workflow

Document contacts, service priority, affected domains, and the ticket path support should follow when production DNS needs attention.

Routing strategy

Match the service to the way your infrastructure actually runs.

Not every domain needs the same DNS posture. Web Envy DNS can support simple backup DNS, standby recovery, global routing, and more advanced multi-site patterns.

Backup authoritative DNSSecondary resilience layer
When to use itYou need provider redundancy for important public zones.
Operational focusZone mirroring, NS planning, TTL review, and change validation.
Active/passive failoverStandby recovery target
When to use itA backup origin or site should receive traffic only when primary health fails.
Operational focusMonitor settings, thresholds, alternate targets, and rollback controls.
Active/active routingMultiple live sites
When to use itUsers can be served by more than one production region or provider.
Operational focusRegional preference, policy clarity, and application consistency.
Geo multi-site DNSLocation-aware access
When to use itCustomer experience improves when users reach the nearest or preferred service location.
Operational focusRegional maps, compliance needs, latency expectations, and recovery routing.
Plans

Pick the coverage level that fits your footprint.

Plans can support everything from straightforward backup DNS to enterprise multi-site routing with stronger support expectations.

PlanBest forIncludes
BusinessSmall teams reducing DNS provider risk5 global node choices, failover support, up to 50 NS records, REST API access, basic continuity guidance
Business PlusGrowing operations with more records and priority needsGlobal node selection, SLA coverage, priority support, up to 150 NS records, implementation guidance
EnterpriseCritical domains and multi-site applicationsWorldcast DNS network, rapid failover protection, load balancing support, comprehensive support, multi-site routing strategy
Scroll to Top