DNS redirection is the practice of sending a domain name lookup to a different resolver or answering it with a different address than expected. It is used for traffic steering, filtering, captive portals, or attack paths such as domain hijacking and phishing.
How DNS redirection works
DNS redirection changes where a name resolution request is answered, so the client receives a different resolver response or destination than it expected. That can happen at the resolver layer, through local network control, or by manipulating the path between the client and the name service. The mechanism is simple, but the security consequences depend on who controls the lookup and what they can return.
In legitimate use, redirection is part of traffic steering and access control, such as sending users to a captive portal, applying filtering, or directing them to a local service. In hostile use, the same trust in name resolution becomes a weak point because users and applications often assume DNS answers are authoritative and stable.
Why DNS redirection is security-sensitive
DNS is an enabling layer for almost every internet-facing service, so redirection can alter where users connect without changing the URL they typed. That makes it attractive for phishing, domain hijacking, and traffic interception, because the visible domain can remain familiar while the underlying destination changes.
When the wrong answer is returned, the impact is not limited to one lookup. A redirected response can steer browsers, APIs, mail systems, or update mechanisms toward hostile infrastructure, which turns a naming problem into a trust and access problem.
Common legitimate and malicious uses
On the defensive and operational side, DNS redirection is used to implement captive portals, block known-bad destinations, or direct clients to region-specific or internal services. These uses rely on administrative control of name resolution and are often tied to policy enforcement rather than application changes.
On the malicious side, attackers may tamper with resolver responses, compromise authoritative DNS control, or abuse a trusted network position to send users to a lookalike destination. Even when the original domain remains visible in a browser, the resolved address can point somewhere else entirely, which can enable credential theft, malware delivery, or session capture.
How organisations reduce exposure
Exposure starts with understanding which resolvers, forwarders, and authoritative zones are trusted, and whether those paths are protected from tampering. Organisations should treat DNS infrastructure as a security dependency, especially for externally exposed domains and high-value internal services.
Good DNS hygiene includes monitoring for unexpected changes in records, registrar settings, and resolver behaviour, then validating that clients are using approved name-resolution paths. Where policy-based redirection is intentional, the design should be explicit and documented so that legitimate steering is not mistaken for compromise.
For a general control baseline, see IANA for the registries that underpin internet naming and numbering, and use authoritative DNS governance processes to keep changes auditable and deliberate.
Detection and recovery after suspicious redirection
Suspicious DNS redirection is often discovered when users reach the wrong site, certificates stop matching expectations, or traffic is suddenly diverted to unfamiliar infrastructure. Investigation should compare observed answers against known-good resolver behaviour and confirm whether the change is local, network-wide, or tied to a registrar or authoritative-zone event.
If compromise is suspected, post-incident review should include resolver logs, zone changes, registrar access, and any downstream authentication activity that may have followed the redirection. The practical question is not only whether the name was altered, but whether the redirected path was used to harvest credentials, tokens, or other session material.
Where name resolution feeds critical services, align response with NIST Cybersecurity Framework 2.0 to structure identification, protection, detection, response, and recovery around the DNS dependency itself.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack and risk surface, while NIST CSF 2.0, CIS Controls v8 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | DE.CM-01 — Monitoring for Anomalies and Events | DNS redirection is detected through unexpected resolution or traffic destination changes. |
| PR.DS-02 — Data-in-Transit is Protected | DNS redirection can divert traffic before transport protections are applied. | |
| Recommendation — Monitor DNS and destination anomalies to spot unexpected redirection quickly. Protect name-resolution and downstream traffic paths against tampering and diversion. | ||
| MITRE ATT&CK | T1568 — Dynamic Resolution | DNS redirection commonly relies on changing resolution paths or answers. |
| Recommendation — Hunt for resolution changes and correlate them with suspicious destination shifts. | ||
| CIS Controls v8 | CIS-12 — Network Infrastructure Management | DNS redirection depends on trusted network and DNS infrastructure management. |
| Recommendation — Harden and monitor DNS infrastructure and related configuration paths. | ||
| NIST SP 800-53 Rev 5 | SC-20 — Secure Name / Address Resolution Service (Authoritative Source or Cache Poisoning) | This control directly addresses secure DNS resolution and poisoning risk. |
| Recommendation — Use secure name resolution controls to reduce poisoning and redirection risk. | ||
Related resources from NHI Mgmt Group
- Why does weak DNS governance increase the risk of redirection, interception, and outage?
- What breaks when internal DNS names are preserved but access governance is not updated?
- Why do DNS and edge configuration changes create IAM and security risk?
- How can security teams detect malicious update redirection in practice?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org