Succesfully set up DNS Alias but content is still from older server

I build my next js site 2.0 and deployed on netlify (https://travel-belgium.
As Netlify doesn’t support .be domains yet I followed the instructions to use Alias on my DNS.
The site setting console seems to show everything went succesful (see picture, no error’s). And alias on my DNS system is also fine.
Yet the content on https://travel-belgium.be and https://travel-belgium.netlify.app is still different between old site and the new site.

How is that possible?

It is working fine now @atjpatatatj2. Propagation of records takes time.

Hey Dig,
Thanks for replying. However it’s not working fine now :stuck_out_tongue: . I just checked and travel-belgium.be is still not the same content as https://travel-belgium.netlify.app

Homepage looks the same to me. What exactly is different?

$ dig travel-belgium.be
travel-belgium.be.	4502	IN	A	75.2.60.5
travel-belgium.be.	4502	IN	A	99.83.231.61
travel-belgium.be.	4502	IN	A	185.86.18.163

Might have something to do with the extra A records. Delete records 2 and 3 above.

Also, set up a domain-level redirect so travel-belgium.netlify.app redirects to travel-belgium.be

correct content net netlify subdomain

Old content on travel-belgium.be

only found one extra A record in my DNS system, I deleted it now it looks like this

I can’t setup the domain-level dedirect because netlify doesn’t accept my domain as .be is not supported :smiley:

removing the extra A record seemed to have worked!
Thanks!

Yes you can! If you read the documentation I linked you’d know the redirect is done via a _redirects file like this

https://travel-belgium.netlify.app/*    https://travel-belgium.be/:splat

It’s already solved so thank you for that :slight_smile: