DNS resolution/propagation issue

Hello.

When did you purchase the domain "uarkcapstone.com"?
Checking the "whois" command shows that the domain was purchased relatively recently, but when you purchase a domain through Route53, a confirmation email is sent to your email address.
The body of the email contains a link, and if you do not click it, your domain will be suspended.

whois uarkcapstone.com
   Domain Name: UARKCAPSTONE.COM
   Registry Domain ID: 3025458407_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.registrar.amazon
   Registrar URL: http://registrar.amazon.com
   Updated Date: 2025-10-02T20:33:42Z
   Creation Date: 2025-10-02T20:23:20Z
   Registry Expiry Date: 2026-10-02T20:23:20Z

Did you click on the link in the domain verification email?
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-click-email-link.html

If you don't click the link in the email in the allotted amount of time, ICANN generally requires that we suspend the domain or cancel the operation, depending on what you were trying to do:

Based on your description, there's a mismatch between the IP address you intended to set (44.217.238.144) and what's actually being returned by the DNS servers (128.129.48.59). This indicates an issue with your Route 53 configuration.

Here are some steps to troubleshoot and resolve this issue:

1. Verify your A record in Route 53: Double-check that your A record in the hosted zone is correctly configured to point to 44.217.238.144 (your Elastic IP). It appears that the A record might be pointing to a different IP address (128.129.48.59).

2. Check for multiple hosted zones: Ensure you don't have multiple hosted zones for the same domain, which could cause confusion. If you created a new hosted zone manually after registering the domain, the nameservers might be pointing to different configurations.

3. TTL considerations: Check the Time-to-Live (TTL) values on your DNS records. Lower TTL values (e.g., 60 seconds) can help speed up propagation after you make corrections.

4. Clear your DNS cache: After making any changes, clear your local DNS cache to ensure you're not seeing cached results.

5. Wait for propagation: After confirming all settings are correct, DNS changes can take up to 48 hours to propagate globally, though most changes are visible within a few hours.

6. Use DNS propagation checkers: Continue using tools like whatsmydns.net or dnschecker.org to monitor the global propagation of your DNS records.

The fact that all the nameservers are returning the same incorrect IP address suggests that the A record in your Route 53 hosted zone is configured with the wrong IP. I recommend checking your Route 53 console and updating the A record to point to your Elastic IP address.
Sources
Troubleshoot DNS resolution issues for records in Route 53 public hosted zones | AWS re:Post
Route 53 domain dns not propagating | AWS re:Post
Migrated domain to AWS and DNS not working in many places | AWS re:Post
DNS Propagation Issues with Domain Registered in Route 53 - No Propagation After 48 Hours | AWS re:Post