When the domain acquired by Name.com suddenly becomes unusable

I'm using RDS, EC2, and route53 for my deployment. This time, if you check the status with the command dig acquired domain in the terminal status: NXDOMAIN </ font> was found and it took me a day to resolve it.

If it suddenly becomes unusable, the solution is ① Check if you can access by IP address.

If you can access by IP address, check the following contents. ① Log in to your name dot com and check if there are any important notices. (2) Check if important emails have arrived.

In my case, in the email Please correct the registration information by 12:00 on xx / xx / 20xx. I received it The domain was unavailable because the specified date was exceeded without noticing it. After correcting the registration information, the domain became available in about 3 days. Many emails from your name dot com ....

Explanation of dig command

Recommended Posts

When the domain acquired by Name.com suddenly becomes unusable
When yum becomes unusable
When using FloatingPanel, the tableView created by Stroybard becomes nil
LIMIT 11 when data is acquired by irb
A note when the heroku command becomes unavailable