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.
IN THIS ARTICLE
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
- Refresh the domain and check whether a recent order or DNS task is still completing.
- Confirm the correct active domain or hosting service is selected.
- Read the displayed usage against the package limit.
- For a nameserver restriction, compare current delegation with the assigned nameservers. Preserve website and email records before changing delegation.
- Use an available package upgrade only after checking what it changes and its current price.
- 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.