If there is a difference between what you see at the custom domain and what you see at the generated URL for your latest production deployment, there are a few things you can do to get them in sync.
Custom Domain Update Tips & Tricks
Create a new deployment
If you recently added the custom domain, but did not created a new deployment afterward, that could explain why it doesn’t work yet.
Some project configuration changes can’t be applied instantly. If you made a change but don’t see it reflected on your site, try creating a new production deployment (or redeploy the most recent one).
Hard refresh the website
Sometimes the problem is caused by local browser caching. In that case, you can hard refresh or clear the local browser cache to fix the problem. This will load all new copies of the site files so you should see the latest version of your site.
Double check DNS records
Sometimes a stray DNS record causes a domain to point to the wrong site. Make sure you have deleted any old DNS records and added the records request to use the domain your Vercel project. You can find complete instructions for how to configure your domain and investigate remaining DNS issues in the Vercel documentation.
Make sure the domain is assigned to the production branch
If your custom domain is not assigned to your production branch, then it will not match your latest production deployment. Instead, it will show the latest preview deployment from the assigned branch.
You can fix this in Project Settings by clearing the Git Branch input box in your custom domain settings. After you make a new deployment, you should see the changes reflected when visiting your custom domain address.
Check that the custom domain is assigned to the right deployment
When you have a custom domain added to your project, it will automatically be assigned to the latest production branch by default. That means it’s updated each time a new production deployment is made. You should see that reflected in the deployment details.
Preview deployments will not be assigned the custom domain unless the domain was configured for a preview git branch instead of the default production configuration.
If you’re comparing against a preview domain, or an outdate production domain, that would explain why the generated URL and custom domain don’t match. In that case they would actually be pointing at different deployments.
Reach out for help
If none of those tricks work for your project, then it might be time to ask the community for more ideas. We can debug it together if you create a new #help post with as many relevant details and code examples as you're able to include.