Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Cloudron DO DNS waiting my.domain

    Support
    dns installation
    3
    11
    524
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      alesnim last edited by girish

      Good day!
      I trying install Cloudron on DO droplet with DO DNS (domain registar Namecheap).
      I am set nameservers and

      host - t NS domainname
      

      works.
      But subdomain my.domain not worked on DO DNS.
      Log from droplet:

      2021-11-05T14:35:54.808Z box:dns/waitfordns isChangeSynced: NS ns3.digitalocean.com (198.41.222.173) errored when resolve domain.xxx (A): Error: queryCname ENODATA domain.xxx
      2021-11-05T14:35:54.809Z box:dns/waitfordns waitForDns: domain.xxx not done ns: ["ns3.digitalocean.com","ns1.digitalocean.com","ns2.digitalocean.com"]
      2021-11-05T14:35:54.809Z box:dns/waitfordns isChangeSynced: NS ns1.digitalocean.com (173.245.58.51) errored when resolve domain.xxx (A): Error: queryCname ENODATA domain.xxx
      2021-11-05T14:35:54.820Z box:dns/waitfordns isChangeSynced: NS ns2.digitalocean.com (173.245.59.41) errored when resolve domain.xxx (A): Error: queryCname ENODATA domain.xxx
      

      How to fix it?

      girish 1 Reply Last reply Reply Quote 0
      • girish
        girish Staff @alesnim last edited by

        @alesnim Can you check the output of host my.domain.com 127.0.0.1 on the server? I think maybe the DNS has not propagated. Did you also try a refresh on the browser? Sometimes things get stuck if browser <-> server connection intermittently broke.

        A 2 Replies Last reply Reply Quote 0
        • A
          alesnim @girish last edited by

          @girish
          host output:
          Using domain server:
          Name: 127.0.0.1
          Address: 127.0.0.1#53
          Aliases:

          Host <domainname> not found: 2(SERVFAIL)

          girish 1 Reply Last reply Reply Quote 0
          • A
            alesnim @girish last edited by

            @girish
            If refresh page, domain setup page displayed "Already setting up or restoring", but main page domain write "Cloudron is offline. Reconnecting"

            girish 1 Reply Last reply Reply Quote 0
            • girish
              girish Staff @alesnim last edited by

              @alesnim said in Cloudron DO DNS waiting my.domain:

              Host <domainname> not found: 2(SERVFAIL)

              Yeah, this is the issue. The DNS has not propagated or there is something wrong with the domain's DNS. Did you just purchase this domain or migrate this domain to DO? If so, sometimes it takes a bit of time for things to sync. While it might work on your local machine, we have to make sure it is propagated before we get certs but Let's Encrypt won't issue certs till DNS is in sync.

              A 1 Reply Last reply Reply Quote 0
              • girish
                girish Staff @alesnim last edited by girish

                @alesnim You can do systemctl restart box and then refresh the browser to start afresh.

                1 Reply Last reply Reply Quote 0
                • A
                  alesnim @girish last edited by alesnim

                  @girish
                  Today I'm bought domain on Namechip and setting nameservers DO. (this guide: https://www.namecheap.com/support/knowledgebase/article.aspx/767/10/how-to-change-dns-for-a-domain/)

                  How to check sync DNS?

                  girish 1 Reply Last reply Reply Quote 0
                  • girish
                    girish Staff @alesnim last edited by

                    @alesnim that's not something in our hands (yours or mine). Please see https://www.namecheap.com/support/knowledgebase/article.aspx/9622/10/dns-propagation-explained/#dnspropagation . nameserver changes take a while to take effect. The 24-48 hours are quite conservative imo, usually it happens in 6 hours for sure. So, I would just wait for some time and check the host command again.

                    A 1 Reply Last reply Reply Quote 0
                    • A
                      alesnim @girish last edited by

                      @girish
                      Oh, thanks) I trying tomorrow again.

                      girish 1 Reply Last reply Reply Quote 0
                      • girish
                        girish Staff @alesnim last edited by

                        @alesnim np, if it doesn't work, you can write to us with your domain name at support@cloudron.io and we can check the DNS status from our networks.

                        1 Reply Last reply Reply Quote 0
                        • d19dotca
                          d19dotca last edited by

                          FWIW, a great DNS tool for checking on DNS propagation progress is here: https://dnschecker.org

                          --
                          Dustin Dauncey
                          www.d19.ca

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post
                          Powered by NodeBB