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. Waiting for DNS propagation

Waiting for DNS propagation

Scheduled Pinned Locked Moved Solved Support
cloudflarednsdomains
13 Posts 3 Posters 2.2k 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.
  • nebulonN nebulon

    Since it looks like you are using Cloudflare, are you using the proxying feature?
    Also can you double check that the unbound service is up and running?

    L Offline
    L Offline
    L3oN
    wrote on last edited by
    #3

    @nebulon
    Yea its runing.
    I use only dns on other server i dont have this problem and same use cf

    1 Reply Last reply
    0
    • nebulonN Offline
      nebulonN Offline
      nebulon
      Staff
      wrote on last edited by
      #4

      So you are saying your my.domain.com is correctly resolving on your server to your public IP address using unbound via 127.0.0.1 ?

      L 1 Reply Last reply
      0
      • nebulonN nebulon

        So you are saying your my.domain.com is correctly resolving on your server to your public IP address using unbound via 127.0.0.1 ?

        L Offline
        L Offline
        L3oN
        wrote on last edited by
        #5

        @nebulon
        Yes

        1 Reply Last reply
        0
        • L Offline
          L Offline
          L3oN
          wrote on last edited by L3oN
          #6

          I use hetzner (2 dedicated, 2 cloud)
          On 1 dedicated working
          on others it's this same so i dont know what's going on
          alt text
          alt text

          only main domain is broken

          nebulonN 1 Reply Last reply
          0
          • L L3oN

            I use hetzner (2 dedicated, 2 cloud)
            On 1 dedicated working
            on others it's this same so i dont know what's going on
            alt text
            alt text

            only main domain is broken

            nebulonN Offline
            nebulonN Offline
            nebulon
            Staff
            wrote on last edited by
            #7

            @L3oN oh! could it be that no A record exists for the main domain? If so just create one with an empty subdomain field through Cloudflare. Cloudron only creates this if an app is installed on that or if any app has an alias/redirect configured for the main domain.

            L 1 Reply Last reply
            0
            • nebulonN nebulon

              @L3oN oh! could it be that no A record exists for the main domain? If so just create one with an empty subdomain field through Cloudflare. Cloudron only creates this if an app is installed on that or if any app has an alias/redirect configured for the main domain.

              L Offline
              L Offline
              L3oN
              wrote on last edited by L3oN
              #8

              @nebulon
              On screen its seems it's dont have but i have A record for main domain 🙂
              third A record is for main domain

              on stats i have app installed

              nebulonN 1 Reply Last reply
              0
              • L L3oN

                @nebulon
                On screen its seems it's dont have but i have A record for main domain 🙂
                third A record is for main domain

                on stats i have app installed

                nebulonN Offline
                nebulonN Offline
                nebulon
                Staff
                wrote on last edited by
                #9

                @L3oN so things look fine from that perspective then. Can you try to run dig @8.8.8.8 domain.com on the server to get an answer from a different source?

                Also if you want, send your actual domain to support@cloudron.io so we can also run some tests against this.

                L 1 Reply Last reply
                0
                • nebulonN nebulon

                  @L3oN so things look fine from that perspective then. Can you try to run dig @8.8.8.8 domain.com on the server to get an answer from a different source?

                  Also if you want, send your actual domain to support@cloudron.io so we can also run some tests against this.

                  L Offline
                  L Offline
                  L3oN
                  wrote on last edited by L3oN
                  #10

                  @nebulon

                  ; <<>> DiG 9.16.1-Ubuntu <<>> @8.8.8.8 webxxx
                  ; (1 server found)
                  ;; global options: +cmd
                  ;; Got answer:
                  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20348
                  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

                  ;; OPT PSEUDOSECTION:
                  ; EDNS: version: 0, flags:; udp: 512
                  ;; QUESTION SECTION:
                  ;webxxx. IN A

                  ;; ANSWER SECTION:
                  xxx. 300 IN A 65.108.xxx

                  ;; Query time: 212 msec
                  ;; SERVER: 8.8.8.8#53(8.8.8.8)
                  ;; WHEN: Tue May 24 18:44:51 UTC 2022
                  ;; MSG SIZE rcvd: 56

                  i send you domain on PM

                  girishG 1 Reply Last reply
                  0
                  • L L3oN

                    @nebulon

                    ; <<>> DiG 9.16.1-Ubuntu <<>> @8.8.8.8 webxxx
                    ; (1 server found)
                    ;; global options: +cmd
                    ;; Got answer:
                    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20348
                    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

                    ;; OPT PSEUDOSECTION:
                    ; EDNS: version: 0, flags:; udp: 512
                    ;; QUESTION SECTION:
                    ;webxxx. IN A

                    ;; ANSWER SECTION:
                    xxx. 300 IN A 65.108.xxx

                    ;; Query time: 212 msec
                    ;; SERVER: 8.8.8.8#53(8.8.8.8)
                    ;; WHEN: Tue May 24 18:44:51 UTC 2022
                    ;; MSG SIZE rcvd: 56

                    i send you domain on PM

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

                    @L3oN I wonder if this is something DNSSEC related. Can you please try https://docs.cloudron.io/troubleshooting/#dns ? You can also forward everything to 8.8.8.8 (the 1.2.3.4 in that example), to see if it gets things moving ahead.

                    L 1 Reply Last reply
                    0
                    • girishG girish

                      @L3oN I wonder if this is something DNSSEC related. Can you please try https://docs.cloudron.io/troubleshooting/#dns ? You can also forward everything to 8.8.8.8 (the 1.2.3.4 in that example), to see if it gets things moving ahead.

                      L Offline
                      L Offline
                      L3oN
                      wrote on last edited by
                      #12

                      @girish
                      And it's work. THX 🙂

                      1 Reply Last reply
                      0
                      • L L3oN has marked this topic as solved on
                      • nebulonN Offline
                        nebulonN Offline
                        nebulon
                        Staff
                        wrote on last edited by
                        #13

                        Just to note, it seems it was a timing issue, where the DNS in this case took longer than expected for full propagation.

                        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