fix: correct proxied DNS records link path

Author: dmmulroy

src/content/docs/ddos-protection/best-practices/proactive-defense.mdx

@@ -38,7 +38,7 @@ In addition to the steps for all customers, Cloudflare Magic Transit customers s
 
 Cloudflare edge protection is only effective if attackers cannot bypass it by reaching your origin directly.
 
-1. Verify that all hostnames serving traffic are [proxied (orange-clouded)](/dns/manage-dns-records/reference/proxied-dns-records/) through Cloudflare.
+1. Verify that all hostnames serving traffic are [proxied (orange-clouded)](/dns/proxy-status/) through Cloudflare.
 2. Check whether your origin IP is reachable from non-Cloudflare sources. If it is, attackers can send traffic directly to the origin and bypass all Cloudflare protections.
 3. Before restricting access, identify any non-Cloudflare sources that must still reach your origin (for example, third-party vendors, monitoring services, CI/CD pipelines, or partner integrations).
 4. Restrict your origin firewall to accept HTTP/HTTPS traffic only from [Cloudflare IP ranges](https://www.cloudflare.com/ips/) and any explicitly trusted IPs you identified.
@@ -53,7 +53,7 @@ If you are experiencing a DDoS attack or suspect elevated attack traffic, use th
 ### Quick triage questions
 
 1. Are you experiencing service impact (timeouts, 5xx errors) or mainly observing high traffic volume in logs and analytics?
-2. Which hostname(s) are affected, and are they [proxied (orange-clouded)](/dns/manage-dns-records/reference/proxied-dns-records/)?
+2. Which hostname(s) are affected, and are they [proxied (orange-clouded)](/dns/proxy-status/)?
 3. What is the timeframe that should be investigated? Provide times in UTC.
 
 ### If your site or origin is impacted