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. Limitation with DNS using OVH in validating name server domains: "Domain nameservers are not set to OVH"

Limitation with DNS using OVH in validating name server domains: "Domain nameservers are not set to OVH"

Scheduled Pinned Locked Moved Solved Support
nameserverovhdomains
7 Posts 4 Posters 1.5k Views 5 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.
  • d19dotcaD Offline
    d19dotcaD Offline
    d19dotca
    wrote on last edited by girish
    #1

    One of my client's domain names has OVH name servers, and that's what's set on the domain, however when I tried to integrate the domain with the newer OVH DNS option in Cloudron, I get an error suggesting it's not using OVH name servers:

    Domain nameservers are not set to OVH
    

    As you can see in the screenshot below, the DNS servers set on this domain are indeed OVH DNS servers and have been for probably the last year or so.

    4e69f072-ac83-4ed9-ad28-711d9b85e125-image.png

    I see the following in the code:

        if (!nameservers.every(function (n) { return n.toLowerCase().indexOf('ovh.net') !== -1; })) { // SoYouStart and Kimsufi can also be accomdated
            debug('verifyDomainConfig: %j does not contain OVH NS', nameservers);
            throw new BoxError(BoxError.BAD_FIELD, 'Domain nameservers are not set to OVH');
        }
    

    If I'm reading it correctly, Cloudron is validating the name servers on the assumption that it's ending with ovh.net, however this is not the only possibility and is currently restricting these other regional TLDs that OVH uses. In my example it's being served on *.ovh.ca.

    To accommodate other regional TLDs from OVH, I wonder if there's a way to simply allow it if it's set to ovh.*. May not be ideal but would at least allow for any currently unknown name server domains OVH uses. I recommend this because I simply couldn't find a master list of all the different domains OVH uses, so would be the more inclusive way to do it I suppose. Alternatively at least consider adding in the following extra domains which I believe OVH uses (just from what I've seen in the past): ovh.ca, ovh.us, ovh.com, ovhcloud.com, ovh.co.uk.

    --
    Dustin Dauncey
    www.d19.ca

    girishG 2 Replies Last reply
    5
    • d19dotcaD d19dotca

      One of my client's domain names has OVH name servers, and that's what's set on the domain, however when I tried to integrate the domain with the newer OVH DNS option in Cloudron, I get an error suggesting it's not using OVH name servers:

      Domain nameservers are not set to OVH
      

      As you can see in the screenshot below, the DNS servers set on this domain are indeed OVH DNS servers and have been for probably the last year or so.

      4e69f072-ac83-4ed9-ad28-711d9b85e125-image.png

      I see the following in the code:

          if (!nameservers.every(function (n) { return n.toLowerCase().indexOf('ovh.net') !== -1; })) { // SoYouStart and Kimsufi can also be accomdated
              debug('verifyDomainConfig: %j does not contain OVH NS', nameservers);
              throw new BoxError(BoxError.BAD_FIELD, 'Domain nameservers are not set to OVH');
          }
      

      If I'm reading it correctly, Cloudron is validating the name servers on the assumption that it's ending with ovh.net, however this is not the only possibility and is currently restricting these other regional TLDs that OVH uses. In my example it's being served on *.ovh.ca.

      To accommodate other regional TLDs from OVH, I wonder if there's a way to simply allow it if it's set to ovh.*. May not be ideal but would at least allow for any currently unknown name server domains OVH uses. I recommend this because I simply couldn't find a master list of all the different domains OVH uses, so would be the more inclusive way to do it I suppose. Alternatively at least consider adding in the following extra domains which I believe OVH uses (just from what I've seen in the past): ovh.ca, ovh.us, ovh.com, ovhcloud.com, ovh.co.uk.

      girishG Do not disturb
      girishG Do not disturb
      girish
      Staff
      wrote on last edited by
      #2

      @d19dotca ah, my bad. I tested with Europe only. Will change the pattern to `.ovh.*

      1 Reply Last reply
      3
      • d19dotcaD d19dotca

        One of my client's domain names has OVH name servers, and that's what's set on the domain, however when I tried to integrate the domain with the newer OVH DNS option in Cloudron, I get an error suggesting it's not using OVH name servers:

        Domain nameservers are not set to OVH
        

        As you can see in the screenshot below, the DNS servers set on this domain are indeed OVH DNS servers and have been for probably the last year or so.

        4e69f072-ac83-4ed9-ad28-711d9b85e125-image.png

        I see the following in the code:

            if (!nameservers.every(function (n) { return n.toLowerCase().indexOf('ovh.net') !== -1; })) { // SoYouStart and Kimsufi can also be accomdated
                debug('verifyDomainConfig: %j does not contain OVH NS', nameservers);
                throw new BoxError(BoxError.BAD_FIELD, 'Domain nameservers are not set to OVH');
            }
        

        If I'm reading it correctly, Cloudron is validating the name servers on the assumption that it's ending with ovh.net, however this is not the only possibility and is currently restricting these other regional TLDs that OVH uses. In my example it's being served on *.ovh.ca.

        To accommodate other regional TLDs from OVH, I wonder if there's a way to simply allow it if it's set to ovh.*. May not be ideal but would at least allow for any currently unknown name server domains OVH uses. I recommend this because I simply couldn't find a master list of all the different domains OVH uses, so would be the more inclusive way to do it I suppose. Alternatively at least consider adding in the following extra domains which I believe OVH uses (just from what I've seen in the past): ovh.ca, ovh.us, ovh.com, ovhcloud.com, ovh.co.uk.

        girishG Do not disturb
        girishG Do not disturb
        girish
        Staff
        wrote on last edited by
        #3

        @d19dotca Can you try this - https://git.cloudron.io/cloudron/box/-/commit/efd42b729361d6d5e35126f9d4b820f65bc455d4 ?

        1 Reply Last reply
        2
        • A Offline
          A Offline
          AriusII
          wrote on last edited by
          #4

          Hello, and sorry to up this issue but,

          I have a similar issue with OVH anycast DNS, who look like this :

          image.png

          dns200.anycast.me
          ns200.anycast.me

          It is possible to add this exception ?

          Thanks 🙂

          girishG 1 Reply Last reply
          2
          • A AriusII

            Hello, and sorry to up this issue but,

            I have a similar issue with OVH anycast DNS, who look like this :

            image.png

            dns200.anycast.me
            ns200.anycast.me

            It is possible to add this exception ?

            Thanks 🙂

            girishG Do not disturb
            girishG Do not disturb
            girish
            Staff
            wrote on last edited by
            #5

            @AriusII Ah thanks.

            I found that "If the DNS server names end with ovh.net, ovh.ca or anycast.me, your domain name is using the OVHcloud DNS servers. " from https://help.ovhcloud.com/csm/en-dns-secure-domain-dnssec?id=kb_article_view&sysparm_article=KB0051637

            1 Reply Last reply
            2
            • girishG girish marked this topic as a question on
            • girishG girish has marked this topic as solved on
            • dsp76D Online
              dsp76D Online
              dsp76
              wrote on last edited by
              #6

              Strange, want to set up my cloudron with a second domain. Selected Hetzner, but get the above error message. Its freshly changed. Is the error message just quoting "OVH" in mistake?

              (Ask me about B2B marketing automation & low code business solutions, if thats interesting for you.)

              girishG 1 Reply Last reply
              1
              • dsp76D dsp76

                Strange, want to set up my cloudron with a second domain. Selected Hetzner, but get the above error message. Its freshly changed. Is the error message just quoting "OVH" in mistake?

                girishG Do not disturb
                girishG Do not disturb
                girish
                Staff
                wrote on last edited by
                #7

                @dsp76 indeed, thanks for reporting. The error message should read Hetzner instead of OVH when you select Hetzner. I have fixed this for the next release.

                1 Reply Last reply
                1
                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