Fix missing DNS controls, read-only zones and limit messages

DNS access is determined by your account, the service that grants the zone, its package and the connected DNS provider. Read the specific message before changing the records or ordering a different service.

01 Check the account and service

Sign in to the client account that owns the domain or qualifying service. If you use a linked WHMCS user, ask the account owner to check your domain or service-management permission. A zone may also become unavailable when its granting service ends or when ownership records require review.

Why are DNS controls missing or records read-only?

  • Read only: your access mode or server connection permits inspection but blocks changes.
  • Zone locked: an administrator or current operation has protected the zone. Read any displayed reason and contact support when necessary.
  • Record type unavailable: the package or DNS backend does not permit that type.
  • Limit reached: the package ceiling applies to zones, records or retained backups. Removing unnecessary records may help only when they are genuinely no longer used.
  • Feature not included: DNSSEC, import/export, record sets, backups or Premium features have separate access rules.
  • Nameservers required: the package allows setup information but requires its DNS delegation before customer record edits.

02 Resolve without disturbing working services

  1. Refresh the domain and check whether a recent order or DNS task is still completing.
  2. Confirm the correct active domain or hosting service is selected.
  3. Read the displayed usage against the package limit.
  4. For a nameserver restriction, compare current delegation with the assigned nameservers. Preserve website and email records before changing delegation.
  5. Use an available package upgrade only after checking what it changes and its current price.
  6. Contact support with the exact restriction if it does not match your service.

03 What not to remove to gain space

A record you do not recognise may be necessary for email authentication, certificate renewal, website verification or a subdomain. Export the zone and identify the owner of each entry before removing it. Protected and forwarder-owned records should be managed through their associated service.

Include the domain, service name, relevant limit and the error text in your request. Support can distinguish a plan limit from an ownership conflict or a provider error. A browser refresh cannot grant server-side permissions, and using a different client account is not a valid way to manage someone else's zone.

  • 0 Users Found This Useful
  • domains-dns, domain-nexus
Was this answer helpful?

Related Articles

Back up and restore DNS records

A DNS backup records the zone's entries so you can review or restore a previous configuration....

Use bulk DNS changes across one or several zones

Bulk management is useful when several records need the same new address or TTL. It also...

Add a domain registered elsewhere to your DNS Manager

You can manage DNS for a domain registered with another company when your Nabtech service...

Read a DMARC aggregate report in DNS Manager

The Premium DNS Plus report reader helps you inspect a DMARC aggregate report received from an...

Enable DNSSEC and complete the DS-record setup

DNSSEC lets validating resolvers check signed DNS data against a chain of trust. It needs both...