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. DNS failure

DNS failure

Scheduled Pinned Locked Moved Solved Support
updatedns
12 Posts 2 Posters 1.4k 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.
  • V Offline
    V Offline
    vansens
    wrote on last edited by joseph
    #1

    Hello, since a few days, my backups are failing and I am getting "Email not configured properly".
    Turns out that name resolution does not work at all.

    I tried to troubleshot unbound as per the Cloudron docs, but that won't work, as I discovered the /etc/netplan folder is completely empty.

    I am running on a small VPS on vpshostingservice.co, Ubuntu 22.04. Cloudron 7.7.2 - I cannot upgrade because this is happening
    3402d2d7-9e2d-4074-8437-e4fc02006e33-image.png

    Kindly assist.

    J 1 Reply Last reply
    1
    • V vansens

      Hello, since a few days, my backups are failing and I am getting "Email not configured properly".
      Turns out that name resolution does not work at all.

      I tried to troubleshot unbound as per the Cloudron docs, but that won't work, as I discovered the /etc/netplan folder is completely empty.

      I am running on a small VPS on vpshostingservice.co, Ubuntu 22.04. Cloudron 7.7.2 - I cannot upgrade because this is happening
      3402d2d7-9e2d-4074-8437-e4fc02006e33-image.png

      Kindly assist.

      J Offline
      J Offline
      joseph
      Staff
      wrote on last edited by
      #2

      @vansens does your provider use netplan? If not, you can simply setup /etc/resolv.conf to your preferred DNS (ideally, this should be your VPS's DNS provider if it has one).

      1 Reply Last reply
      0
      • J Offline
        J Offline
        joseph
        Staff
        wrote on last edited by joseph
        #3

        @vansens if possible, create a test VPS on the service provider and check what they set up the default DNS to. alternately, ask their support . The quick fix while you are figuring this is simply use nameserver 1.1.1.1 in your /etc/resolv.conf

        1 Reply Last reply
        0
        • V Offline
          V Offline
          vansens
          wrote on last edited by
          #4

          Hey thanks for the quick reply. I am looking at another VM at the same provider, and there is nothing in /etc/netplan either.

          In the working machine's resolv.conf I see this:

          nameserver 8.8.8.8
          nameserver 1.1.1.1
          

          In my Cloudron's resolv.conf, I see this:

          nameserver 127.0.0.53
          options edns0 trust-ad
          search .
          

          Do I overwrite it with your suggestion ("simply use nameserver 1.1.1.1") or do I append it?

          J 1 Reply Last reply
          1
          • V vansens

            Hey thanks for the quick reply. I am looking at another VM at the same provider, and there is nothing in /etc/netplan either.

            In the working machine's resolv.conf I see this:

            nameserver 8.8.8.8
            nameserver 1.1.1.1
            

            In my Cloudron's resolv.conf, I see this:

            nameserver 127.0.0.53
            options edns0 trust-ad
            search .
            

            Do I overwrite it with your suggestion ("simply use nameserver 1.1.1.1") or do I append it?

            J Offline
            J Offline
            joseph
            Staff
            wrote on last edited by
            #5

            @vansens You have already upgraded to 8.0.3 correct ? if so, just replace the file and that's it.

            1 Reply Last reply
            0
            • V Offline
              V Offline
              vansens
              wrote on last edited by
              #6

              @joseph sorry I thought i updated but I did not. So i am still on 7.7.2 (but I cannot change the subject). I just tried to update with the /etc/resolv.conf set to what you suggested, but it failed and is still on 7.7.2

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

                @vansens OK, so in 7.7.2, unbound is still in use. And the 127.0.0.53 in resolv.conf is correct . Can you check if

                • unbound is running? Services -> unbound -> restart . Make sure it's green
                • In /etc/resolv.conf, you should have nameserver 127.0.0.1 .
                • then, try resolving using host www.cloudron.io 127.0.0.1 (via ssh) . does this work?

                If the above two work, then the appstore pages should also load.

                1 Reply Last reply
                0
                • V Offline
                  V Offline
                  vansens
                  wrote on last edited by vansens
                  #8

                  Hi @joseph, after restarting Unbound, my resolve.conf looks like this:

                  nameserver 127.0.0.53
                  options edns0 trust-ad
                  search .
                  

                  Name resolution and the appstore work if I change the IP to 127.0.0.1, but not if I leave it at 127.0.0.53
                  With that temporary manual fix, I was able to upgrade to 8.0.3. Name resolution is not working. However, unbound is working now.

                  If I reboot with 8.0.3, the /etc/resolv.conf reads 127.0.0.53 again.

                  My apps are not working now, because they need to download some icons:

                  An error occurred during the configure operation: Network Error: Network error downloading icon : getaddrinfo EAI_AGAIN api.cloudron.io
                  

                  How do I fix this please?

                  1 Reply Last reply
                  1
                  • J Offline
                    J Offline
                    joseph
                    Staff
                    wrote on last edited by joseph
                    #9

                    @vansens 127.0.0.53 is correct in Cloudron 8. I think the issue might be that systemd-resolved has no DNS servers to work with. The nameservers usually come via dhcp or static configuration in /etc/netplan/50-cloud-init.yaml . In that, you can add a static DNS like this (important: merge the setting below with the existing netplan). Then, after a reboot it should work.

                        ethernets:
                            eth0:
                                nameservers:
                                    addresses:
                                    - 8.8.8.8
                                    - 1.1.1.1
                    

                    Above, we are using Cloudflare and Google DNS. Ideally, you should use your server provider's DNS (if they provide one)

                    1 Reply Last reply
                    0
                    • J joseph marked this topic as a question on
                    • V Offline
                      V Offline
                      vansens
                      wrote on last edited by vansens
                      #10

                      @joseph there is nothing in /etc/netplan on my host.
                      I am on a fixed IP set up with /etc/network/interfaces

                      1 Reply Last reply
                      0
                      • J Offline
                        J Offline
                        joseph
                        Staff
                        wrote on last edited by
                        #11

                        @vansens so maybe you can then configure the DNS in /etc/systemd/resolved.conf . Set the DNS there .

                        1 Reply Last reply
                        0
                        • V Offline
                          V Offline
                          vansens
                          wrote on last edited by
                          #12

                          @joseph Thanks, that was it! It's all working now.

                          1 Reply Last reply
                          0
                          • J joseph has marked this topic as solved on
                          • jadudmJ jadudm referenced this topic 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