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. queryNs ENODATA <my domain>

queryNs ENODATA <my domain>

Scheduled Pinned Locked Moved Solved Support
dnsno-ipqueryns enodatadomain setup
8 Posts 4 Posters 2.3k Views 4 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.
    • R Offline
      R Offline
      RichardJActon
      wrote on last edited by
      #1

      Hi I'm setting up cloudron and i'm having some trouble with my domain setup.
      I'm using wildcard dns and a domain from the provider no-ip where I have setup a wildcard *.<my domain> domain, but i'm getting the error in the title: queryNs ENODATA. Any suggestions for how to debug this would be appreciated.

      1 Reply Last reply
      1
      • girishG Do not disturb
        girishG Do not disturb
        girish
        Staff
        wrote on last edited by
        #2

        @RichardJActon If it's a brand new domain, it could be that the DNS has not propagated yet. Or is this a subdomain of an existing domain (for example, foo.ddns.net style)?

        1 Reply Last reply
        0
        • R Offline
          R Offline
          RichardJActon
          wrote on last edited by
          #3

          It is a subdomain of the form foo.ddns.net, i've add *.foo.dns.net. I think the domain should have propagated by now as it sent me to the webpage that I used to host there before I remapped ports 80 and 443 to the machine i'm installing cloudron on.

          1 Reply Last reply
          0
          • girishG Do not disturb
            girishG Do not disturb
            girish
            Staff
            wrote on last edited by girish
            #4

            @RichardJActon In the advanced section of the domain setup page, put ddns.net as the zone name. That should make it work. Note that Let's Encrypt cert will most likely not work because LE has a limit based on the top level domain. Cloudron will automatically use a self-signed certificate in this case. If this happens, just accept the self-signed cert and you should see the admin creation page.

            If you are curious about the zone name: Cloudron uses the public suffix list to get the top level domain of a domain and use that as the zone name. Domains like ddns.net are "special" and they will return foo.ddns.net as the top level domain. So, Cloudron will incorrectly assume that foo.ddns.net is the zone name.

            1 Reply Last reply
            0
            • R Offline
              R Offline
              RichardJActon
              wrote on last edited by
              #5

              Ah seems to be working now thanks - I had added my full domain foo.ddns.net to the zone name field initially as It autofilled ddns.net and I thought that cloundron might then try to generate subdomains with the foo part missing e.g. my.ddns.net which wouldn't work but apparently not. Thanks for the Help!

              1 Reply Last reply
              0
              • J Offline
                J Offline
                jayonrails
                translator
                wrote on last edited by
                #6

                I have the same problem with adding a "two-words.com" domain to my Cloudron; the DNS zone is with Hetzner DNS, but it's not empty as some services need to run on another server for a few months.

                I cannot add the domain to Cloudron, the Hetzner API is fresh and fine (works to manage with other domains in the same account).

                Adding "two-words.com" to the DNS zone file name doesn't solve the issue on my end. What can I do?

                1 Reply Last reply
                0
                • J Online
                  J Online
                  joseph
                  Staff
                  wrote on last edited by
                  #7

                  Have you tried host -NS two-words.com already? Does it point to Hetzner?

                  1 Reply Last reply
                  0
                  • J Offline
                    J Offline
                    jayonrails
                    translator
                    wrote on last edited by
                    #8

                    As I have a similar and bigger issue, I created a new thread:

                    https://forum.cloudron.io/post/101241

                    1 Reply Last reply
                    0
                    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