We removed that record and added a A record(with DNS Proxy enabled) so it points to our own servers.
But Cloudflare is still routing traffic to the old CNAME record and our server is not receiving any traffic.
Previously, We had not enabled DNS proxy for this CNAME record because that breaks the integration in gitbook.
Right now, We are being sent to https://instadapp-3.gitbook.io/instadapp-eng
and the A records are,
18.104.22.168 22.214.171.124 126.96.36.199
which makes me believe that somehow even though I didn’t turn on DNS Proxy when I had a CNAME record there, It turned on DNS proxy on it’s own.
Now, I see these cloudflare IPs and because of some bug, The traffic is being sent to gitbook’s servers.
Please look into this.