Troubleshooting

1. Check if the TLD is valid:
   # List all valid TLDs
   cat ~/.config/rdap/tlds.txt | grep -i "yourtld"
   
2. Update your bootstrap configs:
   rdap --update
   
3. Use explicit server override:
   rdap -s https://rdap.example.com example.com
   
4. For ccTLDs not in IANA bootstrap, add to ~/.config/rdap/tlds.local.json:
   {
     "example.tld": "https://rdap.example-registry.com/"
   }
   

• Verify the IP format is correct (standard or CIDR)
• Some IP ranges may not have RDAP coverage yet

• Ensure the AS number exists and is allocated
• Try with or without “AS” prefix: rdap 15169 or rdap AS15169

1. Update bootstrap URLs:
   rdap --update
   
2. Check IANA bootstrap service status:
   • Visit: https://data.iana.org/rdap/
   • Verify files are accessible: dns.json, asn.json, ipv4.json, ipv6.json
3. Manual config override: Create ~/.config/rdap/config.local.json:
   {
     "bootstrap": {
       "dns": "https://data.iana.org/rdap/dns.json",
       "asn": "https://data.iana.org/rdap/asn.json",
       "ipv4": "https://data.iana.org/rdap/ipv4.json",
       "ipv6": "https://data.iana.org/rdap/ipv6.json"
     },
     "cache": {
       "ttl_seconds": 86400
     }
   }
   
