Newbie Issue regarding custom domain DNS and worker DNS

[davy.martial3]

What is the name of the domain?

Toutes les écoles d'arts martiaux et clubs de sports de combat

What is the error number?

need to delete an existing record

What is the error message?

need to delete an existing record

What is the issue you’re encountering

Conflict DNS between my main domain and a worker

What steps have you taken to resolve the issue?

Hi there,

I have limited knowledge about hosting and need some help.

I’m using a low-code platform called WeWeb. To add a custom domain, I had to point my domain to the DNS provided by WeWeb. I did this, and everything works fine.

However, since I am building a marketplace, I need to create dynamic indexing for some of my pages (the same page is used multiple times, so I need to index each instance). I set up a worker for this purpose. The problem now is that to validate the worker, I need to add my custom domain.

My custom domain is already hosted on Cloudflare with WeWeb’s DNS, creating a conflict. The worker does not allow me to add the same custom domain unless I delete the existing DNS record from WeWeb. When I did this, the worker pointed to my custom domain, but my WeWeb website went offline, presumably because I deleted the record that was hosting it.

It seems I can’t have both the worker and my domain hosted on Cloudflare. What should I do to have my domain hosted on Cloudflare and the worker working, considering that all the pages that need to be indexed only have different slugs from my main domain (e.g., mydomain.com/supplier1, mydomain.com/supplier2, etc.)?

Thank you!

What feature, service or problem is this related to?

DNS records

What are the steps to reproduce the issue?

try to set up a worker on your main domain

[Laudian]

@davy.martial3

The worker does not allow me to add the same custom domain unless I delete the existing DNS record from WeWeb

Are you maybe using Cloudflare Pages instead of a Worker? Workers don’t have DNS records, but Cloudflare Pages does.

For Workers, you should create Workers Routes.

[davy.martial3]

It’s a worker but I think this is where the issue is in my case:

I need to have an orange clouded DNS record set up.

I have a conflict with the existing DNS

[sdayman]

It sounds like you’re trying to get two different origins to response for that hostname.

Since your site looks to be on the www hostname, that DNS record would have to be Proxied, and then you can assign a Worker Route to www.martialmap.com/*, instead of a Worker Custom Domain.

Your worker should be coded to pass the requests through with a fetch(), but perform the indexing during the request flow.

[davy.martial3]

I think this is already done, because I committed my gitlab with different routes per pages :

[davy.martial3]

This is a snippet of what I pushed.

Would you say that it should be working like this, without adding a custom domain on my worker?