Introduce Asian directory server in code#3697
Conversation
For geo redundancy, latency and since Any Genre 3 is not heavily used, we introduce a directory in Asia. See jamulussoftware#3692
|
Any Genre Asia shows up correctly in the client and server instead of Any Genre 3 |
| case AT_ANY_GENRE2: | ||
| return CENTSERV_ANY_GENRE2; | ||
| case AT_ANY_GENRE3: | ||
| return CENTSERV_ANY_GENRE3; |
There was a problem hiding this comment.
We should probably rather not name it CENTSERV anymore...
There was a problem hiding this comment.
Yeah, I was going to say - separate PR to move to DIRECTORY_ and .app in one go?
There was a problem hiding this comment.
We could do this yes. But .app didn't resolve for me yet. @gilgongo
There was a problem hiding this comment.
Ah, looking at the Cloudflare config- I'd forgotten that it works using 301 redirects. For some reason I thought it had some DNS wildcard capability. So no .app for directories right now I'm afraid.
There was a problem hiding this comment.
Yeah, I was going to say - separate PR to move to
DIRECTORY_and.appin one go?
I suppose we could replicate the .io zone to .app and maintain both in parallel? We don't make changes that often after all. As far as I can tell, CloudFlare don't allow pointing two domains to the same zone file at least.
There was a problem hiding this comment.
OK sure. I'll see if I can set up .app with the same host names as .io. Then when that's done we can CNAME all the the .io hosts to those. Might mean some slight downtime on the website cert while that gets re-generated perhaps (or some other hidden issue crops up).
BTW we don't use the CF proxy for .io - in fact we found out we can't with GitHub Pages as it breaks their cert renewal. The proxy is only for .app at the moment so that it can do the http redirects I think.
There was a problem hiding this comment.
Ah, looking at the Cloudflare config- I'd forgotten that it works using 301 redirects. For some reason I thought it had some DNS wildcard capability. So no .app for directories right now I'm afraid.
301 redirects are a HTTP-only concept, and don't apply when just resolving names in DNS. We can do all we need using CNAMEs or parallel A records (and AAAA when we're ready).
There was a problem hiding this comment.
OK so I can try this:
- Export the .io zone file
- Change all .io references in the exported file to .app
- Remove any TXT records that have keys relating to .io (eg _github-challenge-jamulussoftware)
- Delete all the current zone entries in .app
- Import the new zone file into .app
- Add TXT records with new keys for .app
- Remove the www 301 redirect and switch Github Pages over to using .app
The worst that can happen is that the .app version of the website stops responding while it gets sorted out, but .io will be unaffected. Then once it's all working for .app, we change all the relevant CNAMEs in .io to .app.
There was a problem hiding this comment.
Hmm. Maybe we could rather wait for the main website? So just set all the directories as .app instead.
This means duplicating only the cnames set for the .app zone similar to what we have in .io
Then wait a day.
Then put the CNAMEs in .io to .app
Don't change anything on GitHub pages.
There was a problem hiding this comment.
Yeah, I'd just copy the Directory .io entries over as .app entries -- export both zones, extract the Directories from .io, rename to .app, add to the .app zone file, reimport the .app zone file. That should give two DNS entries for each target without any chance of anything breaking.
softins
left a comment
softins
left a comment
There was a problem hiding this comment.
Looks fine and runs as expected, for both Client and Server modes.
4 participants
Short description of changes
For geo-redundancy, latency and since Any Genre 3 is not heavily used, we introduce a directory in Asia. See
#3692
CHANGELOG: Introduce Directory Server in Asia. This replaces Any Genre 3. Asian/Australian users should from now on use Any Genre Asia.
Context: Fixes an issue?
Does this change need documentation? What needs to be documented and how?
Fixes: #3692
Status of this Pull Request
Ready for review
What is missing until this pull request can be merged?
Review
Checklist