this post was submitted on 12 Nov 2023
3 points (100.0% liked)

Self-Hosted Main

515 readers
1 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

For Example

We welcome posts that include suggestions for good self-hosted alternatives to popular online services, how they are better, or how they give back control of your data. Also include hints and tips for less technical readers.

Useful Lists

founded 1 year ago
MODERATORS
communick@selfhosted.forum
3
Transferred my domain to CF but none of my tunnels work, everything is still going through my previous registrar. (alien.top)
submitted 1 year ago by RoleAwkward6837@alien.top to c/main@selfhosted.forum
1 comments fedilink hide all child comments
 

I had my domain with Dynu for years, great company btw. But I recently switched over to Cloudflare to use tunnels.

I followed the steps outlined on the CF site, removed the old name servers, added CFs name servers, enabled zone transfer at my old registrar, and when I go to my site overview on the CF dashboard I see the message "Great news! Cloudflare is now protecting your site". The transfer was initiated almost exactly 24 hours ago.

here's how I have things setup:

  • All services setup with a CF tunnel is a sub domain, so "service.mydomain.com"
  • All CF Tunnels show up as CNAME records.
  • My base domain A Record points to the public IP of my VPS. This is used as a tunnel for my email server since CF won't pass SMTP or IMAP through their tunnels. (at least that's what I was told)
  • All MX records point to relays I still have with Dynu.

I have 2 other domains with Cloudflare, one of which was also transferred from Dynu, and the tunnels on them work just fine.

Im not sure if I did something wrong, missed a step, or if I just need to wait longer.

you are viewing a single comment's thread
view the rest of the comments
[–] essellburns@beehaw.org 1 points 1 year ago

Given the timescale of the transfer, sounds like a DNS cache somewhere in the chain.

It'll fix itself if I'm right