-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Hyperlint Automation: Broken Link Fixes #20345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -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. | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This page: https://developers.cloudflare.com/dns/proxy-status/limitations/ By looking at the page: https://developers.cloudflare.com/dns/proxy-status/limitations/ |
||
|
|
||
| If this warning is still present after 24 hours, refer to [Troubleshooting](/dns/troubleshooting/). | ||
|
|
||
|
|
||
There was a problem hiding this comment.
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-recordsdoes 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