bisq-network / roles

@bisq-network contributor roles
https://bisq.wiki/Roles
16 stars 16 forks source link

DNS Admin #18

Open cbeams opened 7 years ago

cbeams commented 7 years ago

This role is responsible for administering DNS for the bisq.network and bisq.io domain names via Cloudflare. This role does not include administering and renewing domain name registrations at Namecheap; this is the job of the Domain Name Owner role (#77). Other bisq-related domains such as bisq.wiki and bisq.community are independently managed.


Docs: none, other than the above Team: @bisq-network/dns-admins

cbeams commented 6 years ago

2017.12 report

Nothing to report. Only DNS activities this month involved migrating forum.bisq.io to bisq.community in bisq-network/dns#5.

/cc bisq-network/compensation#26

cbeams commented 6 years ago

2018.01 report

Nothing to report.

/cc bisq-network/compensation#35

cbeams commented 6 years ago

2018.02 report

Nothing to report.

/cc bisq-network/compensation#40

cbeams commented 6 years ago

2018.03 report

At @alexej996's request, I created a CNAME for the old forum.bisq.io to the new bisq.community. Otherwise, nothing to report.

/cc bisq-network/compensation#57

cbeams commented 6 years ago

2018.04 report

No activity / nothing to report.

/cc bisq-network/compensation#68

cbeams commented 6 years ago

2018.05 report

Nothing to report.

/cc bisq-network/compensation#74

ripcurlx commented 6 years ago

2018.06 report

Nothing to report.

/cc https://github.com/bisq-network/compensation/issues/84

cbeams commented 6 years ago

2018.06 report

Thanks @ripcurlx for taking on the role here. Need to actually grant you access rights to our DNS at Namecheap and CloudFlare though :)

/cc bisq-network/compensation#89

ripcurlx commented 6 years ago

2018.07 report

Nothing to report.

/cc bisq-network/compensation#98

cbeams commented 6 years ago

2018.07 report

I've updated the description of this issue for accuracy and removed @ripcurlx as an owner as he doesn't actually have access to Namecheap / Cloudflare, and both are required to carry out the duties of the role. We definitely should get a secondary role owner who has this access as I'm currently a single point of failure, but better to keep things accurate in the meantime. @ripcurlx, when I get you set up with Netlify for the website (as mentioned in https://github.com/bisq-network/roles/issues/12#issuecomment-409176789), I'll also get you set up with access to these resources. Thanks.

BSQ requested: 25

/cc bisq-network/compensation#101

ripcurlx commented 6 years ago

2018.08 report

Nothing to report.

/cc bisq-network/compensation#109

cbeams commented 6 years ago

@ripcurlx, there's no need to report here monthly, as (a) you were originally set up as a secondary owner and (b) because you don't actually have access to any of our DNS infrastructure (yet). Would be good to change that soon, though.

cbeams commented 6 years ago

2018.08 report

Nothing to report.

BSQ Requested: 25

/cc bisq-network/compensation#114

cbeams commented 6 years ago

2018.09 report

Nothing to report.

BSQ Requested: 25

/cc bisq-network/compensation#139

cbeams commented 5 years ago

2018.10 report

We had a minor mix-up this month in which bitsquare.io DNS was switched back from being managed at Cloudflare to being managed at Namecheap, and the site was down for a while until control was restored to Cloudflare.

In the process, I granted @ManfredKarrer access to Cloudflare, so that I'm not the only one who can handle these issues in the future.

BSQ Requested: 25

/cc bisq-network/compensation#160

cbeams commented 5 years ago

2018.11 report

Nothing to report.

BSQ requested: 25

/cc bisq-network/compensation#179

cbeams commented 5 years ago

Per https://github.com/bisq-network/roles/issues/1#issuecomment-444857417, I'll be away for the next ~2 months, but I will retain the primary DNS Admin role during that time. Changes here are infrequent, and Manfred and I agreed there's no immediate need to formally hand off the role. Manfred has access to Cloudflare, where our DNS is managed, and in the end, Manfred has control over NS records for our various domains via Namecheap, so can always take over control of DNS if need be.

Note that I will not issue any monthly updates for this role while I'm away.

cbeams commented 4 years ago

Cycle 10 report

Similar to my notes at https://github.com/bisq-network/roles/issues/77#issuecomment-585931639, there have not been reports on this role in my long absence, but I'll be picking them up again now going forward. Nothing has changed in the meantime with our existing DNS configuration, though I did create new DNS entries for our new bisq.wiki domain. These entries are being managed at the domain registrar (Gandi) currently, but as mentioned in the link above, I plan to hand off both the bisq.wiki domain name ownership as well as DNS administration to a new Bisq Wiki Operator role, currently being played informally by @wiz.

cbeams commented 4 years ago

Cycle 12 report

Just to acknowledge it, I missed my report for Cycle 11. There has been no activity to report in any case. I did, however, just create bisq-network/proposals#211 to eliminate this role altogether. The impetus for creating that proposal now is that this role has never had a bond posted for it. Instead of posting that bond now, however, I am suggesting that we eliminate this role entirely, which will avoid the need to do it at all.

cbeams commented 4 years ago

Cycle 12 report (continued)

The proposal I mentioned above to eliminate this role was flawed for reasons pointed out in the comments at bisq-network/proposals#211. I'll be withdrawing it shortly. I've also just created a proposal to post my bond for this role at bisq-network/proposals#213.

/cc bisq-network/compensation#533

cbeams commented 4 years ago

Cycle 13 report

Nothing to report.

/cc bisq-network/compensation#573

cbeams commented 4 years ago

Cycle 14 report

