I tried to recreate your use case and had one of my VM's assign a static public IP.
When I checked your domain dig
command was providing correct IP, which meant you had A record set up OK.
$ dig archents.app
; <<>> DiG 9.11.5-P4-5.1+build1-Debian <<>> archents.app
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24202
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;archents.app. IN A
;; ANSWER SECTION:
archents.app. 299 IN A 35.237.246.77
;; Query time: 41 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jan 07 10:03:46 CET 2020
;; MSG SIZE rcvd: 57
So - to be sure everything works (in my case) I followed those steps:
- reserved external regional static address and attached it to my test VM
- created a public zone in cloud DNS (in your case put
archents.app
in the "DNS name" field.
- added a record set to my zone (just selected A Record Type, set TTL to 1 minute (for convinience) and put my IP in the "IPv4 Address".
Please have a look into an official documentation how to update a DNS record sets.
After a few minutes everything started working as expected.