Confusion about what 'authoritative' and 'recursive' DNS do and which you need
Authoritative DNS answers for your zone (you manage vectel.nl). Recursive DNS is the middleman that fetches and caches answers for a client (Google 8.8.8.8, Cloudflare 1.1.1.1, your ISP, your router). You need both, but you manage them separately.
Try this first
- 1For your domain you need an authoritative provider (TransIP, Cloudflare, Versio, Route 53). That is where you edit records.
- 2For workstation clients you use a recursive resolver. Often the ISP/router default, but 1.1.1.1 or 9.9.9.9 are usually faster and more privacy-friendly.
- 3In an office with AD: let clients use the Domain Controllers as recursive (they forward to public resolvers), not 8.8.8.8 directly.
- 4Never open a recursive resolver to the public internet. That is an open relay for DNS amplification attacks.
- 5When you wonder where a problem lives: dig @authoritative-server versus dig @public-resolver, the difference tells you whether cache or origin is at fault.
When to bring us in
If you have a mix of AD, on-prem resolvers and cloud DNS and records get tangled, we can lay out the architecture again.
See also
- Domain expires tomorrow and nobody saw the emailAn expired domain doesn't transfer instantly. There's a redemption window, but you pay extra.
- Unsure whether to enable auto-renewDisabling auto-renew only makes sense for domains you'll truly drop. For anything live, just keep it on.
- New registrar asks for auth code, can't find itEPP code or transfer code is the password to move a domain from registrar A to B.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.