Waiting for DNS propagation
-
@L3oN oh! could it be that no A record exists for the main domain? If so just create one with an empty subdomain field through Cloudflare. Cloudron only creates this if an app is installed on that or if any app has an alias/redirect configured for the main domain.
-
@L3oN so things look fine from that perspective then. Can you try to run
dig @8.8.8.8 domain.com
on the server to get an answer from a different source?Also if you want, send your actual domain to support@cloudron.io so we can also run some tests against this.
-
; <<>> DiG 9.16.1-Ubuntu <<>> @8.8.8.8 webxxx
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20348
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;webxxx. IN A;; ANSWER SECTION:
xxx. 300 IN A 65.108.xxx;; Query time: 212 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue May 24 18:44:51 UTC 2022
;; MSG SIZE rcvd: 56i send you domain on PM
-
@L3oN I wonder if this is something DNSSEC related. Can you please try https://docs.cloudron.io/troubleshooting/#dns ? You can also forward everything to 8.8.8.8 (the 1.2.3.4 in that example), to see if it gets things moving ahead.
-