From 02e3f89d24898cda79a855bc6bca7b70e27bec3c Mon Sep 17 00:00:00 2001 From: favonia Date: Sun, 27 Aug 2023 23:15:26 -0500 Subject: [PATCH] docs(README): update wording --- README.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.markdown b/README.markdown index 0717c7e2..d3a9316e 100644 --- a/README.markdown +++ b/README.markdown @@ -233,7 +233,7 @@ _(Click to expand the following items.)_ > - `none`\ > Stop the DNS updating completely. Existing DNS records will not be removed. > - `url:URL` (🧪 experimental)\ -> Fetch the content at a URL via the HTTP(S) protocol as the IP address. The provider format is `url:` followed by the URL. For example, `IP4_PROVIDER=url:https://api4.ipify.org` will fetch the IPv4 addresses from , a server maintained by [ipify](https://www.ipify.org). ⚠️ Currently, the updater does not force the HTTP(S) connections to use IPv4 or IPv6 when retrieving the content at the URL, and thus the service must restrict its access to the correct network (IPv4 or IPv6) or return the correct address even when the wrong network is used. Currently, there is no elegant way to force IPv4 or IPv6 using the Go standard library; please [open a GitHub issue](https://github.com/favonia/cloudflare-ddns/issues/new) if you have a use case. +> Fetch the content at a URL via the HTTP(S) protocol as the IP address. The provider format is `url:` followed by the URL. For example, `IP4_PROVIDER=url:https://api4.ipify.org` will fetch the IPv4 addresses from , a server maintained by [ipify](https://www.ipify.org). ⚠️ Currently, the updater does not force the HTTP(S) connections to use IPv4 or IPv6 when retrieving the content at the URL, and thus the service must restrict its access to the correct network (IPv4 or IPv6) or return the correct address even when the wrong network is used. The reason is that there is no elegant way to force IPv4 or IPv6 using the Go standard library; please [open a GitHub issue](https://github.com/favonia/cloudflare-ddns/issues/new) if you have a use case. > > The option `IP4_PROVIDER` is governing IPv4 addresses and `A`-type records, while the option `IP6_PROVIDER` is governing IPv6 addresses and `AAAA`-type records. The two options act independently of each other; that is, you can specify different address providers for IPv4 and IPv6. >