Manage internal zones

Refer to the following sections to learn how to manage your internal DNS zones.

Configuration conditions

When setting up internal zones, observe the following conditions:

• Internal zones can contain the same DNS record types that Cloudflare supports for public zones.
• An internal zone can have the same name as a public zone in the same account.
• Each internal zone can be linked to multiple views.
• There can be several internal zones with the same name in one account. However, two internal zones with the same name cannot be linked to the same view.
• Internal zones are not subject to any top-level domain (TLD) restrictions. This means that an internal zone can be created if its TLD is not registered publicly (for example, xyz.local), if it is created on the TLD itself (local), or even if on the root (.).

Create an internal zone

1. Use the Create Zone endpoint to create an internal zone. Specify your account ID and set the type to internal.

2. Add DNS records to your internal zone using your preferred option:

• Import a formatted BIND file. Refer to the DNS records how-to for guidance.
• Use other API endpoints, such as /batch, to manage DNS records. Refer to Batch record changes for details.

3. Repeat this process for each internal zone you wish to add.

Other actions

The API endpoints to manage internal zones are the same as for managing public zones. The main difference is that the zone type must be set to internal. Refer to the API documentation below for details:

• Update an internal zone (PATCH)
• Get internal zone details (GET)
• List internal zones (GET)
• Delete an internal zone (DELETE)