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. setup get stuck in waitForDns

setup get stuck in waitForDns

Scheduled Pinned Locked Moved Solved Support
dnsnetworking
2 Posts 1 Posters 28 Views 1 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.
  • C Offline
    C Offline
    CodeResearcher
    wrote last edited by joseph
    #1

    Hi all,

    looking for some support regarding the initial setup of cloudron.

    My domain is registered by namecheap.com. Unfortunately I'm not fullfilling the criteria by namecheap for using an API key. Therefore I used Wildcard as a DNS Provider. But the setup gets stuck. Log file is repeating those entries:

    2025-07-12T20:21:36.032Z box:dns/waitfordns waitForDns: nameservers are ["dns1.registrar-servers.com","dns2.registrar-servers.com"]
    2025-07-12T20:21:36.033Z box:dns/waitfordns resolveIp: Checking AAAA for my.my-domain.net at 156.154.132.200
    2025-07-12T20:21:36.041Z box:dns/waitfordns isChangeSynced: my.my-domain.net (AAAA) was resolved to aaaa:bbbb:cccc:dddd:: at NS dns1.registrar-servers.com (156.154.132.200). Expecting aaaa:bbbb:cccc:dddd::1. M>
    2025-07-12T20:21:36.041Z box:dns/waitfordns resolveIp: Checking AAAA for my.my-domain.net at 2610:a1:1024::200
    2025-07-12T20:21:36.071Z box:dns/waitfordns isChangeSynced: my.my-domain.net (AAAA) was resolved to aaaa:bbbb:cccc:dddd:: at NS dns1.registrar-servers.com (2610:a1:1024::200). Expecting aaaa:bbbb:cccc:dddd::1.>
    2025-07-12T20:21:36.071Z box:dns/waitfordns waitForDns: my.my-domain.net at ns dns1.registrar-servers.com: not done
    2025-07-12T20:21:36.071Z box:dns/waitfordns Attempt 91 failed. Will retry: ETRYAGAIN
    

    I looks like IPv6 address don't match. My IPv6 address is aaaa:bbbb:cccc:dddd:: it's expecting aaaa:bbbb:cccc:dddd::1. Any idea how this can be solved?

    1 Reply Last reply
    1
    • C Offline
      C Offline
      CodeResearcher
      wrote last edited by
      #2

      solved by adjusting existing DNS A Record entry. Changing from aaaa:bbbb:cccc:dddd:: to aaaa:bbbb:cccc:dddd::1

      1 Reply Last reply
      2
      • C CodeResearcher has marked this topic as solved
      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