DNS management for example.com:
| Type | Name | Content | Proxy status | TTL |
|---|---|---|---|---|
| A | blog | 192.0.2.1 | Proxied | Auto |
| A | blog | 192.0.2.5 | DNS only | Auto |
In this example, all traffic intended for blog.example.com will be treated as if both records were proxied.
The sections below describe specific behaviors and expected outcomes when you have DNS records set to proxied. For further context, refer to About proxying.
By default, all proxied records have a time to live (TTL) of Auto, which is set to 300 seconds.
Since only IP resolution records can be proxied, this setting ensures that queries to your domain name resolve fairly quickly. This setting also means that any changes to proxied A, AAAA, or CNAME records will take place within five minutes or less.
If you have multiple A or AAAA records on the same name and at least one of them is proxied, Cloudflare will treat all A or AAAA records on this name as being proxied.
Example
DNS management for example.com:
| Type | Name | Content | Proxy status | TTL |
|---|---|---|---|---|
| A | blog | 192.0.2.1 | Proxied | Auto |
| A | blog | 192.0.2.5 | DNS only | Auto |
In this example, all traffic intended for blog.example.com will be treated as if both records were proxied.
For proxied records, if your domain has HTTP/2 or HTTP/3 enabled, Cloudflare automatically generates corresponding HTTPS Service (HTTPS) records on the fly. HTTPS records allow you to provide a client with information about how it should connect to a server upfront, without the need of an initial plaintext HTTP connection.