- DigiCert product docs
- DigiCert DNS
- Shared DNS settings
- Inbound IP sets
Inbound IP sets
Inbound IP sets define the primary nameservers DigiCert® DNS uses for inbound zone transfers and the sources permitted to send zone change notifications. Apply an inbound IP set to a secondary zone to specify where it receives DNS updates.
What an inbound IP set is
An inbound IP set is a named, reusable configuration that contains the IP addresses of primary nameservers and permitted notification sources.
When DigiCert® DNS hosts a secondary zone, it synchronizes the zone’s DNS records from primary nameservers. The inbound IP set identifies those servers and specifies which sources can notify DigiCert® DNS when the zone changes.
You can apply the same inbound IP set to multiple secondary zones that use the same primary DNS infrastructure. Select a set when creating a secondary zone, or change the assigned set from an existing secondary zone’s Settings tab.
Explore the Inbound IP sets page
To view inbound IP sets in your account, go to Configuration > Product settings and select the Inbound IP sets tab.
The page displays the following information:
Column | Description |
|---|---|
Name | The name of the inbound IP set |
Transfer from | The IP addresses of the primary nameservers used for inbound zone transfers |
Receive notifications from | The IP addresses or network ranges permitted to send zone change notifications |
Zones | The number of secondary zones using the set. Select the count to view the applied zones |
Description | Additional information about the set for future reference |
To view the zones using a set, select its count in the Zones column. The Applied zones panel lists those zones. Select a zone name to open it.
Create an inbound IP set
Select Create inbound IP set.
Enter a Name that identifies the set.
In Transfer from, enter the IP addresses of the primary nameservers used for zone transfers.
Separate multiple addresses using commas, new lines, or spaces.
In Receive notifications from, enter the IP addresses or network ranges permitted to send zone change notifications.
Separate multiple addresses or ranges using commas, new lines, or spaces.
Optionally, enter a Description for future reference.
Select Create.
After creating the set, assign it to a secondary zone during zone creation or from the zone’s Settings tab. You can select a TSIG key when assigning the set. The default selection is None (Default).
To edit an inbound IP set, select its edit icon on the Inbound IP sets page, update the settings, and select Update.
Apply inbound IP sets to secondary zones
Apply an inbound IP set to a secondary zone to identify its primary nameservers and permitted notification sources.
Before creating the secondary zone, complete the transfer and notification configuration at your primary provider. Creating or assigning an inbound IP set does not configure access permissions or notification destinations at that provider.
Apply an inbound IP set when creating a secondary zone
Go to DNS > Zones and select Create zone.
Select Secondary zone.
Enter the Zone name.
Select an Inbound IP set. If the set does not exist, select Create inbound IP set from the menu.
Select a TSIG key if required, or leave None (Default) selected.
Optionally, enter a Comment to provide context for the audit log entry.
Select Create.
Change the inbound IP set for an existing secondary zone
Go to DNS > Zones and select the Secondary zones tab.
Open the zone and select its Settings tab.
Select the edit icon beside Inbound IP sets.
Select the inbound IP set and the appropriate TSIG key.
Select Apply.
The zone’s Inbound IP sets section displays the assigned set, its transfer sources, its notification sources, and the selected TSIG key.
After applying the set, review the zone’s Health tab to confirm that zone data is transferring from the intended primary nameservers. See DNS zone health for synchronization checks.
Transfer and notification sources
An inbound IP set identifies transfer and notification sources by IP address. Its two address lists serve different purposes:
Transfer from identifies the primary nameservers from which DigiCert® DNS retrieves zone data.
Receive notifications from identifies the sources permitted to notify DigiCert® DNS that zone data has changed.
These lists can contain different addresses. For example, a DNS provider may use one server to provide zone transfers and another to send change notifications. Configure each list using the addresses supplied by your primary DNS provider.
Assigning an inbound IP set connects these settings to a secondary zone. You can review the assigned set, its transfer sources, its notification sources, and the selected TSIG key in the zone’s Settings tab.
Notice
The addresses in an inbound IP set belong to your primary DNS provider. They are different from the DigiCert® service addresses your provider must allow for transfer requests or use as NOTIFY destinations.
At your primary provider, allow zone transfer requests from the required DigiCert® source addresses and configure notifications to the DigiCert® NOTIFY destinations. See Secondary nameservers and delegation for the address lists and configuration instructions.
Do not enter those DigiCert® service addresses in Transfer from or Receive notifications from.
Inbound IP sets and TSIG keys
TSIG uses a shared secret to authenticate DNS messages between servers. If your primary DNS provider requires TSIG, configure matching key details in DigiCert® DNS and at the primary provider.
Select a TSIG key when assigning an inbound IP set to a secondary zone. In this workflow, the key is selected alongside the set’s assignment to the zone.
You can select an existing key or choose Create TSIG key from the key menu. If TSIG is not used, leave None (Default) selected.
To change the selected key for an existing secondary zone, open its Settings tab, select the edit icon beside Inbound IP sets, choose the appropriate TSIG key, and select Apply.
See TSIG keys for key creation, supported algorithms, and guidance on changing shared credentials.
IPv4 and IPv6 addresses
An inbound IP set can identify primary nameservers using IPv4 and IPv6 addresses. You can include both address types in the same set.
For example, a set could contain these primary nameserver addresses:
Address type | Example |
|---|---|
IPv4 |
|
IPv4 |
|
IPv6 |
|
Enter the IP addresses of the servers that provide zone transfers. If your provider uses separate sources for notifications, add those to Receive notifications from.