Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Depending on the configuration, you may or may not be able to delete or schedule the deletion of a zone and all its contents. Superusers can determine which group of users are allowed to delete or schedule the deletion of a zone and all its contents. For information about how to configure the recursive deletion of zones, see Configuring Recursive Deletions of Networks and Zones.
Note that you must have Read/Write permission to all the subzones and resource records in order to delete a zone. The possible effects of removing or re-parenting are illustrated in Figure 19.4figure Removing or Reparenting Subzones.
The appliance puts all deleted objects in the Recycle Bin, if enabled. You can restore the objects if necessary. When you restore a parent object from the Recycle Bin, all its contents, if any, are re-parented to the restored parent object. For information about the Recycle Bin, see Using the Recycle Bin.
Anchorbookmark1792bookmark1792
Figure 19.4 Removing or Reparenting Subzones

Drawio
border1
baseUrlhttps://infoblox-docs.atlassian.net/wiki
diagramName19.4
zoom1
custContentId7933139
pageId26476850custContentId7933139
lbox1
contentVer1
revision1

...

  • Consider in-addr.arpa zone having 10.10.in-addr.arpa + 10.0.0.1 (PTR record)
  • If you add 10.in-addr.arpa, then 10.10.in-addr.arpa is reparented under 10.in-addr.arpa
  • and 10.0.0.1 PTR record is reparented from in-addr.arpa to 10.in-addr.arpa.
  • If you delete 10.in-addr.arpa, then 10.10.in-addr.arpa is reparented under in-addr.arpa (depending on the Remove zone only/ Remove all subzones option) and 10.0.0.1 PTR record is deleted along with 10.in-addr.arpa zone.
  • When you remove a zone and reparent its subzones, any subzone that inherited its admin access settings from its previous parent zone (as opposed to having specific access settings for the subzone) now receive their settings from its new parent zone, which might be different. See Figure 19.5.

...

  • the following figure:


Changed Admin Access Settings after Reparenting Subzones

Drawio
border1
baseUrlhttps://infoblox-docs.atlassian.net/wiki
diagramName19.5
zoom1
custContentId8653819
pageId26476850custContentId8653819
lbox1
contentVer1
revision1

...

Note
titleNote

Instead of removing a zone, you can also disable it. For more information, see see Enabling   and   Disabling   Zones.


To remove a zone:

  1. From the Data Management tab, select the DNS tab -> Zones tab.
  2. Click the checkbox of the zones you want to delete.
  3. Click the Delete icon.
  4. Select one of the following. Note that these options appear only if you are allowed to delete zones and all its contents. For information about how to configure this, see see Configuring Recursive Deletions of Networks and Zones.
    • Remove zone only: Select this to remove the zone and all its content. The appliance reparents all subzones to the parent zone of the zone that you want to remove, except for the automatically created AD (Active Directory) subzones.
    • Remove all subzones: Select this to remove the selected zone, all its subzones, and all the resource records of the selected zone and its subzones.
  5. Click Yes. Grid Manager displays a warning message. Click Yes to continue or No to cancel the process. Note that this process may take a longer time to complete depending on the size of the data.

You can also schedule the deletion for a later time. Click Schedule Deletion and in the Schedule Change panel, enter a date, time, and time zone. For information, see Scheduling Deletions. For information about scheduling recursive deletions of zones, see see Scheduling Recursive Deletions of Network Containers and Zones.