1 個回答
- 最新
- 最多得票
- 最多評論
0
Hello, here are some possible solutions you can try for troubleshooting :)
- Determine if the domain status: Active or Suspended (clientHold)
-
Install whois For the instruction how to install whois: https://www.cyberciti.biz/faq/how-to-install-whois-on-ubuntu-debian-linux/
-
Run the following command to check the domain status For Windows: Open a Windows command prompt, and then enter whois -v example.com. For Linux: Open your SSH client. In the command prompt, enter whois example.com.
- Make sure that the your domain name is on the domain register
- In the whois output, note the Name Servers
- Open the Route 53 console
- Confirm that the Name Servers listed in the Host zone details are the same to the Name Servers in 1.
- Check for subdomain delegation issues
- Check the parent hosted zone (example.com) for a Name Server record for the domain name: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-listing.html
- Confirm that the parent hosted zone contains a record for the (sub)domain name that you're trying to resolve
- For more information on configuring multiple levels of subdomain delegation, see https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-routing-traffic-for-subdomains.html#dns-routing-traffic-for-sub-subdomains
- Check if the issue you encounter is the result of negative caching
- Note that NXDOMAIN response is considered a negative response, being stored in negative caching from an authoritative name server in the cache
- Note that NXDOMAIN response usually occurs when the record neg.example.com doesn't exist
已回答 1 年前
相關內容
- AWS 官方已更新 2 年前
- AWS 官方已更新 9 個月前