You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a server sends a heartbeat to masterservers, it only sends to the ipv6 of the domains in "masterservers" cvar, if they are available. (atm only dpmaster.deathmask.net)
Can be manually fixed by adding the raw ipv4, but that's not very flexible.
The heartbeat should be sent to both ipv4 and ipv6.
The text was updated successfully, but these errors were encountered:
For a non-engine change, you can use multiple masterserver cvars, but this will be dependent on having hosts specific to the protocol you need.
dpmaster.deathmask.net (bound to both ipv4 and ipv6) does have alternative specific bindings which you can use directly or cname to:
ipv4.dpmaster.deathmask.net
ipv6.dpmaster.deathmask.net (also bound to both ipv4 and ipv6, but if the client is ipv6, it will prefer ipv6, and ipv4 is a safe fallback).
When a server sends a heartbeat to masterservers, it only sends to the ipv6 of the domains in "masterservers" cvar, if they are available. (atm only dpmaster.deathmask.net)
Can be manually fixed by adding the raw ipv4, but that's not very flexible.
The heartbeat should be sent to both ipv4 and ipv6.
The text was updated successfully, but these errors were encountered: