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. Issue with setup

Issue with setup

Scheduled Pinned Locked Moved Solved Support
installationroute53dns
6 Posts 3 Posters 1.1k 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.
    • A Offline
      A Offline
      Azzer
      wrote on last edited by girish
      #1

      Hey friends. I apologize if this wouldn't be the place, but I'm trying to set up cloudron on a fresh install of ubuntu on my homelab. I've set up port forwarding (Port 443 is open and targeted to my server) and I've installed a fresh version of ubuntu (22.04) and cloudron. I am using Route 53 as my DNS and have created an 'A' record that points to my ip (wrote up a dynamic DNS script that runs every hour to update aws with my ip in the case of change) . I tried setting up my domain and got the error 'queryNs ESERVFAIL'.
      c6353e77-9f0b-4afb-9698-08b1dd54fd05-image.png

      I also made sure that my user permissions were setup correctly in AWS and had supplied an access key

      After some research, I was told to try pinging my hosted zone. I pinged my hosted zone and got no response (Which I assume is the issue). I understand that DNS registration can take a few days. I've had this domain for 9 months and haven't thought about using it till now. It's got no errors that I know of associated with it

      After this, I thought about testing my A record to see if it would respond correctly and this was the response.

      b0ad8590-b7d1-496a-b26a-9f8055baa056-image.png

      Now I'm really lost. Been looking around for a while but am itching my head at this. Networking isn't really my thing yet so I apologize if the answer is staring right at me.

      M girishG 2 Replies Last reply
      1
      • A Azzer

        Hey friends. I apologize if this wouldn't be the place, but I'm trying to set up cloudron on a fresh install of ubuntu on my homelab. I've set up port forwarding (Port 443 is open and targeted to my server) and I've installed a fresh version of ubuntu (22.04) and cloudron. I am using Route 53 as my DNS and have created an 'A' record that points to my ip (wrote up a dynamic DNS script that runs every hour to update aws with my ip in the case of change) . I tried setting up my domain and got the error 'queryNs ESERVFAIL'.
        c6353e77-9f0b-4afb-9698-08b1dd54fd05-image.png

        I also made sure that my user permissions were setup correctly in AWS and had supplied an access key

        After some research, I was told to try pinging my hosted zone. I pinged my hosted zone and got no response (Which I assume is the issue). I understand that DNS registration can take a few days. I've had this domain for 9 months and haven't thought about using it till now. It's got no errors that I know of associated with it

        After this, I thought about testing my A record to see if it would respond correctly and this was the response.

        b0ad8590-b7d1-496a-b26a-9f8055baa056-image.png

        Now I'm really lost. Been looking around for a while but am itching my head at this. Networking isn't really my thing yet so I apologize if the answer is staring right at me.

        M Offline
        M Offline
        michaelpope
        wrote on last edited by michaelpope
        #2

        @Azzer Which of Cloudron's DNS Settings are you using?

        Are you using Manual Setup (where you manually edit the DNS settings), or are you using Automatic Setup (where you provide Cloudron a Secret Key to change your DNS for you).

        A 1 Reply Last reply
        0
        • A Azzer

          Hey friends. I apologize if this wouldn't be the place, but I'm trying to set up cloudron on a fresh install of ubuntu on my homelab. I've set up port forwarding (Port 443 is open and targeted to my server) and I've installed a fresh version of ubuntu (22.04) and cloudron. I am using Route 53 as my DNS and have created an 'A' record that points to my ip (wrote up a dynamic DNS script that runs every hour to update aws with my ip in the case of change) . I tried setting up my domain and got the error 'queryNs ESERVFAIL'.
          c6353e77-9f0b-4afb-9698-08b1dd54fd05-image.png

          I also made sure that my user permissions were setup correctly in AWS and had supplied an access key

          After some research, I was told to try pinging my hosted zone. I pinged my hosted zone and got no response (Which I assume is the issue). I understand that DNS registration can take a few days. I've had this domain for 9 months and haven't thought about using it till now. It's got no errors that I know of associated with it

          After this, I thought about testing my A record to see if it would respond correctly and this was the response.

          b0ad8590-b7d1-496a-b26a-9f8055baa056-image.png

          Now I'm really lost. Been looking around for a while but am itching my head at this. Networking isn't really my thing yet so I apologize if the answer is staring right at me.

          girishG Offline
          girishG Offline
          girish
          Staff
          wrote on last edited by
          #3

          @Azzer there is something wrong with the domain

          $ host -t NS aldharrab.co.uk
          Host aldharrab.co.uk not found: 2(SERVFAIL)
          

          You can see same results in https://dnschecker.org/#NS/aldharrab.co.uk . Is this a new domain ? You might have to contact AWS (if that is where you purchased this domain) and ask them why the nameservers have not propagated.

          A 1 Reply Last reply
          0
          • girishG girish marked this topic as a question on
          • M michaelpope

            @Azzer Which of Cloudron's DNS Settings are you using?

            Are you using Manual Setup (where you manually edit the DNS settings), or are you using Automatic Setup (where you provide Cloudron a Secret Key to change your DNS for you).

            A Offline
            A Offline
            Azzer
            wrote on last edited by
            #4

            @michaelpope
            Hello Michael, thanks for your prompt response!

            I am using the automatic setup and provided the access key and secret key to a user that has the exact permissions that have been specified by cloudron documentation

            1 Reply Last reply
            0
            • girishG girish

              @Azzer there is something wrong with the domain

              $ host -t NS aldharrab.co.uk
              Host aldharrab.co.uk not found: 2(SERVFAIL)
              

              You can see same results in https://dnschecker.org/#NS/aldharrab.co.uk . Is this a new domain ? You might have to contact AWS (if that is where you purchased this domain) and ask them why the nameservers have not propagated.

              A Offline
              A Offline
              Azzer
              wrote on last edited by
              #5

              @girish said in Issue with setup:

              You can see same results in https://dnschecker.org/#NS/aldharrab.co.uk . Is this a new domain ? You might have to contact AWS (if that is where you purchased this domain) and ask them why the nameservers have not propagated.

              Hey Girish!
              I've had this domain since April 2022, I did indeed purchase this domain from Route 53 (AWS) and will be contacting them shortly regarding this matter.

              Well, thank god it told me I need to wait 360 seconds before responding to this message.

              Apparently, I need to upgrade to get support on an issue on their end. I'll try to find some other way to contact technical support in the meantime
              15353099-eda7-482e-8f8e-80c0d8034448-image.png

              1 Reply Last reply
              1
              • A Azzer has marked this topic as solved on
              • A Offline
                A Offline
                Azzer
                wrote on last edited by
                #6

                Hey y'all. Used another domain I had that was correctly propagated. It's perfect. Now I gotta wait for my DNS records to update before I do the switch!

                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