Half of “I changed DNS and the site died” tickets actually changed nameservers; the other half edited an A record inside a zone. Both get called “DNS,” but they are different jobs. Doing one while watching the other panel is how you spend an afternoon asking why nothing propagates.
Changing nameservers chooses which authority the world asks. Editing DNS records changes A, CNAME, MX, and TXT lines inside that authority’s zone. At EuroVDC the authority pair is ns1.eurovdc.eu and ns2.eurovdc.eu. This article splits the two jobs and tells you when to use each.
What nameservers control
The NS hosts you set at the registrar tell resolvers who answers for the domain. Point NS at EuroVDC and the A/MX rows in the old hosting panel stop being authoritative — they may still display, but the internet no longer queries them. Conversely, adding records in the EuroVDC zone while NS still points elsewhere does not move live traffic.
NS changes propagate from minutes to about 48 hours depending on TTL and parent caches. For a clean cut, populate the destination zone first, then flip NS. Record types walkthrough: change nameservers and manage DNS records (A, CNAME, MX, TXT).
What zone records control
When NS already is ns1.eurovdc.eu / ns2.eurovdc.eu, you work in the EuroVDC DNS panel: A or CNAME for www, A for the apex, MX for mail, TXT for proofs. Corporate mail typically uses MX securemail.eurovdc.eu (priority 10) and SPF like v=spf1 mx ip4:45.84.90.12 -all. Mail record meaning: SPF, DKIM, DMARC and deliverability.
Moving one subdomain to another IP does not require a nameserver change — edit that A/CNAME. Moving all DNS management to EuroVDC means prepare the zone, then change NS. Reverse order yields empty or partial answers.
Common mix-ups
- Web host moved, NS forgotten: visitors still hit the old IP.
- NS moved, MX not copied: site loads, mail dies.
- Updating the same record in two panels: only the authoritative NS zone counts.
- Putting a CNAME on the apex (@): invalid or risky on many TLDs — follow A/ALIAS policy.
Keeping corporate mail and web in one zone: see corporate email; DNS still rides ns1/ns2.
Suggested order
- Build A, MX, TXT, DKIM in the destination zone and verify with dig (you can inspect a non-authoritative copy before the NS flip).
- Set registrar NS to
ns1.eurovdc.euandns2.eurovdc.eu. - Watch propagation; old answers linger until TTL expires.
- Keep the old panel as backup briefly, then clean up.
Nameserver = whose panel is law; records = what that panel publishes. Do not blur both into “I changed DNS.”
FAQ
Do I need to change NS just to edit MX?
No. Edit MX in whichever panel is authoritative. Change NS only when you move authority.
Must I enter both ns1 and ns2?
Yes. Register both EuroVDC nameservers. A single NS weakens redundancy and can fail registrar checks.
Does an NS change cut mail immediately?
Only if the new zone lacks MX/SPF. Pre-copy the zone and mail usually continues.
Is a CDN CNAME the same as changing nameservers?
No. CDNs usually want a www CNAME inside the zone — that is a record edit, not an NS move.
How does dig show which server answers?
dig NS yourdomain.com shows the authoritative NS; dig A shows what those NS return. Dig corrects the wrong-panel habit.
