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.

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

Enable DNSSEC for all Bisq infrastructure domain names #7

Closed
11 of 13 tasks
wiz opened this issue Aug 13, 2020 · 12 comments
Closed
11 of 13 tasks

Enable DNSSEC for all Bisq infrastructure domain names #7

wiz opened this issue Aug 13, 2020 · 12 comments

Comments

@cbeams
Copy link
Contributor

cbeams commented Aug 13, 2020

From https://support.cloudflare.com/hc/en-us/articles/360006660072-Understanding-and-Configuring-DNSSEC-in-Cloudflare-DNS:

To configure DNSSEC, you first enable it in the Cloudflare dashboard and then add a DS record at your domain registrar.

I'll do this for all the domains above that are managed under Cloudflare DNS. I'll then assign @ManfredKarrer to take care of the domain registrar part, as he plays the role of Domain Name Owner (bisq-network/roles#77) and is now the only one with access to make such changes.

@devinbileck
Copy link
Member

I have enabled DNSSEC on the bisq.services domain.

@cbeams
Copy link
Contributor

cbeams commented Aug 19, 2020

Attn @ManfredKarrer: I have just enabled DNSSEC for the bisq.network domain via Cloudflare DNS. You now need to follow the instructions at https://www.namecheap.com/support/knowledgebase/article.aspx/9722/2232/managing-dnssec-for-domains-pointed-to-custom-dns to register the values below with Namecheap. A screenshot from the Cloudflare interface follows, with each of the individual values pasted below.

image

DS Record

bisq.network. 3600 IN DS 2371 13 2 29A0443DC8173F7C3A57E58645C0E10FDD0E4B757CDB276020D9AFCBE79F52CD

Digest

29A0443DC8173F7C3A57E58645C0E10FDD0E4B757CDB276020D9AFCBE79F52CD

Digest Type

SHA256

Algorithm

13

Public Key

mdsswUyr3DPW132mOi8V9xESWE8jTo0dxCjjnopKl+GqJxpVXckHAeF+KkxLbxILfDLUT0rAK9iUzy1L53eKGQ==

Key Tag

2371

Flags

257 (KSK)

@ManfredKarrer
Copy link

Done.

@wiz
Copy link
Contributor Author

wiz commented Aug 20, 2020

@ManfredKarrer looks great, just verified it. thank you!

@wiz wiz unassigned cbeams Aug 20, 2020
@ManfredKarrer
Copy link

Also done now for bisq.io.

@alexej996
Copy link
Member

bisq.community has dnssec enabled now. Sorry for the delay, had to change the domain provider.

@Emzy
Copy link
Contributor

Emzy commented Sep 1, 2020

emzy.de has dnssec now.

@wiz wiz unassigned Emzy Sep 1, 2020
@wiz wiz removed their assignment Sep 11, 2020
@wiz
Copy link
Contributor Author

wiz commented Nov 13, 2020

Since the last 3 explorers are the ones that don't have DNSSEC, closing per bisq-network/bisq#4791

@wiz wiz closed this as completed Nov 13, 2020
@wiz wiz unassigned m52go, mrosseel and sqrrm Nov 13, 2020
@sqrrm
Copy link
Member

sqrrm commented Nov 13, 2020

Finally enabled dnssec for sqrrm.net, thanks for the reminder.

@wiz
Copy link
Contributor Author

wiz commented Nov 13, 2020

Okay cool... Well, I checked your checkbox, but your legacy BSQ explorer is still retired :)

@sqrrm
Copy link
Member

sqrrm commented Nov 13, 2020

Yeah, I think I will stop running an explorer. I don't think we need that many and getting mempool up and running, and then keeping it stable, is better left for those of you with more ops experience.

I'll keep running the bitcoin nodes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants