From f1fb4624b461420a92ada77fd953fdfdf5fbb311 Mon Sep 17 00:00:00 2001 From: Anon Date: Fri, 21 Oct 2022 14:15:11 -0700 Subject: [PATCH] Updated docs since cloudflare will no longer set an A record to 1.1.1.1 --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index f87f5da..33728ac 100644 --- a/README.md +++ b/README.md @@ -54,9 +54,10 @@ Next you need to login to your Cloudflare account and generate the API tokens fo - Copy and paste the A record id to 'cf_record_id' - Once you save the config file, the script will not print out all of the information it did in the previous step. Running the bot without the 'cf_record_id' set is equivilent to running it with `./run.sh --get-record-ids` - Save and close the file. -- To make sure everything worked correctly, you can manually update your A record to a random IP address `./run.sh --set 1.1.1.1` - - FYI 1.1.1.1 is the IP address for Cloudflares DNS servers +- To make sure everything worked correctly, you can manually update your A record to a random IP address `./run.sh --set 95.217.163.246` + - The address used in the example above is for archlinux.org - Your site should become inaccessible and you should see the change reflected in the A record of your domain in your Cloudflare account. + - To see if the changes took effect in the terminal you can run `./run.sh --get-record-ids`, and look for the address. - Run `./run.sh` to change it back. It should auto detect your web-facing IP and update the A record accordingly. ## Automate DynamicCloudflareDNS