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


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. AAAA dns error – how to solve?

AAAA dns error – how to solve?

Scheduled Pinned Locked Moved Solved Support
dns setup
11 Posts 3 Posters 763 Views 3 Watching
  • 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.
  • nebulonN Offline
    nebulonN Offline
    nebulon
    Staff
    wrote on last edited by
    #2

    Which DNS backend provider are you using for that domain? Also do you see more errors in the app logs?

    Cloudron will retry until all nameservers are in sync. Do all of them have the expected AAAA record?

    1 Reply Last reply
    0
    • nebulonN nebulon marked this topic as a question on
    • T Offline
      T Offline
      thoresson
      wrote on last edited by
      #3

      It's a Swedish one, Oderland, configured using the Wildcard option. And yes, dns1/2/3.oderland.com all have the AAAA record.

      1 Reply Last reply
      0
      • nebulonN Offline
        nebulonN Offline
        nebulon
        Staff
        wrote on last edited by
        #4

        Hm, so all Cloudron will do here is to check all nameservers directly for the records. So are the records also resolving fine from the server itself via SSH?

        You can check with:
        host -t AAAA <app.yourdomain.com> <nameserver1/2/3>

        1 Reply Last reply
        0
        • T Offline
          T Offline
          thoresson
          wrote on last edited by
          #5

          Hmm, your terminal command got me thinking: I'm trying to install apps under my Cloudron's primary domain. For primary.tld I've AAAA records configured at my registrar. I thought that Cloudron managed the AAAA records for any subdomains thanks to this setup? But should I add the AAAA record for linkwarden.primary.tld at my registrar as well?

          I haven't done that for any of the already working apps, and they run as expected.

          1 Reply Last reply
          0
          • nebulonN Offline
            nebulonN Offline
            nebulon
            Staff
            wrote on last edited by
            #6

            Since Oderland is not a supported API by Cloudron, you have to setup all records manually. If you use the wildcard, then this works for all subdomains, but not the main domain. DNS wildcards for the primary.tld do not exist.

            1 Reply Last reply
            1
            • T Offline
              T Offline
              thoresson
              wrote on last edited by
              #7

              Ah, I see! Thanks!

              But I also noticed that it worked if I disabled IPv6 even for the primary domain. Why is that?

              1 Reply Last reply
              0
              • nebulonN Offline
                nebulonN Offline
                nebulon
                Staff
                wrote on last edited by
                #8

                Cloudron will then skip the check if it is disabled.

                1 Reply Last reply
                0
                • T Offline
                  T Offline
                  thoresson
                  wrote on last edited by
                  #9

                  So it's IPv6 entries that are handled by Oderland, but Cloudron takes care of the IPv4?

                  1 Reply Last reply
                  0
                  • nebulonN Offline
                    nebulonN Offline
                    nebulon
                    Staff
                    wrote on last edited by
                    #10

                    Not really, Cloudron can't change records unless the provider has an API which is integrated with Cloudron and Oderland is not yet added. So in such cases you can either use wildcard or manual provider, which means you have to setup the records manually (or for subdomains the single wildcard DNS record works). A or/and AAAA are handled the same way.

                    1 Reply Last reply
                    0
                    • jdaviescoatesJ Offline
                      jdaviescoatesJ Offline
                      jdaviescoates
                      wrote on last edited by
                      #11

                      Recently when I was installing a new Cloudron and using Wildcards it was stuck on waiting for dns propagation until I created both A and AAAA entries

                      I use Cloudron with Gandi & Hetzner

                      1 Reply Last reply
                      1
                      • J joseph has marked this topic as solved on
                      Reply
                      • Reply as topic
                      Log in to reply
                      • Oldest to Newest
                      • Newest to Oldest
                      • Most Votes


                      • Login

                      • Don't have an account? Register

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • Bookmarks
                      • Search