Forum Discussion
Cirrostratuswhat will happen if local gtm/dns disable the sync with other gtm/dns sync group?
Hello Herman2024
As per my information, once you removed, the local GTM will no longer receive updates (wide IPs, pools, data centers, server objects) from the global sync group. Its configuration becomes stale or frozen in time at the point of removal unless you manually manage it. local GTM will continue to answer DNS queries.
However, its view of the GTM topology is limited to only what it still knows — it won't see the updated health or availability of GTM objects in other regions.
what will work
Local DNS service will not stop — it will still answer queries.
Health checks to local application servers will still be accurate.
Any wide IPs or pools using only local resources should behave normally.
RISK:
Let’s say an app is hosted only in Region B, and Region A's GTM was learning about that app via the sync group.If you remove Region A's GTM from the group:
It may mark that app as down because it no longer sees Region B's data.
Local users in Region A may get an NXDOMAIN, fallback, or be routed to an incorrect pool.
BR
Aswin
MVPHello Herman2024
As per my information, once you removed, the local GTM will no longer receive updates (wide IPs, pools, data centers, server objects) from the global sync group. Its configuration becomes stale or frozen in time at the point of removal unless you manually manage it. local GTM will continue to answer DNS queries.
However, its view of the GTM topology is limited to only what it still knows — it won't see the updated health or availability of GTM objects in other regions.
what will work
Local DNS service will not stop — it will still answer queries.
Health checks to local application servers will still be accurate.
Any wide IPs or pools using only local resources should behave normally.
RISK:
Let’s say an app is hosted only in Region B, and Region A's GTM was learning about that app via the sync group.
If you remove Region A's GTM from the group:
It may mark that app as down because it no longer sees Region B's data.
Local users in Region A may get an NXDOMAIN, fallback, or be routed to an incorrect pool.
BR
Aswin
Herman2024Thanks Aswin_mk for your kind advice!
