- DigiCert product docs
- DigiCert DNS
- Route DNS traffic
- Regional views
Regional views
Regional views let you configure different DNS responses for different geographic regions. Use a Global default configuration for shared responses and regional records where a different response is required.
What regional views are
A regional view provides a region-specific version of a zone’s records. Regional views support multiple record types. This article uses A records as an example: the same record name can use one IPv4 address in Global (Default) and another in North America - West.
Regional views let you customize individual records without creating a separate zone for each region. Records without a regional override use the Global default configuration.
DMARC TXT records can have regional overrides when Valimail Monitor is enabled. Each override must retain the required Valimail reporting address. Existing regional exclusions are preserved; a region with no applicable DMARC TXT record does not report to Valimail. See Valimail Monitor for details.
Explore regional views on the Records page
To view regional records, go to DNS > Zones, select a zone from Primary zones, and open the Records tab.
When regional views are enabled, region selectors appear above the records. Select Global (Default) or a specific region to review its records.
The page includes the following information and controls:
Item | Description |
|---|---|
Regions | Selects the regional view displayed on the page |
Regional view | Identifies whether a record belongs to Global (Default) or a specific region |
Override record | Creates a region-specific version of a Global default record |
Hide Global (Default) | Hides inherited Global records so you can focus on records configured for the selected region |
Policy | Displays the record’s routing policy, including its failover indicator when configured |
Record actions | Provides actions such as Edit, Override, Disable, Enable, or Delete, depending on the record |
Regional records can be reviewed in Grouped view or Table view. Selecting Hide Global (Default) changes the displayed list; it does not disable the Global records.
The Primary zones page also includes a Regional views column showing whether the feature is enabled for each zone.
Supported regional views and account limits
The following regional views are available:
Regional view | Label on the Records page |
|---|---|
Global (Default) | Global (Default) |
North America - West | NA West |
North America - East | NA East |
South America | South America |
Europe | Europe |
Africa | Africa |
Asia-Pacific | Asia-Pacific |
Oceania | Oceania |
Your plan limits the regional views you can add. When the limit is reached, the Upgrade plan message explains that an upgrade is required to add more.
Enable regional views
You can enable regional views when creating a primary zone or from an existing zone’s settings.
When creating a zone, select Enable regional views under Advanced configuration, then complete zone creation. For the full workflow, see Manage DNS zones.
To enable regional views for an existing zone:
Go to DNS > Zones and select a zone from Primary zones.
Open the Settings tab.
Turn on Enable regional views.
In the confirmation dialog, select Enable.
Open Records to configure the Global default and regional records.
Override an existing Global record
Use an override to add a regional version of an existing Global record that supports regional views.
Open the zone’s Records tab.
Select the target region, such as NA West.
Locate the inherited Global record.
Select its Override record icon or choose Override from its actions menu.
Review the record name and selected region.
Update the record’s values and available policy settings as required.
Select Override.
The regional version appears in the selected view, while the global record remains available in Global (Default).
You can also create an override by adding a record with the same name and record type in the target region.
To update a regional record later, choose Edit from its actions menu, make the required changes, and select Update.
Disable records or regional views
You can disable an individual record in a selected region or disable regional views for the entire zone.
To disable a record in a region:
Open the zone’s Records tab.
Select the region.
Open the record’s actions menu and select Disable.
Verify the record name and region in the confirmation dialog.
Select Disable.
The record remains visible with a disabled indicator. To enable it again, select Enable from its actions menu.
To return no record data in a particular region for a record that exists in the default view, disable the record in that region. Queries matching that regional view receive a NXDOMAIN response, indicating that no record data is available for the requested type.
To disable regional views for the entire zone:
Open the zone’s Settings tab.
Turn off Enable regional views.
Review the deletion warning.
Select Disable to confirm.
Notice
Disabling regional views permanently deletes all records in non-default regions. Review those records before confirming. Disabling an individual record leaves it visible in its regional view.
Global defaults and regional overrides
Global (Default) provides the shared record configuration. A regional override supplies a different configuration for the same record in a specific region.
For example, you could configure:
Record | Regional view | IPv4 address |
|---|---|---|
| Global (Default) |
|
| North America - West |
|
The regional version supplies the response for North America - West. Regions without their own override use the Global default record.
When you select a region on the Records page, inherited records retain Global (Default) in the Regional view column. After you create an override, the regional version appears with the selected region’s name.
An override applies to the selected region. It does not replace the Global record or configure overrides in other regions.
When Valimail Monitor is enabled, you can configure regional DMARC TXT overrides with different policies while retaining the required Valimail reporting address. Each region can have only one applicable _dmarc record type: TXT, NS, or CNAME. A regional NS or CNAME delegation to another provider requires the global _dmarc record to be excluded from that region. A delegation pointing to Valimail prevents enablement, even in an excluded region. See Valimail Monitor for validation rules and Nameserver sets for managing the zone’s authoritative nameservers.
Regional views and simple failover
Regional views determine which record configuration applies to a region. If that configuration uses simple failover, the failover policy selects a destination from the addresses configured for that record.
For example, a Global A record and its North America - West override can have different destination addresses. If the regional override uses simple failover, its configured priorities and health checks determine which of its destinations serves the response.
The Regional view field identifies the record’s DNS response region. The Region field under Monitoring configuration controls health-check monitoring and is a separate setting.
For configuration instructions, destination selection, monitoring protocols, and limits, see Simple failover.
Add a record to a regional view
You can add supported record types to regional views. The following procedure uses an A record as an example and shows how to assign IPv4 addresses to a region. For other record types, complete the corresponding record fields.
Open the primary zone’s Records tab.
Select the region you want to configure.
Select Add record.
Select A (Address - IPv4) as the record type.
Enter the Name and TTL.
Confirm the intended region in Regional view.
With Policy set to None (Default), enter the destination IPv4 address. Select Add another to include additional addresses.
If required, configure Simple failover using the instructions in Simple failover.
Select Save and close, or Save and add another to continue adding records.
Review the saved record’s Regional view column to confirm that it belongs to the intended region. For A record fields, see A records.