I have a domain, originally from GoDaddy, eventually transferred to AWS; it's under Registered Domains in Route53. The status is "clientTransferProhibited", which is one of the "ok" statuses, and the domain is not yet expired (good until 2020-07-12)
But it stopped working at some point (not sure exactly when or why). It used to, I had it point to a bunch of different EC2 instances, an S3 website, used it with and without subdomains, no problems, until I recently tried to use it with a Digital Ocean droplet (just put the IP in the Record Set as an A record), and discovered it's no longer working. Pings just time out, traceroute hangs.
I checked whois - and the results confused me, because it's saying the registrar is some Gandi SAS. Never heard the name before; I own a couple other domains, and they show Godaddy in the Registrar part of whois response, as expected. After domain was transferred to AWS, I expect AWS tp show up as a registrar.
Name Servers listed in whois response seem to be correct though - same as I see in the Domain section in Route53, and same as are listed in Value of type NS in the Hosted Zone.
and yet: traceroute: unknown host alexakarpov.xyz =|
what am I doing wrong?
If you provided the true name, any online tool shows the problem: http://dnsviz.net/d/alexakarpov.xyz/dnssec/
You have a lame delegation.
xyz authoritative nameservers are telling:
$ dig @$(dig ns xyz. +short|tail -1) alexakarpov.xyz NS | grep 'IN NS '
alexakarpov.xyz. 1h IN NS ns-102.awsdns-12.com.
alexakarpov.xyz. 1h IN NS ns-1223.awsdns-24.org.
alexakarpov.xyz. 1h IN NS ns-1724.awsdns-23.co.uk.
alexakarpov.xyz. 1h IN NS ns-954.awsdns-55.net.
Asking any of those nameservers:
for ns in ns-102.awsdns-12.com. ns-1223.awsdns-24.org. ns-1724.awsdns-23.co.uk. ns-954.awsdns-55.net. ; do dig @$ns alexakarpov.xyz NS +noqr| grep status; done
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 57934
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 14503
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 48681
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 12837
None of the listed nameservers at parent are authoritative for your name, so you have a lame delegation.
You need either to fix those nameservers, in order for them to be authoritative on your domain name, or you need to change nameservers for some that are authoritative on your nameserver.
Who is your registrar does not come into play in the above, except if you need to change your nameservers, which is something that needs to happen through your registrar.
PS: you can see the list of gTLD registrars at https://www.internic.net/alpha.html this is the official list. Amazon is listed but then which registrar sponsors your domain name is something to see in whois, which is its sole use in your case.