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 ESERVFAIL example.com - on all domains?

queryNs ESERVFAIL example.com - on all domains?

Scheduled Pinned Locked Moved Solved Support
netcupdns
6 Posts 2 Posters 471 Views 2 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.
  • J Offline
    J Offline
    jayonrails
    translator
    wrote on last edited by joseph
    #1

    Hi,

    I cannot change the DNS Server settings in my domain settings for a domain, because Cloudron says:

    queryNs ESERVFAIL example.com

    When trying on the terminal as stated here:

    @girish said in Domain setup shows 'queryNs ESERVFAIL':

    @SignalScout On the server, please try host -t NS example.com 127.0.0.1 . Does that work? Sometimes, it takes a bit for the NS of a new domain to propagate. One just has to wait it out.

    root@my ~ # host -t NS example.com
    example.com name server root-dns.netcup.net.
    example.com name server third-dns.netcup.net.
    example.com name server second-dns.netcup.net.
    root@my ~ # host -t NS example.com 127.0.0.1
    ;; communications error to 127.0.0.1#53: connection refused
    ;; communications error to 127.0.0.1#53: connection refused
    ;; no servers could be reached

    I don't know how to fix that, I cannot get my domains running. The result is the same for all domains, so I think it is a general error on my server.

    How to get deeper on this?

    Troubleshooter says:

    root@my ~ # cloudron-support --troubleshoot
    Vendor: Hetzner Product:
    Linux: 6.8.0-52-generic
    Ubuntu: noble 24.04
    Processor: AMD Ryzen 5 3600 6-Core Processor
    BIOS AMD Ryzen 5 3600 6-Core Processor Unknown CPU @ 3.6GHz x 12
    RAM: 65758340KB
    Disk: /dev/md2 26G
    [OK] node version is correct
    [OK] IPv6 is enabled and public IPv6 address is working
    [OK] docker is running
    [OK] docker version is correct
    [OK] MySQL is running
    [OK] nginx is running
    [OK] dashboard cert is valid
    [OK] dashboard is reachable via loopback
    [OK] box v8.2.4 is running
    [OK] netplan is good
    [OK] DNS is resolving via systemd-resolved
    [OK] Dashboard is reachable via domain name
    [WARN] Domain example-host.de expiry check skipped because whois does not have this information
    [OK] unbound is running

    I am lost and don't know what to do next, I appreciate any tips on this.

    Best
    Jay

    1 Reply Last reply
    1
    • J joseph marked this topic as a question on
    • J Online
      J Online
      joseph
      Staff
      wrote on last edited by
      #2

      @jayonrails host -t NS example.com 127.0.0.1 is obsolete from Cloudron 8.2 . This is not expected to work.

      • host -t NS example.com - this should also work. this is system dns
      • host -t NS example.com 127.0.0.150 - this should work. this is unbound
      1 Reply Last reply
      0
      • J Offline
        J Offline
        jayonrails
        translator
        wrote on last edited by
        #3

        Thanks for clarification. This works, but doesn't solve the problem that I cannot add new domains to Cloudron with the error

        queryNs ESERVFAIL example.com

        Any idea on that?

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

          @jayonrails So both commands work but still you get ESERVFAIL . Hmmm... Does this happen for all your domains or just a single one? Cloudron is internally querying host -t NS example.com 127.0.0.150 , not sure how the output can be different

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

            Thanks for the information, I will wait for one day for all the DNS changes to take place and then try again.

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

              @jayonrails sounds good. Otherwise, if both commands work and things are still failing, please send a mail to support@cloudron.io to debug this further. Can't see how it fails.

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