What Does This Error Mean?
The error message "Operation can't be performed - Zonecheck message" indicates issues with your domain's DNS zone configuration. This typically occurs during domain operations such as nameserver changes or domain transfers.
This error is triggered during the zonecheck — a technical pre-delegation check performed by many national domain registries (e.g., .IS, .NO, .IE, .BR, etc.) to ensure DNS compliance before allowing critical changes.
Regardless of the specific TLD, the zonecheck usually verifies that:
The nameservers are properly configured and reachable.
A valid zone file for your domain is installed on those servers.
Technical requirements specific to the registry are fully met.
If the domain fails the check, the operation is blocked.
Why Does This Happen?
Common reasons for this error include:
Zone file is missing: NS records are set, but no actual zone is installed.
Zone file contains errors, such as:
Missing required records (e.g.,
SOA,NS,A)Syntax issues or invalid formatting
TTL values or record settings that violate the registry’s policy
Mismatched or inconsistent data between nameservers
DNS servers are unreachable or do not respond to queries from the registry's network.
How to Fix It: Step-by-Step Guide
1. Check Nameserver Configuration
Ensure that your nameservers:
Host the correct and active zone file for your domain.
Are reachable on UDP port 53.
Respond with a valid
SOArecord when queried.
If you use external DNS services (e.g., Cloudflare, AWS Route53, DigitalOcean), make sure the zone is properly set up and published.
2. Use Your Registry’s Zonecheck Tool
Most registries offer an online test tool for checking zone compliance. For example:
ISNIC (.IS): https://www.isnic.is/en/domain/test
IE Domain Registry (.IE): https://www.iedr.ie
Registro.br (.BR): https://registro.br
Run the test for your domain. If issues are detected, the tool will provide a detailed report.
3. Fix Zone Errors
Based on the test results:
Add missing records (
SOA,NS,A, etc.)Correct TTL values and ensure consistent data
Verify that all NS servers are correctly serving the same zone
Restart your DNS service or flush caches if needed
4. Retry the Operation
After resolving all configuration issues:
Return to your registry’s control panel.
Retry the operation (e.g., nameserver update, transfer).
It should now complete without errors.
Best Practices
Never assign nameservers to a domain before the zone is properly configured on them.
All NS servers must return the same, authoritative data.
If you’re unsure, consult your DNS provider or hosting company.
Example of a Valid Zone File
$ORIGIN yourdomain.is.
@ 3600 IN SOA ns1.example.com. hostmaster.yourdomain.is. (
2025061801 ; serial
3600 ; refresh
1800 ; retry
1209600 ; expire
3600 ) ; minimum
IN NS ns1.example.com.
IN NS ns2.example.com.
IN A 192.0.2.1 www
IN A 192.0.2.1