Glossary
DNS hijacking
Definition
DNS hijacking changes how internet names are resolved so traffic intended for a legitimate service goes somewhere an attacker controls.
Attackers may change domain records, compromise DNS infrastructure or alter a device's DNS settings. Website and email traffic can both be affected.
A customer may include “DNS hijacking” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.
DNS hijacking interferes with the system that translates internet names into the addresses used to reach services. An attacker changes the answer or the settings that produce it, directing traffic away from the intended destination.
It can involve stolen access to a domain or DNS provider, compromised infrastructure or changed settings on a device. The impact depends on what is altered. A website may lead to an imitation page, while changed mail-routing records can affect email delivery. Typing the expected domain name is not sufficient if its underlying records have been changed.
Hypothetical example: a small retailer loses control of its domain-provider account. The attacker changes the website records to point to a false login page while the retailer's actual web server remains intact. Repairing the web server would miss the cause.
Protect domain administration accounts and retain a record of who controls DNS changes. Protect registrar and DNS accounts with MFA, narrow administrator access and log changes. If records change unexpectedly, verify them through a trusted registrar route, restore known-good settings and investigate the compromised account or system. After a suspected hijack, review affected records and investigate the account or infrastructure compromise that enabled it. DNS security measures have different roles; no single label establishes that every route for changing records is protected.
Sources: ICANN alert on attacks against DNS; CISA guidance on DNS tampering.