Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

DNS Migration: Unknown Cloudflare to new Cloudflare account #272

Closed
3 tasks done
noahsbwilliams opened this issue Mar 29, 2022 · 3 comments
Closed
3 tasks done

DNS Migration: Unknown Cloudflare to new Cloudflare account #272

noahsbwilliams opened this issue Mar 29, 2022 · 3 comments
Assignees
@noahsbwilliams
Labels
security

Comments

@noahsbwilliams
Copy link
Member

noahsbwilliams commented Mar 29, 2022 •
edited
Loading

Background

The DNS records of progcode.org are currently hosted in a Cloudflare account we don't have access to. We need this to change.

Supports #269, #273

Acceptance Criteria

  • Nameservers updated with new ProgCode-owned Cloudflare account (creds in password manager)
  • No regressions with Google Workspace
  • No regressions with current website
@noahsbwilliams noahsbwilliams self-assigned this Mar 29, 2022
@noahsbwilliams noahsbwilliams changed the title DNS Migration: Unknown Cloudflare to ProgCode Namecheap DNS Migration: Unknown Cloudflare to ProgCode Namecheap or new Cloudflare account Mar 30, 2022
@noahsbwilliams noahsbwilliams changed the title DNS Migration: Unknown Cloudflare to ProgCode Namecheap or new Cloudflare account DNS Migration: Unknown Cloudflare to new Cloudflare account Mar 30, 2022
@noahsbwilliams
Copy link
Member Author

Update as of Wednesday: New Cloudflare account created, credentials in the 1Password.

The existing DNS records were autodetected and preserved by Cloudflare, so all I had to do to port over ProgCode was flip over the nameservers (done).

@noahsbwilliams
Copy link
Member Author

Further Update: There was a recursive DNS loop, probably related to Cloudflare's proxying. I added the raw cname records for the current website hosted in Heroku in "DNS only" mode for now.

@noahsbwilliams
Copy link
Member Author

Further Update: This was resulting in TLS issues, so I've re-enabled proxying just through the new account.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@noahsbwilliams noahsbwilliams

Labels
security
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@noahsbwilliams