No activity to report this month. Note that I am stepping away from the project and so have handed off most of my roles and responsibilities, but I plan to continue to own this role indefinitely.

/cc bisq-network/compensation#600

cbeams commented 4 years ago

Cycle 15 report

There was a major Cloudflare DNS outage on July 17th (yesterday as of this writing), but I was not alerted to any problems on our side. That is, bisq.network (which is managed at Cloudflare) may have indeed experienced an outage, but I did not hear anything about it. Nothing additional to report.

/cc bisq-network/compensation#612

cbeams commented 4 years ago

Cycle 16 report

Per https://github.com/bisq-network/ops/issues/7, I enabled DNSSEC for the bisq.io and bisq.network domains via Cloudflare and @ManfredKarrer, acting as Domain Name Owner (#77), handled registering the information on the Namecheap side.

I also updated the description of this role to better reflect its actual duties.

/cc https://github.com/bisq-network/compensation/issues/648

cbeams commented 4 years ago

Cycle 17 report

Nothing to report.

/cc https://github.com/bisq-network/compensation/issues/668

cbeams commented 3 years ago

Cycle 18 report

Added an SPF record per @wiz's request to avoid spoofing email from the bisq.network domain. Nothing else to report.

/cc https://github.com/bisq-network/compensation/issues/694

cbeams commented 3 years ago

Cycle 19 report

Updated DNS record for list.bisq.network per @Emzy's request at https://github.com/bisq-network/roles/issues/26#issuecomment-734260162. Nothing else to report.

/cc https://github.com/bisq-network/roles/issues/26#issuecomment-734260162

cbeams commented 3 years ago

Cycle 20 report

/cc https://github.com/bisq-network/compensation/issues/737

cbeams commented 3 years ago

Cycle 21 report

Nothing to report.

/cc bisq-network/compensation#771

cbeams commented 3 years ago

Cycle 22 report

Nothing to report.

/cc bisq-network/compensation#794

cbeams commented 3 years ago

Cycle 23 report

Nothing to report.

/cc bisq-network/compensation#820

cbeams commented 3 years ago

Cycle 24 report

Nothing to report.

/cc bisq-network/compensation#836

cbeams commented 3 years ago

Cycle 25 report

Nothing to report.

/cc https://github.com/bisq-network/compensation/issues/862

cbeams commented 3 years ago

Cycle 26 report

Nothing to report.

/cc bisq-network/compensation#881

cbeams commented 2 years ago

Cycle 29 report

Nothing to report

/cc https://github.com/bisq-network/compensation/issues/924

cbeams commented 2 years ago

Cycle 30 report

Nothing to report

/cc https://github.com/bisq-network/compensation/issues/942

cbeams commented 2 years ago

Cycle 31 report

Nothing to report

/cc https://github.com/bisq-network/compensation/issues/964

cbeams commented 2 years ago

Cycle 32 report

Nothing to report

/cc https://github.com/bisq-network/compensation/issues/992

cbeams commented 2 years ago

Cycle 33 report

Nothing to report

/cc https://github.com/bisq-network/compensation/issues/1007

cbeams commented 2 years ago

Cycle 34 report

@leo816 asked whether we have @bisq.network email addresses he or someone else could use to prove ownership over our domain. I told him we don't, but that we could do a TXT record proof if that's sufficient for his needs.

Otherwise nothing to report.

/cc https://github.com/bisq-network/compensation/issues/1043

cbeams commented 2 years ago

Update: I've just re-enabled Cloudflare proxying in front of the bisq.network site. We got a bill from Netlify for the first time last month (March 2022), and after following up with them and looking at traffic data, it's because there was what looks like an attack on March 21st and 22nd resulting in 22M+ requests in a single day totaling nearly a TB of data transfer. @ripcurlx has paid the bill and will request reimbursement for it similar to the way he requests reimbursement for GitHub fees. I'm still waiting for Netlify support to tell us if there's anything we can do to avoid such spikes in the future, but in the meantime, I've re-enabled Cloudflare proxying for bisq.network in hopes that Cloudflare's DDoS protection might help mitigate any such future attacks. I see no practical downside in doing this, and the change is easy to reverse (to remove the proxying) if anything does come up.

Emzy commented 2 years ago

The only downside is that Cloudflare will collect all the access data. But you have to use the Tor browser anyway to be private on the Internet.

cbeams commented 2 years ago

Cycle 35 report

Nothing to report beyond the presumed to the leading to high Netlify billing issue leading to re-enablement of Cloudflare proxying discussed above in https://github.com/bisq-network/roles/issues/18#issuecomment-1097807082

/cc https://github.com/bisq-network/compensation/issues/1057

cbeams commented 2 years ago

Cycle 36 report

Nothing to report

/cc https://github.com/bisq-network/compensation/issues/1084

cbeams commented 2 years ago

Cycle 37 report

Nothing to report

/cc https://github.com/bisq-network/compensation/issues/1105

cbeams commented 2 years ago

Cycle 38 report

Nothing to report

/cc https://github.com/bisq-network/compensation/issues/1117

cbeams commented 2 years ago

Cycle 39 report

Nothing to report

/cc https://github.com/bisq-network/compensation/issues/1142

cbeams commented 1 year ago

Cycle 40 report

Nothing to report

/cc https://github.com/bisq-network/compensation/issues/1168

cbeams commented 1 year ago

Cycle 41 report

Nothing to report

/cc https://github.com/bisq-network/compensation/issues/1182

cbeams commented 1 year ago

Cycle 42 report

Nothing to report

/cc https://github.com/bisq-network/compensation/issues/1201