Skip to content

Commit

Permalink
Update FAQ on ExternalDNS (#2773)
Browse files Browse the repository at this point in the history
The feature flag it points to have been moved to stable, so the link
is not useful any more.

Also removed notes on ipv6, since they aren't 100% accurate, as we were
discussing in #2767.
  • Loading branch information
markmandel authored Oct 24, 2022
1 parent c34207b commit b8eb48c
Showing 1 changed file with 3 additions and 6 deletions.
9 changes: 3 additions & 6 deletions site/content/en/docs/FAQ/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -140,12 +140,9 @@ the Node (which it should if it's a publicly addressable Node), that it utilised
`InternalIP` address.

### How do I use the DNS name of the Node?
[You can make this available by using the feature flag.]({{< ref "/docs/Guides/feature-stages.md" >}})
Agones uses an IP address as the game server address by default.
This works fine in most cases, but can be a problem if your game server and game client are running on different IP protocols.
e.g) The game server is connected only to the IPv4 network, and the game client is connected only to the IPv6 network.
When this feature is enabled, Agones will preferentially use the External DNS of the Node on which the GameServer Pod is running.
Since the game client can get the domain name instead of the IP address, it will be able to communicate with the game server via DNS64 and NAT64.

If the Kubernetes nodes have an `ExternalDNS` record, then it will be utilised as the `GameServer` address
preferentially over the `ExternalIP` node record.

### How is traffic routed from the allocated Port to the GameServer container?

Expand Down

0 comments on commit b8eb48c

Please sign in to comment.