# the Cloud DNS zone to update
DCDNS_ZONE=**_MYHOST_**

https://console.cloud.google.com/net-services/dns/zones/**_MYHOST_**/details?project=myexampleproject

is it a proper mapping?

the DNS hostname to update, e.g. your.host.com

DCDNS_HOST=dynamichost.domain.com

https://console.cloud.google.com/net-services/dns/zones/**_MYHOST_**/rrsets/your.host.com./A/view?project=myexampleproject

is it a proper mapping?

the URL of your deployed cloud function

DCDNS_FUNCTION_URL=https://us-central1-myexampleproject .cloudfunctions.net/updateHost
cant figure out where to find "us-central1" i have got
https://console.cloud.google.com/compute/instances?project=myexampleproject => Zone = "northamerica-northeast2-a" is it the same ?

It could be possible that for some reason the ipify API returns some incorrect data, like returning an IPv4 address from https://api6.ipify.org

We should check the format of the value returned, and ignore if it isn't correct.

If the request to ipify fails for any reason, it raises an error, which causes the main loop to exit, and systemd is responsible for restarting it.

It would be much better if there was at least an attempt to retry the request before failing.

logs entries like

DEBUG    urllib3.connectionpool    Starting new HTTPS connection (1): api.ipify.org

then nothing

In install.sh the line:

echo "Edit /etc/dynamic_cloud_dns_client_$1 and then run systemctl enable dynamic_cloud_dns_client@$1.service"

should have dashes rather than underscores for "dynamic-cloud-dns-client@$1.service".

Otherwise when someone copies and pastes the message to enable the service they naturally get an error.