You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cloudflare uses these new HTTPS records to speed up TLS, and at least chrome based browsers are starting to use them.
In my particular use-case I override a specific subdomain for local only use local.mydomain.tld:
Overrided A and AAAA records point to a local IP on my network. This has been working fine for years.
Now the browser is asking for HTTPS record instead, which gets forwarded to Cloudflare DNS upstream, and returns the public, external IP address, breaking local connections intermittently.
The text was updated successfully, but these errors were encountered:
Cloudflare uses these new HTTPS records to speed up TLS, and at least chrome based browsers are starting to use them.
In my particular use-case I override a specific subdomain for local only use
local.mydomain.tld
:Overrided A and AAAA records point to a local IP on my network. This has been working fine for years.
Now the browser is asking for HTTPS record instead, which gets forwarded to Cloudflare DNS upstream, and returns the public, external IP address, breaking local connections intermittently.
The text was updated successfully, but these errors were encountered: