When running DNS diagnostics for www.empleosmadrid.es, you encountered the critical error: "Delegation not found at parent. No delegation could be found at the parent, making your zone unreachable from the Internet." This indicates a broken DNS chain where the parent domain (.es TLD) doesn't properly point to your nameservers.
The DNS hierarchy requires proper NS (Name Server) records at each level. For empleosmadrid.es to resolve, the .es registry must contain correct NS records pointing to your authoritative nameservers. The error suggests this delegation is missing or incorrect.
// Example of proper DNS delegation
$ dig NS empleosmadrid.es +trace
; <<>> DiG 9.16.1 <<>> NS empleosmadrid.es +trace
;; global options: +cmd
. 516371 IN NS a.root-servers.net.
. 516371 IN NS b.root-servers.net.
...
es. 172800 IN NS n3dns.nic.es.
es. 172800 IN NS sns-pb.isc.org.
...
empleosmadrid.es. 86400 IN NS ns1.yourhostingprovider.com. <-- THIS MUST EXIST
1. Check parent delegation using WHOIS:
whois empleosmadrid.es | grep -i "Name Server"
2. Compare with your actual nameservers:
dig NS empleosmadrid.es @8.8.8.8
Case 1: New domain not fully propagated
# Solution: Wait 24-48 hours or contact registrar
Case 2: Incorrect NS records at registrar
# Corrective action (example for Cloudflare):
curl -X PATCH "https://api.cloudflare.com/client/v4/zones/:zone_id/dns_records/:identifier" \
-H "Authorization: Bearer API_TOKEN" \
-H "Content-Type: application/json" \
--data '{"type":"NS","name":"empleosmadrid.es","content":"ns1.yourdns.com"}'
For complex cases, verify glue records at TLD level:
dig @a.root-servers.net empleosmadrid.es NS
dig @n3dns.nic.es empleosmadrid.es NS
Check for DNSSEC misconfiguration that might break delegation:
delv empleosmadrid.es
The .es domain registry has particular requirements:
- Minimum 2 nameservers
- Glue records must be properly registered
- Changes may take longer than generic TLDs
Always verify with NIC España's official tool: https://www.nic.es/
When running DNS checks for domains like www.empleosmadrid.es, you might encounter the critical error: "Delegation not found at parent. No delegation could be found at the parent, making your zone unreachable from the Internet." This indicates a broken DNS chain where parent nameservers don't properly reference child nameservers.
The error occurs when:
- NS records at registrar don't match authoritative nameservers
- Glue records are missing for subdomains
- DNS propagation hasn't completed (though this is temporary)
- Incorrect TTL values causing caching issues
Use these terminal commands to verify the issue:
# Check parent nameserver records
dig NS empleosmadrid.es @a.gtld-servers.net +short
# Verify authoritative servers
dig NS www.empleosmadrid.es +trace
# Check for glue records
host -t NS empleosmadrid.es
For a domain hosted on AWS Route53 (common scenario):
# Step 1: Get your nameserver delegation set from AWS
aws route53 get-hosted-zone --id Z1PA6795UKMFR9 \
--query 'DelegationSet.NameServers'
# Expected output:
[
"ns-2048.awsdns-64.com",
"ns-2049.awsdns-65.net",
"ns-2050.awsdns-66.org",
"ns-2051.awsdns-67.co.uk"
]
# Step 2: Update at your domain registrar
# (Example for GoDaddy API)
curl -X PUT "https://api.godaddy.com/v1/domains/empleosmadrid.es/records/NS" \
-H "Authorization: sso-key ${GODADDY_API_KEY}" \
-H "Content-Type: application/json" \
-d '[{"data":"ns-2048.awsdns-64.com"},{"data":"ns-2049.awsdns-65.net"}]'
After making changes, verify with:
- Google DNS Tool
dig +nocmd www.empleosmadrid.es NS +noall +answer- Global DNS Propagation Checker
For complex setups with subdomains, ensure:
# Subdomain NS record must exist in parent zone
$ORIGIN empleosmadrid.es.
subdomain 3600 IN NS ns1.subdomainhost.com.
subdomain 3600 IN NS ns2.subdomainhost.com.
# Corresponding glue records at registrar
ns1.subdomainhost.com. IN A 192.0.2.1
ns2.subdomainhost.com. IN A 192.0.2.2