Service definition and covered entity
A business using DNS for its own website does not automatically become a DNS service provider. Identify which legal entity delivers recursive or authoritative name resolution to internet users or third parties, its infrastructure, customers and external dependencies. Keep the NIS2 classification assessment separate from the service-definition question.
Applying the detailed Annex requirements
The Annex to Regulation 2024/2690 includes risk-management policies, incident handling, continuity, supplier assurance, system security and access controls. Map each applicable requirement to actual operating controls and evidence. Where a qualified provision is not applied, record comprehensible reasons rather than treating flexibility as a general exemption.
Operational security and resilience
DNS operators should protect administrative access, zone integrity, configuration changes and the availability of their resolution infrastructure. Examine upstream services, network dependencies and denial-of-service resilience. Recovery exercises should cover both inadvertent misconfiguration and deliberate compromise, with lessons linked to documented remediation.
Incident significance under the regulation
Article 5 provides DNS-specific significant-incident conditions. Assess them alongside the common Article 3 criteria and repeated-incident rules in Article 4. Retain evidence of affected users, the domains or services involved, timing, geographic impact and relevant integrity or confidentiality consequences. Internal priority labels cannot replace the legal significance tests.
Governance, evidence and regulatory coordination
Identify the competent authority and applicable Article 23 incident notification route. Align incident triage, emergency contacts and management oversight with the actual services delivered. Refresh the assessment when the provider changes infrastructure, outsources critical functions or expands its scope.
Austria, NISG 2026 and .at domain holder data
Austria implemented NIS2 through the Network and Information Systems Security Act 2026, NISG 2026, passed on 12 December 2025 and in force from 1 October 2026. For domain names, the relevant duty is Article 28 of NIS2, which requires registries, registrars and internet service providers to keep domain holder data complete and accurate. For .at, the registry nic.at now requires a telephone number in addition to name, postal address and email address, for new registrations and for existing holders who had not supplied one.
Holders must cooperate if nic.at asks to verify their data, and verification is risk based, so not every holder is asked. For legal entities, holder name, address, email and telephone are now public in WHOIS, and nic.at recommends a general office address and switchboard number rather than a named person's direct details. For individuals, personal details are not published. If a holder does not complete a verification request in time, the domain can be placed on serverHold and removed from DNS.
Points of clarification
Does this regulation apply to every NIS2 entity?
No. Its Article 1 identifies specific provider categories.
Does it replace the NIS2 Directive?
No. The Directive and the implementing regulation serve different, complementary roles.