Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/content/docs/dns/proxy-status/limitations.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ To proxy HTTP/HTTPS traffic on [non-standard ports](/fundamentals/reference/netw

<Render file="onboard-warning" product="dns" />

This means that DNS records — even those set to [proxy traffic through Cloudflare](#proxied-records) — will be [DNS-only](/dns/proxy-status/#dns-only-records) until your zone has been activated and any requests to your DNS records will return your origin server's IP address.
This means that DNS records — even those set to [proxy traffic through Cloudflare](#proxy-eligibility) — will be [DNS-only](/dns/proxy-status/#dns-only-records) until your zone has been activated and any requests to your DNS records will return your origin server's IP address.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This page: https://developers.cloudflare.com/dns/proxy-status/limitations/
has a broken internal link to: https://developers.cloudflare.com/dns/proxy-status/limitations/.
The fragment proxied-records does not exist.

By looking at the page: https://developers.cloudflare.com/dns/proxy-status/limitations/
The best fragment to use seems to be: #proxy-eligibility


If this warning is still present after 24 hours, refer to [Troubleshooting](/dns/troubleshooting/).

Expand Down
2 changes: 1 addition & 1 deletion src/content/partials/dns/limitations.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ To proxy `HTTP/HTTPS` traffic on [non-standard ports](/fundamentals/reference/ne

<Render file="onboard-warning" product="dns" /> <br/>

This means that DNS records — even those set to [proxy traffic through Cloudflare](#proxied-records) — will be [DNS-only](/dns/proxy-status/#dns-only-records) until your zone has been activated and any requests to your DNS records will return your origin server's IP address.
This means that DNS records — even those set to [proxy traffic through Cloudflare](#proxy-eligibility) — will be [DNS-only](/dns/proxy-status/#dns-only-records) until your zone has been activated and any requests to your DNS records will return your origin server's IP address.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This page: https://developers.cloudflare.com/dns/proxy-status/limitations/
has a broken internal link to: https://developers.cloudflare.com/dns/proxy-status/limitations/.
The fragment proxied-records does not exist.

By looking at the page: https://developers.cloudflare.com/dns/proxy-status/limitations/
The best fragment to use seems to be: #proxy-eligibility


If this warning is still present after 24 hours, refer to [Troubleshooting](/dns/troubleshooting/).

Expand Down