• How Tos

  • Adding your custom domain to the new platform

Carlos I agree with you @Carlos, when scaling the server the ip could be changed. Its a minute change, I don't think the server is changed every week o moth.
Lets wait until tomorrow! I think we are not the only users for this requirement, I have faith in @Saurabh

      Carlos
      EzequielMombelli

      No!
      Changing the IP is a huge mess!!!

      We are about to reach 500 customers on the new platform. Even with this number, when we change our IP address, all the 500 websites will be down and the operation will be halted resulting in financial loss.

      All these 500 websites' admin needs to be notified and they all need to login to their Cloudflare and change the IP address and wait for some time for the DNS Propagation. You see this is a hectic process.
      And most importantly we cannot let our customers lose their business because of this stuff.

      The main objective of this new platform is to take away your technical challenges so that you can do what you do best, the business. And we do the heavy lifting of managing the tech for you. In short, we are your Tech Partner 🙂

      ===

      Coming back to the subdomain linking thing, it WORKS!!!

      Here's how to do it:

      1. On Foodomaa, when asked for the Custom Domain enter your subdomain like app.yourdomain.com

      2. Foodomaa will generate the Records that you need to insert into your Cloudflare DNS page. (two TXT records and one CNAME record)

      3. Add the provided TXT record but Ignore the CNAME record provided in the Foodomaa Dashboard, instead add this:
        This should be your CNAME if you use a subdomain as your custom domain:


        Type: CNAME
        Name: app
        Value: brandname.foodomaa.com
        Proxy Status: OFF (DNS Only) - Very Important
        TTL: Auto


      Screenshot:

      (After a few minutes, the verification process will be completed, and your subdomain can be linked to Foodomaa)


      ====


      Now your A record for your main domain is free to use, so on Cloudflare, you can now create an A record with this:
      Type: A
      Name: @
      Value: {your hosting provider IP address where the main domain is hosted}
      TTL: Auto


      Screenshot:


          Thank you so much!
          In my case, in the foodomaa backend I already set the custom domain to mydomain.com in a hurry and following the steps that in cloudflare did not allow me to enter the subdomain. Should I open a ticket with @Mani ?

          @Saurabh Ok surely it can be done this way but the cost is too high. Without the proxy, the only thing we would get is a simple DNS resolution, no benefits of Cloudfare, such as caching, protection against DDOS, brute-force attacks and threats against our website, would be taken advantage of. In my case, I have a PRO account in Cloudfare and I see it as nonsense to resolve my subdomain without a proxy.
          I understand the arguments made in this forum why it is complicated to use an A record pointing to the Foodomaa server, but at this point I don't see any better alternative to use a subdomain. The other option would be to forget about the subdomain and use an alternative domain but, well, that's not my idea.

            Carlos guys you don't have to worry about that, that we are handling for your domain. We are handling all the cache and security related stuff.

            Please don't worry about any tech things, leave that to us.

                Saurabh With all due respect, I prefer to continue with my pro plan on Cloudfare so, please, let me know how we can do with custom domain.

                    Carlos sorry, that's not something we can help with.

                    When you add your website to Foodomaa, your domain is managed by our Platform Cloudflare account. All the things are managed by us.
                    (And as said earlier, the security things, caching things, SSL etc will be handled by us)

                    If that's not feasible for you, there's nothing more we can explain on this topic.

                        Saurabh Ok, in that case the only option left for me is to use an alternate domain instead of a subdomain. But, as I understood that there would not be so many inconveniences, I have already requested a custom subdomain from the saas admin panel. I would need to please remove that information to use the alternate main domain and migrate as soon as possible.
                        Thank you very much.

                            Carlos Can you please check once again, I have just reset the server level cache for you .

                                4 days later

                                EzequielMombelli You should skip all these steps and keep only the defaults on.
                                As when you link your custom domain, your website will be managed by our Cloudflare account configs.

                                  What will be the procedure to migrate the old data, If I accidentally upgraded to pro.

                                    @Saurabh @Mani after Cloudflare linked domain successfully and after adding the custom domain name TXT Record and CNAME the url is now showing Cloudflare Error 1014 CNAME Cross-User Banned. Can you guide where might it go wrong.

                                      DaveT delete all the A and AAAA records and then add the CNAME and TXT records.

                                          Saurabh i have check there are no A or AAAA records. There are only 3 DNS that is the TXT and the CNAME which i have added as per instruction. And also on the New Platform Custom Domain Page its is showing only 1 TXT Record and 1 CNAME Record. Please find support ticket #17063 for screenshots.