Hyperlint Automation: Broken Link Fixes #20345
Conversation
hyperlint-ai
bot
requested review from
a team and
RebeccaTamachiro
as code owners
![hyperlint-ai[bot]](https://avatars.githubusercontent.com/in/718456?s=60&v=4){kind=small}
| <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. |
There was a problem hiding this comment.
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
| <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. |
There was a problem hiding this comment.
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
|
Howdy and thanks for contributing to our repo. We review new, external PRs within 2 weeks. If it's been longer than then without any movement, tag the PR Assignees in a comment. |
|
Preview URL: https://421f5ad7.preview.developers.cloudflare.com Files with changes (up to 15)
|
|
Same as #20210 |
1 participant
Broken Link Fix Proposal(s)
The goal of this pull request is to fix broken links in the documentation.
Proposing changes to the following files:
to edit this branch locally, run:
🗣️Leave us feedback
This pull request is part of a series of Hyperlint Automations to ease the burden of maintaining documentation.
We'll be introducing this automation, and others, over the coming months. These automations will always open pull requests(or issues) prior to making changes.
If this is not the change you want, please close this pull request and let us know what you'd like to see.
This feature may introduce erroneous changes (although we work hard to make sure that doesn't happen). Please review the changes before merging.
❌ Limitations:
At this time, Hyperlint can't respond to pull requests or issues.
📩 Need Help?
Please reach out to support with any requests, questions, or concerns.