Checking your DNS and domain name setup—confirming you're on the right track.
Checking your DNS and domain name setup—confirming you're on the right track.
I've taken care of the server after losing my lab webserver due to a missing domain. I decided to proceed with moving it to a VPS. Everything is now configured on the VPS and it's functioning properly. I'm still unsure about updating the DNS zone for my new domain and have some doubts. Although I'm halfway through the 48-hour propagation period, I can't act until tomorrow. My idea is to change the A record and point it to the VPS IP address—should that suffice? Are there any differences between editing the record myself versus using the redirect wizard? Should I include both mydomain.xyz and www.mydomain.xyz in separate A records, or will one replace the other? My VPS supports adding a secondary domain, which suggests I should add an "ownercheck" TXT record for that subdomain. Is this the best approach? I'm using Apache with virtual servers (or at least I plan to once the domain is live), so I wonder if I need to define each subdomain as a CNAME or if Apache can handle routing on its own. Since I obtained both the VPS and domain from OVH, I don't see why I can't link them automatically through their admin panel—it feels overly complicated.
No concept, because I don’t understand the service or the wizard’s role. Usually you set the base domain and use CNAME records like A-name pointing to your server and www pointing to the site itself. It’s unclear what “overwite” means, but yes, including both IPv4 and IPv6 addresses is a good practice if connectivity issues arise.
OVH that's correct. Then defining each Apache Virtual Server as a CNAME also seems necessary. I initially thought so, but when I tried, I received a warning about potential conflicts. It appears this is just the standard "If A or AAA exists while adding A or AAA then WARN" rule.
When multiple services share the same IP address, it works. Applying CNAME records is beneficial because you only have to modify one entry when the IP changes, directing everything to the updated address. It might seem unusual to caution about this, given many servers use dual-stack IPs.