Adding your custom domain to the new platform

Saurabh

Make sure you have upgraded to the Pro Plan first.
Make sure this process is only done after you have migrated the data from your old domain to the new platform.
https://discuss.foodomaa.com/d/3332-migration-tool-migrating-data-from-old-foodomaa-to-new-platform

▶ Procedure

Create an account in Cloudflare (Free Plan) and add your main domain. (yourdomain.com and not yourdomain.foodomaa.com)
Log in to your Domain Manager.
(Domain Manager is the entity through which you have purchased your domain Example: GoDaddy, NameCheap, Hostinger, BigRock, etc)
Goto the DNS Settings/DNS Manager on your Domain Manager Dashboard
Remove your current NameServers and add the Nameservers that are provided by Cloudflare.
(Domain Propagation may take 24 hours, but generally happens within a couple of hours)
(Cloudflare will notify you that your domain has been linked successfully)

(Skip Steps: 1, 2, 3, 4 if your main domain is already connected to Cloudflare)
In the new platform, goto Admin > Settings > All Settings > Custom Domain
(This should be your main domain, make sure to enter this domain correctly)
You will be provided with the Records that need to be added to Cloudflare DNS Page.
There will be 3 Records:
Two TXTRecords, and one CNAME Record
Add these records as shown on the Foodomaa Custom Domain page.
If the records are added successfully to Cloudflare, Foodomaa will automatically verify all the configs and your main domain will be ready to be linked. (Generally takes 2-5 minutes, if the records have been added without any mistake)

After this, we will change your Free Plan Domain to your Main Domain in 4-6 working hours.

baljit1221

Sir I want to change my domain name. First my domain name is "FC FOOD". And I have been using foodooma for the past one year. I also have valid license. I have to change my brand name, means is the domain name change.

Do I have to reset Foodooma license first?
Then after setting the new domain, sign-up the new platform?
@Saurabh

baljit1221

baljit1221 Please tell me now sir @Saurabh

Saurabh

baljit1221 no need to reset, just Sign-up to the new platform.

baljit1221

Saurabh ok sir thanks

EzequielMombelli

I want to have a landing page on the main domain and foodoma on the app.mydomain.com subdomain. Can i do this ?

Carlos

I will use a subdomain, too so I have a doubt about CNAME record. In my admin panel I see this:
CNAME @ brandname.foodomaa.com Auto
Since I will use app.mydomain.com is @ correct or must use something like this?:
CNAME app brandname.foodomaa.com Auto
Or is it not possible to add an A record pointing to your IP?

Saurabh

Carlos

I think you should be able to do that:

Record: CNAME
Name: app
Value: brandname.foodomaa.com
TTL: auto

Just give it a try, it might work, if it doesn't, let us know, we will try to figure something out.

Carlos

Saurabh Ok, I will try, thank you.
I am planning to fully migrate tomorrow. I need your help regarding the apps, I don't want to be without service for a long time and from what I understand the old apps will stop working properly. For this reason, please tell me what the fastest procedure would be.
By the way, when I have the new apps can I publish them on the Play Store as an update of the old ones?

EzequielMombelli

Saurabh This i snot working

I think if we add an A record pointing to the ip of your server it might work

EzequielMombelli

@Saurabh I did the custom domain procedure, but I would like to use the subdomain app.mydomain.com
It's possible ?

Carlos

EzequielMombelli @Saurabh Well, I saved myself the test with that setup.
Maybe, as EzequielMombelli says, an A record pointing to the platform IP will solve the problem if the zone for the domain is created on the server.
Or maybe it can be done using some hosted DNS service like https://dns.he.net
Of course we would lose, in this way, the benefits of Cloudfare that I do not need to explain what they are.

Saurabh

Carlos linking A record to our server IP is the easiest way to do it, but there's a big problem with that.

Your domain will stop working if our server IP changes. (Will surely change in the future when we scale our server or migrate to a completely different server architecture)

So CNAME record are only way to go.

EzequielMombelli

@Saurabh @Carlos
I think there must be a solution to this, a large part of the users hosted foodoma in a subdomain and then used the root of the domain as a landing page or website.
I believe at this point that this solution should be a priority before requesting the apps.

Saurabh

EzequielMombelli

Tomorrow I will try to link a custom subdomain and then make the main domain available to link with other hosting.
If it works then I will let you guys know here.

EzequielMombelli

Saurabh Thanks!
Let's wait to see what happens with the test.
We are in touch

Carlos

Saurabh Sorry but I don't agree with that.
If we have an A record pointing to the IP of the server that hosts the main domain and another A record pointing to the IP of the subdomain, both should resolve without any problem in the IPs of the two servers. In fact, I have a similar configuration in cloudfare that I use and it works without problems.

For example:

Record: A
Name: @
Value: main domain server IP (hosting server)

Record: A
Name: app
Value: subdomain server IP (foodomaa server)

Carlos

Saurabh sorry, I misunderstood. You say that the subdomain would stop working if the IP of the foodomaa server changed and, logically, it would.
In that case, maybe the solution would be to change the IP, too, in that DNS record. As you said, the IP will change in the future when you scaled your server, I understand that this will happen eventually and it seems to me something that can be anticipated to make the corresponding change in the DNS record. Personally, it's not a problem for me.

EzequielMombelli

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

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:

On Foodomaa, when asked for the Custom Domain enter your subdomain like app.yourdomain.com
Foodomaa will generate the Records that you need to insert into your Cloudflare DNS page. (two TXT records and one CNAME record)
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: