Workers Sites with a custom domain in Cloudflare Registrar

Developers Workers
1

Hi there,

just started using Worker Sites! Really excited to see this feature. The good news, I can work through the quick start tutorial an dmake everything work on workers.dev. That all works like a charm. :+1:

Next I tried to make it work on a domain I transferred to Cloudflare Registrar. Unfortunately I can’t make it work on my custom domain (raupach.io).

$ cat wrangler.toml
account_id = "hidden"
name = "www"
type = "webpack"
workers_dev = false

[site]
bucket = "./public"
entry-point = "workers-site"

[env.www]
zone_id = "hidden"
route = "raupach.io/*"

I can publish, but the site does not get resolved. Which isn’t surprising because I don’t have any DNS records set for the domain. I only parked it at Cloudflare.

$ dig raupach.io

; <<>> DiG 9.10.6 <<>> raupach.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7638
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
;; QUESTION SECTION:
;raupach.io. IN A

;; AUTHORITY SECTION:
raupach.io. 2724 IN SOA chuck.ns.cloudflare.com. dns.cloudflare.com. 2032117724 10000 2400 604800 3600

;; Query time: 27 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Fri Sep 27 18:53:44 CEST 2019
;; MSG SIZE rcvd: 102

Question is: how to make it work? Do I need to setup a CNAME record pointing to workers.dev?

with kind regards
Björn

1 Like
2

Solved it. All it takes is adding an A record pointing to 192.2.0.1.

All credits go to this post:

3

I think you meant 192.0.2.1 which is an unused IP. The address 192.2.0.1 is publicly routed.