Figured it out with the help of ChatGPT. I followed these instructions:

Potential Issues:

• The URL Redirect Record could be conflicting with the A record, which is expected to handle the root domain (@). Try temporarily removing the URL Redirect Record and check if that resolves the issue.
• Caching or Propagation Delays: If you've made recent changes, make sure that DNS propagation has completed across all servers, which could take up to 48 hours. However, since you mentioned it's been weeks, this might not be the case.

Suggested Steps:

1. Remove the URL Redirect Record for @.
2. Wait a bit (or use DNS propagation checkers) to see if that clears the conflict.
3. If removing the redirect works but you still want redirection from @ to www, you could set up that redirect using Vercel’s platform instead of a DNS redirect.

Hi,

I can confirm that your hostname isn't returning the necessary DNS record yet: https://dnschecker.org/#A/lawrencluo.me

Hi, I think you had a typo in the address. It should be lawrenceluo.me which does now have just one address listed, which is the correct IP.

I just checked the records for the domain and it seems to be working now.

If you run into trouble with a custom domain in the future, Vercel has a domain troubleshooting guide to help.

https://vercel.com/docs/projects/domains/troubleshooting

vercel.com

Troubleshooting domains

Learn about common reasons for domain misconfigurations and how to troubleshoot your domain on Vercel.