Domain not resolving on Google Cloud DNS

Admin 1
Viewed 1175

Been trying to setup a new domain on Google Cloud DNS and Google Domains, but it just wont resolve.

I'm a bit of a newby to this. Domain is primer.finance. I setup the zone in Cloud DNS, added the records to Google Domains, but fails to resolve anyway.

Checked on https://dnssec-analyzer.verisignlabs.com/primer.finance# and seems to be error free too

google-cloud-dns google-cloud-platform dns
1 Answers

I'm able to open http://primer.finance/ in my web browser. There's no issue related to DNS configuration. Have a look at some checks below:

  1. configured DNS servers for domain at the registrar side (Google Domains):

    $ whois primer.finance | grep "Name Server"
Name Server: ns-cloud-e1.googledomains.com
Name Server: ns-cloud-e2.googledomains.com
Name Server: ns-cloud-e3.googledomains.com
Name Server: ns-cloud-e4.googledomains.com

    I assume that records above are correct because your website is reachable.

  2. NS records for domain requested from 8.8.8.8 and 1.1.1.1:

    $ dig NS primer.finance @8.8.8.8
...
;; ANSWER SECTION:
primer.finance.         21599   IN      NS      ns-cloud-e1.googledomains.com.
primer.finance.         21599   IN      NS      ns-cloud-e2.googledomains.com.
primer.finance.         21599   IN      NS      ns-cloud-e3.googledomains.com.
primer.finance.         21599   IN      NS      ns-cloud-e4.googledomains.com.
...

$ dig NS primer.finance @1.1.1.1
...
;; ANSWER SECTION:
primer.finance.         21600   IN      NS      ns-cloud-e1.googledomains.com.
primer.finance.         21600   IN      NS      ns-cloud-e2.googledomains.com.
primer.finance.         21600   IN      NS      ns-cloud-e3.googledomains.com.
primer.finance.         21600   IN      NS      ns-cloud-e4.googledomains.com.
...

  3. domain name resolve requested from 8.8.8.8 and 1.1.1.1:

    $ dig A primer.finance @8.8.8.8
...
;; ANSWER SECTION:
primer.finance.         299     IN      A       35.228.29.215
...

$ dig A primer.finance @1.1.1.1
...
;; ANSWER SECTION:
primer.finance.         300     IN      A       35.228.29.215
...

$ dig A www.primer.finance @8.8.8.8
...
;; ANSWER SECTION:
www.primer.finance.     299     IN      CNAME   primer.finance.
primer.finance.         299     IN      A       35.228.29.215
...

$ dig A www.primer.finance @1.1.1.1
...
;; ANSWER SECTION:
www.primer.finance.     300     IN      CNAME   primer.finance.
primer.finance.         300     IN      A       35.228.29.215
...

  4. web server response:

    $ curl -I http://primer.finance
HTTP/1.1 200 OK
Date: Fri, 12 Jun 2020 11:01:45 GMT
Server: Apache
X-Frame-Options: SAMEORIGIN
Cache-Control: max-age=0, no-cache
Content-Type: text/html; charset=utf-8

  5. domain propagation at dnsmap.io, dnschecker.org whatsmydns.net also looks good.

The only problem I found is wrong SSL certificate:

...
Issued To:

Common Name (CN)    www.example.com
Organization (O)    Bitnami
Organizational Unit (OU)    Certificate generated at boot time

Issued By:
Common Name (CN)    www.example.com
Organization (O)    Bitnami
Organizational Unit (OU)    Certificate generated at boot time
....

You should reply this test certificate with the proper one that was issued for your domain. Also, something wrong with switching between pages of your site: at some pages domain name was replaced by IP.

Your issue could be related to domain propagation time (accordingly to the documentation it could take up to 48 hours after last change and it'll be self resolved) or local caches on your computer (try to check your web site from other computer or phone and via mobile Internet if possible).

user_124287940
Related