Cloudflare Developers•3mo ago

Unable to use AWS Route53 CNAME custom domain

I have a CF pages project with a custom domain added i.e. foo.example.com. The domain example.com is set up with AWS nameservers, and it is not possible (powers that be) to migrate to CF DNS. So I set up a CNAME for the foo subdomain with the value of my pages project URL. However, it never passes through the DNS initialisation on CF. (Please note values have been obscured, if you require genuine values please ask and i will DM.) I can dig it:

➜ dig foo.example.com +short

foo.pages.dev.
172.66.44.231
172.66.47.25

➜ dig foo.example.com +short

foo.pages.dev.
172.66.44.231
172.66.47.25

but if i curl it:

➜ curl -vs foo.example.com           
*   Trying 172.66.47.25:80...
* Connected to foo.example.com (172.66.47.25) port 80 (#0)
> GET / HTTP/1.1
> Host: foo.example.com
> User-Agent: curl/7.81.0
> Accept: */*
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 409 Conflict
< Date: Fri, 30 Aug 2024 10:49:11 GMT
< Content-Type: text/plain; charset=UTF-8
< Content-Length: 16
< Connection: close
< X-Frame-Options: SAMEORIGIN
< Referrer-Policy: same-origin
< Cache-Control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
< Expires: Thu, 01 Jan 1970 00:00:01 GMT
< Server: cloudflare
< CF-RAY: 8bb43676da3ab37e-MAN
< 
* Closing connection 0
error code: 1001%

➜ curl -vs foo.example.com           
*   Trying 172.66.47.25:80...
* Connected to foo.example.com (172.66.47.25) port 80 (#0)
> GET / HTTP/1.1
> Host: foo.example.com
> User-Agent: curl/7.81.0
> Accept: */*
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 409 Conflict
< Date: Fri, 30 Aug 2024 10:49:11 GMT
< Content-Type: text/plain; charset=UTF-8
< Content-Length: 16
< Connection: close
< X-Frame-Options: SAMEORIGIN
< Referrer-Policy: same-origin
< Cache-Control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
< Expires: Thu, 01 Jan 1970 00:00:01 GMT
< Server: cloudflare
< CF-RAY: 8bb43676da3ab37e-MAN
< 
* Closing connection 0
error code: 1001%

I can see on the CF docs that this HTTP 409/ CF1001 is setup issues, but does not describe any steps to remediate. I dont believe there's anything on the aws Route53 to block this from working, but i have also contacted the aws team for support. Is there anything on cloudflare that needs doing to resolve?

1 Reply

Jack828OP•3mo ago

Looking at some other threads people have provided some more info, so here it is: Account id d50cb835fb03dc5587fe034dcda135b1 Deployment id 28b40405-3dc6-4a2e-94f4-8b543dcc1ba0 This is now resolved, I deleted the custom domain and re-added. No idea what the difference is, since i definitely tried that...

Gaming

Programming

Unable to use AWS Route53 CNAME custom domain