4. Clear cache:
   rm -rf ~/.cache/rdap/*
   

1. Update TLD list:
   rdap --update
   
   This downloads the latest tlds.txt from IANA.
2. Explicitly specify query type:
   rdap -t tld google
   
3. Use full domain syntax for domains:
   rdap google.com  # Clearly a domain
   

• Single word → Check if it’s in IANA TLD list → If yes: TLD, if no: check if numeric
• If numeric → AS number
• Otherwise → Domain

1. Use full IP notation:
   rdap 1.0.0.1  # Instead of 1.1
   
2. Explicitly specify type:
   rdap -t ip 1.1
   
3. Use CIDR notation:
   rdap 1.1.1.0/24
   

• 1.1 → 1.0.0.1
• 8.8 → 8.0.0.8
• 192.168 → 192.168.0.0

1. For IPv6 queries: Some servers don’t support host-level IPv6 queries. The client auto-retries with CIDR:
   rdap -v 2001:db8::1  # Use verbose to see retry attempts
   
   If auto-retry fails, manually use CIDR:
   rdap 2001:db8::/64
   rdap 2001:db8::/48
   rdap 2001:db8::/32
   
2. Check query format:
   • Domain: example.com (no trailing dot unless intentional)
   • IP: Valid IPv4 or IPv6 address
   • AS: Numeric only, AS prefix optional
3. Try different server:
   rdap -s https://rdap.arin.net/registry 8.8.8.8
   

1. Verify the resource exists:
   • Check domain registration elsewhere (DNS lookup)
   • Verify IP allocation (WHOIS)
   • Confirm AS number is allocated
2. Check if you’re querying the right server:
   rdap -v example.com  # Verbose shows server URL
   
3. Some registries may not have RDAP data:
   • Not all registries have transitioned from WHOIS to RDAP
   • Some objects may exist in WHOIS but not RDAP yet
4. For recently registered domains:
   • RDAP data may lag by a few hours
   • Try again later or use --server to query registrar directly

1. Increase timeout:
   rdap --timeout 60 example.com  # 60 seconds
   
2. Check internet connectivity:
   ping data.iana.org
   curl -I https://rdap.verisign.com/com/v1/
   
3. Verify firewall/proxy settings:
   • Ensure outbound HTTPS (port 443) is allowed
   • Check if corporate proxy is interfering
4. Try alternate bootstrap servers: Edit ~/.config/rdap/config.local.json with mirror URLs if available.
5. Use explicit server:
   rdap -s https://rdap.verisign.com/com/v1 example.com
   

1. Check if registry provides referral link:
   rdap -f json-pretty example.com | grep -A5 '"links"'
   
2. Some registries don’t include referral links:
   • This is compliant with RDAP spec
   • You’ll only get registry-level data
3. Disable referral following to see registry-only data:
   rdap --no-referral example.com
   
4. Manually query registrar if you know the URL:
   rdap -s https://rdap.markmonitor.com/rdap example.com
   

1. View detailed error with verbose mode:
   rdap -v example.com
   
2. Client falls back to registry-only data:
   • The query still succeeds with registry data
   • Warning is logged about registrar fetch failure
3. Try querying registrar directly:
   # Get registrar URL from registry response
   rdap --no-referral -f json example.com | jq '.links[] | select(.rel=="related")'
   
   # Query it directly
   rdap -s <registrar-url> example.com
   
4. Report to registrar if consistently failing:
   • May indicate misconfigured RDAP server
   • Some registrars still transitioning to RDAP

1. Check permissions:
   ls -la ~/.config/rdap/
   # Ensure directory is writable
   chmod 755 ~/.config/rdap/
   
2. Verify internet connectivity:
   curl https://raw.githubusercontent.com/xtomcom/rdap/main/config/config.json
   
3. Check disk space:
   df -h ~
   
4. Manual update:
   cd ~/.config/rdap/
   curl -O https://raw.githubusercontent.com/xtomcom/rdap/main/config/config.json
   curl -O https://raw.githubusercontent.com/xtomcom/rdap/main/config/tlds.json
   curl -O https://data.iana.org/TLD/tlds-alpha-by-domain.txt
   mv tlds-alpha-by-domain.txt tlds.txt
   

1. Verify file location:
   ls ~/.config/rdap/*.local.json
   
   Files must be in ~/.config/rdap/, not /etc/rdap/
2. Check JSON syntax:
   cat ~/.config/rdap/tlds.local.json | jq .
   
   If this errors, you have invalid JSON.
3. Verify file is being loaded:
   rdap -v example.io 2>&1 | grep -i "config\|override"
   
4. For TLD overrides, ensure correct format:
   {
     "io": "https://rdap.identitydigital.services/rdap/",
     "com.af": "https://rdap.coccaregistry.org/rdap/"
   }
   
   Keys are TLDs (lowercase), values are base RDAP URLs with trailing slash.

1. Clear cache:
   rm -rf ~/.cache/rdap/*
   
2. Update configs and cache:
   rdap --update
   rm -rf ~/.cache/rdap/*
   rdap example.com  # Re-populates cache
   
3. Adjust cache TTL: Edit ~/.config/rdap/config.local.json:
   {
     "cache": {
       "ttl_seconds": 3600
     }
   }
   
   Lower value = more frequent bootstrap fetches, higher latency but fresher data.
4. Disable caching (for debugging):
   {
     "cache": {
       "ttl_seconds": 0
     }
   }
   

​

Bootstrap Errors

​

HTTP Errors

​

Query Errors

​

Network Errors

​

JSON Errors

​

I/O Errors

1. Enable caching (default):
   • First query fetches bootstrap (slow)
   • Subsequent queries use cache (fast)
2. Pre-warm cache:
   rdap example.com  # Populates DNS bootstrap cache
   rdap 8.8.8.8      # Populates IPv4 bootstrap cache
   rdap AS15169      # Populates ASN bootstrap cache
   
3. Use explicit server to skip bootstrap:
   rdap -s https://rdap.verisign.com/com/v1 example.com
   
4. Batch queries in scripts:
   # Share client instance in library usage
   let client = RdapClient::new()?;
   for domain in domains {
       client.query(&RdapRequest::new(QueryType::Domain, domain)).await?;
   }
   
5. Reduce timeout for faster failures:
   rdap --timeout 10 example.com  # 10 seconds instead of 30
   

1. For CLI usage:
   • Memory usage is minimal (typically less than 10 MB)
   • If high, may indicate network buffering of large responses
2. For library usage with many queries:
   // Drop large responses when done
   let result = client.query(&request).await?;
   // Process result
   drop(result);  // Explicit drop if holding many in memory
   
3. Limit JSON output size:
   rdap -f json example.com | head -n 100  # Truncate large responses