feat: add GeoDNS documentation #842
Conversation
* chore: document hostPaths mounted by CVMs * fix table * add link to sysbox design nodes * chore: edit text * remove stray character Co-authored-by: Katie Horne <katie@coder.com>
|
Very rough. I'm not super happy with the Cloudflare section taking up the whole document but I'm unsure how to solve it |
|
✨ Coder.com for PR #842 deployed! It will be updated on every commit.
|
admin/satellites/geo-dns.md
Outdated
| @@ -0,0 +1,120 @@ | |||
| --- | |||
| title: GeoDNS | |||
There was a problem hiding this comment.
How about we call this "global load balancing," or something similar?
If you google GeoDNS, this is the top hit: https://en.wikipedia.org/wiki/GeoDNS
Do these docs only refer to Anycast routing, or can people use this if they are using split-horizon DNS?
admin/satellites/geo-dns.md
Outdated
| - A primary access URL (e.g. `https://primary.example.com`). | ||
| - One or more satellite access URLs (e.g. `https://sydney.example.com`, | ||
| `https://london.example.com`). | ||
| - A GeoDNS load balancer access URL (e.g. `https://coder.example.com`). The |
There was a problem hiding this comment.
GCP does something similar with Anycast, https://cloud.google.com/load-balancing
We should distinguish whether this feature is for people using Anycast (a CDN or global load balancing) versus split-horizon DNS (where the DNS responses vary according to the user's IP address/location)
Co-authored-by: Jonathan Yu <jonathan@coder.com>
|
@deansheather I don't think the Cloudflare section is too big of a problem, but if you'd like, we can split it into its own guide? Then people could use if if they need the help in that section, otherwise they can ignore if they have a load balancer already |
|
If you're OK with it then I think it's fine [SC-20846] |
|
This pull request has been linked to Shortcut Story #20846: Allowed hosts docs. |
|
@deansheather do you have any thoughts on @jawnsy 's suggestions?
Other than that, I think all else is ok |
|
@jawnsy GeoDNS is a correct term for it AFAIK and means the same thing as split-horizon DNS. What are your thoughts on disambiguating it in the first paragraph but keeping it called GeoDNS? |
|
|
I've renamed it to "Proximity based configuration" but I don't think that's a good name yet. Also, I've replaced most of the references to "GeoDNS access URL" with "unified access URL" instead |
4 participants
No description provided.