route 53 ACM cert api gateway custom domain stopped working

Question

Hi, my custom domain was working just fine yesterday. I didn't change anything in the console. This morning my site is no longer reachable by the custom domain. I can access it from the public api gateway url, however: ``` ~ dig SOA coreycc.com ; <<>> DiG 9.10.6 <<>> SOA coreycc.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 34975 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTION SECTION: ;coreycc.com. IN SOA ;; AUTHORITY SECTION: com. 277 IN SOA a.gtld-servers.net. nstld.verisign-grs.com. 1708373230 1800 900 604800 86400 ;; Query time: 2 msec ;; SERVER: 192.168.0.1#53(192.168.0.1) ;; WHEN: Mon Feb 19 12:17:57 PST 2024 ;; MSG SIZE rcvd: 116 ``` ``` ~ dig SOA 3pk16lof2m.execute-api.us-west-2.amazonaws.com ; <<>> DiG 9.10.6 <<>> SOA 3pk16lof2m.execute-api.us-west-2.amazonaws.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3805 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ;; QUESTION SECTION: ;3pk16lof2m.execute-api.us-west-2.amazonaws.com. IN SOA ;; AUTHORITY SECTION: execute-api.us-west-2.amazonaws.com. 900 IN SOA ns-508.awsdns-63.com. awsdns-host******.amazon.com. 1 7200 900 1209600 86400 ;; Query time: 16 msec ;; SERVER: 192.168.0.1#53(192.168.0.1) ;; WHEN: Mon Feb 19 12:18:36 PST 2024 ;; MSG SIZE rcvd: 159 ``` ``` ~ nslookup coreycc.com Server: 192.168.0.1 Address: 192.168.0.1#53 ** server can't find coreycc.com: NXDOMAIN ``` ``` ~ nslookup 3pk16lof2m.execute-api.us-west-2.amazonaws.com Server: 192.168.0.1 Address: 192.168.0.1#53 Non-authoritative answer: Name: 3pk16lof2m.execute-api.us-west-2.amazonaws.com Address: 35.155.9.54 Name: 3pk16lof2m.execute-api.us-west-2.amazonaws.com Address: 50.112.6.109 ```

Accepted Answer

The Whois results show that the Domain Status is "clientHold".
This is why we believe that name resolution is not possible.

According to the explanation of ICANN, these are measures to be taken when there is a problem with payment, so it would be better to check with AWS support.

```
Domain Name: COREYCC.COM
Registry Domain ID: 2852356781_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.registrar.amazon.com
Registrar URL: http://registrar.amazon.com
Updated Date: 2024-02-19T12:16:04Z
Creation Date: 2024-02-04T18:16:47Z
Registry Expiry Date: 2025-02-04T18:16:47Z
Registrar: Amazon Registrar, Inc.
Registrar IANA ID: 468
Registrar Abuse Contact Email: abuse@amazonaws.com
Registrar Abuse Contact Phone: +1.2067406200
Domain Status: clientHold https://icann.org/epp#clientHold 
Name Server: NS-1318.AWSDNS-36.ORG
Name Server: NS-161.AWSDNS-20.COM
Name Server: NS-1766.AWSDNS-28.CO.UK
Name Server: NS-842.AWSDNS-41.NET
```

route 53 ACM cert api gateway custom domain stopped working

Contenus pertinents