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


  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
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

Cloudron Forum

Apps | Demo | Docs | Install

DNS status tool reports null on all records

Scheduled Pinned Locked Moved Solved Support
7 Posts 3 Posters 170 Views
    • 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.
  • yusfY Offline
    yusfY Offline
    yusf
    wrote on last edited by yusf
    #1

    a06034a0-2381-4014-ac43-de12187eb78e-bild.png

    Since some recent update, all DNS records are reported [not set] (or null if viewed in Notifications view) even though they present. The Expected value suggested in my case is also not the right one (main domain instead of selected domain).

    I use one domain with automatic DNS provision (Digital Ocean) and one with manual, same problem on both.

    1 Reply Last reply
    0
  • yusfY Offline
    yusfY Offline
    yusf
    wrote on last edited by
    #2

    Adding to this, records aren't added properly when installing new apps:

    c8353496-d6e2-4c81-9cfe-6ac559f07a8a-bild.png

    1 Reply Last reply
    0
  • murgeroM Offline
    murgeroM Offline
    murgero App Dev
    wrote on last edited by
    #3

    I do not have this issue on the latest public stable version. Can you please provide some logs?

    --
    https://urgero.org
    ~ Professional Nerd. Freelance Programmer. ~
    Matrix: @murgero:urgero.org

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

    I would check the following:

    1. Is unbound running? You will find this in the Services view.
    2. Maybe the DNS API keys are invalid/expired?
    3. Any chance outbound UDP requests are blocked? (for DNS)

    As @murgero said, can you see the app logs when it's waiting for DNS.

    1 Reply Last reply
    0
  • yusfY Offline
    yusfY Offline
    yusf
    wrote on last edited by yusf
    #5

    Alright.unbound is not running, log below.

    Jan 01 00:00:00 Logs begin at Tue 2020-01-21 12:12:03 UTC. --
    Jan 23 18:37:50 my.domain.tld systemd[1]: Started Unbound DNS Resolver.
    Jan 23 18:37:51 my.domain.tld unbound[1320]: [1320:0] notice: init module 0: validator
    Jan 23 18:37:51 my.domain.tld unbound[1320]: [1320:0] error: failed to read /var/lib/unbound/root.key
    Jan 23 18:37:51 my.domain.tld unbound[1320]: [1320:0] error: error reading auto-trust-anchor-file: /var/lib/unbound/root.key
    Jan 23 18:37:51 my.domain.tld unbound[1320]: [1320:0] error: validator: error in trustanchors config
    Jan 23 18:37:51 my.domain.tld unbound[1320]: [1320:0] error: validator: could not apply configuration settings.
    Jan 23 18:37:51 my.domain.tld unbound[1320]: [1320:0] error: module init for module validator failed
    Jan 23 18:37:51 my.domain.tld unbound[1320]: [1320:0] fatal error: failed to setup modules
    Jan 23 18:37:51 my.domain.tld systemd[1]: unbound.service: Main process exited, code=exited, status=1/FAILURE
    Jan 23 18:37:51 my.domain.tld systemd[1]: unbound.service: Unit entered failed state.
    Jan 23 18:37:51 my.domain.tld systemd[1]: unbound.service: Failed with result 'exit-code'.
    Jan 23 18:37:51 my.domain.tld systemd[1]: unbound.service: Service hold-off time over, scheduling restart.
    Jan 23 18:37:51 my.domain.tld systemd[1]: Stopped Unbound DNS Resolver.
    Jan 23 18:37:51 my.domain.tld systemd[1]: Started Unbound DNS Resolver.
    Jan 23 18:37:51 my.domain.tld systemd[1]: unbound.service: Main process exited, code=exited, status=1/FAILURE
    Jan 23 18:37:51 my.domain.tld systemd[1]: unbound.service: Unit entered failed state.
    Jan 23 18:37:51 my.domain.tld systemd[1]: unbound.service: Failed with result 'exit-code'.
    Jan 23 18:37:51 my.domain.tld systemd[1]: unbound.service: Service hold-off time over, scheduling restart.
    Jan 23 18:37:51 my.domain.tld systemd[1]: Stopped Unbound DNS Resolver.
    Jan 23 18:37:51 my.domain.tld systemd[1]: Started Unbound DNS Resolver.
    Jan 23 18:37:51 my.domain.tld unbound[1503]: [1503:0] notice: init module 0: validator
    Jan 23 18:37:51 my.domain.tld unbound[1503]: [1503:0] error: failed to read /var/lib/unbound/root.key
    Jan 23 18:37:51 my.domain.tld unbound[1503]: [1503:0] error: error reading auto-trust-anchor-file: /var/lib/unbound/root.key
    Jan 23 18:37:51 my.domain.tld unbound[1503]: [1503:0] error: validator: error in trustanchors config
    Jan 23 18:37:51 my.domain.tld unbound[1503]: [1503:0] error: validator: could not apply configuration settings.
    Jan 23 18:37:51 my.domain.tld unbound[1503]: [1503:0] error: module init for module validator failed
    Jan 23 18:37:51 my.domain.tld unbound[1503]: [1503:0] fatal error: failed to setup modules
    Jan 23 18:37:51 my.domain.tld systemd[1]: unbound.service: Main process exited, code=exited, status=1/FAILURE
    Jan 23 18:37:51 my.domain.tld systemd[1]: unbound.service: Unit entered failed state.
    Jan 23 18:37:51 my.domain.tld systemd[1]: unbound.service: Failed with result 'exit-code'.
    Jan 23 18:37:52 my.domain.tld systemd[1]: unbound.service: Service hold-off time over, scheduling restart.
    Jan 23 18:37:52 my.domain.tld systemd[1]: Stopped Unbound DNS Resolver.
    Jan 23 18:37:52 my.domain.tld systemd[1]: Started Unbound DNS Resolver.
    Jan 23 18:37:52 my.domain.tld unbound[1525]: [1525:0] notice: init module 0: validator
    Jan 23 18:37:52 my.domain.tld unbound[1525]: [1525:0] error: failed to read /var/lib/unbound/root.key
    Jan 23 18:37:52 my.domain.tld unbound[1525]: [1525:0] error: error reading auto-trust-anchor-file: /var/lib/unbound/root.key
    Jan 23 18:37:52 my.domain.tld unbound[1525]: [1525:0] error: validator: error in trustanchors config
    Jan 23 18:37:52 my.domain.tld unbound[1525]: [1525:0] error: validator: could not apply configuration settings.
    Jan 23 18:37:52 my.domain.tld unbound[1525]: [1525:0] error: module init for module validator failed
    Jan 23 18:37:52 my.domain.tld unbound[1525]: [1525:0] fatal error: failed to setup modules
    Jan 23 18:37:52 my.domain.tld systemd[1]: unbound.service: Main process exited, code=exited, status=1/FAILURE
    Jan 23 18:37:52 my.domain.tld systemd[1]: unbound.service: Unit entered failed state.
    Jan 23 18:37:52 my.domain.tld systemd[1]: unbound.service: Failed with result 'exit-code'.
    Jan 23 18:37:52 my.domain.tld systemd[1]: unbound.service: Service hold-off time over, scheduling restart.
    Jan 23 18:37:52 my.domain.tld systemd[1]: Stopped Unbound DNS Resolver.
    Jan 23 18:37:52 my.domain.tld systemd[1]: Started Unbound DNS Resolver.
    Jan 23 18:37:52 my.domain.tld unbound[1548]: [1548:0] notice: init module 0: validator
    Jan 23 18:37:52 my.domain.tld unbound[1548]: [1548:0] error: failed to read /var/lib/unbound/root.key
    Jan 23 18:37:52 my.domain.tld unbound[1548]: [1548:0] error: error reading auto-trust-anchor-file: /var/lib/unbound/root.key
    Jan 23 18:37:52 my.domain.tld unbound[1548]: [1548:0] error: validator: error in trustanchors config
    Jan 23 18:37:52 my.domain.tld unbound[1548]: [1548:0] error: validator: could not apply configuration settings.
    Jan 23 18:37:52 my.domain.tld unbound[1548]: [1548:0] error: module init for module validator failed
    Jan 23 18:37:52 my.domain.tld unbound[1548]: [1548:0] fatal error: failed to setup modules
    Jan 23 18:37:52 my.domain.tld systemd[1]: unbound.service: Main process exited, code=exited, status=1/FAILURE
    Jan 23 18:37:52 my.domain.tld systemd[1]: unbound.service: Unit entered failed state.
    Jan 23 18:37:52 my.domain.tld systemd[1]: unbound.service: Failed with result 'exit-code'.
    Jan 23 18:37:52 my.domain.tld systemd[1]: unbound.service: Service hold-off time over, scheduling restart.
    Jan 23 18:37:52 my.domain.tld systemd[1]: Stopped Unbound DNS Resolver.
    Jan 23 18:37:52 my.domain.tld systemd[1]: unbound.service: Start request repeated too quickly.
    Jan 23 18:37:52 my.domain.tld systemd[1]: Failed to start Unbound DNS Resolver.
    Jan 23 18:37:52 my.domain.tld systemd[1]: unbound.service: Unit entered failed state.
    Jan 23 18:37:52 my.domain.tld systemd[1]: unbound.service: Failed with result 'start-limit-hit'.
    
    1 Reply Last reply
    0
  • girishG Offline
    girishG Offline
    girish Staff
    wrote on last edited by
    #6

    @yusf I guess you ran out of disk space at some point. See https://cloudron.io/documentation/troubleshooting/#unbound for how to fix it.

    yusfY 1 Reply Last reply
    0
  • yusfY Offline
    yusfY Offline
    yusf
    replied to girish on last edited by yusf
    #7

    @girish Your guess is entirely correct. 😊 I'll try it out.

    Edit: Worked. Yay 🎉

    1 Reply Last reply
    2
  • saikarthikS saikarthik referenced this topic on

  • Login

  • Don't have an account? Register

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