DNS · Name servers · Resolvers
DNS is three different things.
Who does what, and what we manage.
The public resolver that answers your computers, the internal DNS server of your network, the name servers that answer the world about your domain. Who is European and who is American, where it matters, and the service with which we keep your domain’s zone in order without changing registrar.
Who does what
Resolver, internal DNS, name servers: three answers to three different questions
When people say “DNS” they mix up three things that live in different places, are managed by different people and carry different risks. The resolver answers your devices, the internal DNS knows your network, the name servers tell the world where your mail and your website live. The question “American or European” only makes sense for the first; the question “who can change it” is decisive for the third.
| Role | Who it answers | Examples | Who manages it |
|---|---|---|---|
| Public resolver | Your devices, when they ask “where is this name?”. Outside the office they talk to it directly. | European: DNS4EU (European Union), Quad9 (Switzerland). American: Google, Cloudflare. | You choose it, for free. We set it on the firewall, the internal DNS and Intune profiles. |
| Internal DNS | The names of your network: servers, printers, Active Directory. Everything else is forwarded to the public resolver. | Windows Server with Active Directory, the office firewall. | Us, under the support contract, together with the network logs. |
| Authoritative name servers | The whole world, about your domain: where mail and website live, SPF, DKIM, DMARC, MTA-STS, certificates. | The registrar’s name servers (Aruba, Register.it and the like), Azure DNS, Cloudflare. | Whoever holds the keys to the zone. It is the service on this page. |
Your people’s browsing queries go through the resolver, and they are personal data: that is why a European resolver makes sense, and we cover it on the European DNS page. The records of a public zone, instead, are public by nature: on the name servers what counts is redundancy, the DNSSEC signature and who holds the keys, not the flag.
How our own domains are set up
DNS4EU and Quad9, one primary and one secondary, set on the firewall, the internal DNS and Intune profiles.
anycast on four different top-level domains, replicated worldwide: if one disappears, the others answer.
DNSSEC active with the DS record at the registry: the chain is validated by DNS4EU, Quad9, Google and Cloudflare.
we have been managing domains and DNS zones for Italian businesses.
What we manage
European resolver on your devices
Internal DNS of the network
Domain zone on redundant name servers
Who can edit the zone
DNSSEC, zone side and resolver side
Records, monitoring, evidence
The whole DNS topic
Related tools, pages and articles
DNS runs through half the site: the tools to look inside a domain, the service pages that live in the zone’s records and the articles where we explained the single pieces.
Free tools
Related pages
Frequently asked questions on DNS, name servers and resolvers
The questions we get when a customer finds out that their domain sits on the registrar’s default name servers, with the password in a drawer.
The name server is the server that answers the whole world about your domain: when someone writes to name@yourcompany.com or opens www.yourcompany.com, their provider asks the domain’s name servers where the mail and the website live. The zone records hold MX, SPF, DKIM, DMARC, MTA-STS and the website addresses: whoever can edit the zone can hijack the company’s mail and website without touching a single server. That is why the zone must be treated as a critical system, with named accounts, MFA and a change history.
They are the three halves of DNS. The public resolver answers your devices when they ask “where is this name?”: DNS4EU and Quad9 are European, Google and Cloudflare American, and you choose it, for free. The internal DNS is the server of your network, usually Windows Server with Active Directory or the firewall: it knows the internal names and forwards the rest to the public resolver. The authoritative DNS is your domain’s name servers, which answer the world about mail and website. Resolver and internal DNS are set up under the support contract; the authoritative zone is the service on this page.
It matters on the resolver, because that is where your people’s browsing queries go, which is personal data: a European resolver such as DNS4EU, a European Union initiative, or Quad9, a Swiss foundation, resolves within the European legal space and costs nothing. On the domain’s name servers the flag matters less, because the records of a public zone are public by nature: what counts there is redundancy, the DNSSEC signature and who holds the keys to edit the zone, under which account and which contract.
No. The domain stays registered where it is: only the NS records at the registrar change, telling the world which name servers answer for the domain. We copy the zone to the new name servers, compare it record by record, lower the TTLs in advance and check from several resolvers with DIG before and after the switch. If the domain is new we register it with the extension you need.
On Azure DNS: four anycast name servers on four different top-level domains (.com, .net, .org, .info), replicated worldwide, with DNSSEC. It is the same infrastructure our own domains atworkstudio.it and atws.cloud run on, with signed zones validated by the public resolvers. Azure DNS is a global service, not a regional one: for a public zone that is a merit, because answers come from the node closest to whoever asks. Control of the zone stays in our tenant, with named accounts, MFA and a change log.
That is exactly why you need it. DNS4EU, Quad9 and the other resolvers that validate DNSSEC can only notice a tampered answer if the domain’s zone is signed and the DS record is published at the registry. Without a signature, validation has nothing to check and the resolver accepts any answer. We sign the zone, publish the DS and check the chain with DIG; we have been doing it on our own domains for a long time.
It is the worst case for a domain: whoever gets into the zone can move the mail to their own server, publish a fake website or let the domain expire. The countermeasures are well known and we apply all of them: registrar lock and MFA on the registrar account, named accounts with separate roles on the zone, periodic zone export as a backup, monitoring of changes and expiry dates, a documented recovery procedure. It is part of the support contract, not a separate price list.
No. The filter on malicious domains is public and free today: DNS4EU in its protective variant and Quad9 do it with the threat intelligence of the European CERTs, and for devices outside the office category blocking is done by the EDR and Intune profiles. The work, and therefore the service, lies in the domain’s authoritative zone and in the network’s internal DNS: redundant name servers, DNSSEC, controlled access, correct and monitored mail and website records. AtWorkStudio is certified ISO/IEC 27001, 27017, 27018 and ISO 9001.
Do you know who can edit your domain’s DNS zone?
Look with DIG at which name servers answer for your domain and whether the zone is signed; then write to us and we will tell you where your zone lives, who can touch it and what would change.