Zoom: Zoom Conference Room Connector DNS Changes: November 14, 2026 (No Operational Impact)
Affected components: Zoom Conference Room ConnectorZoom Meetings - Zoom Conference Room Connector
Timeline of updates
- scheduled
As part of ongoing service enhancements for the Cloud Room Connector (CRC) service, Zoom will be updating DNS records for SIP/H.323 endpoints in the Japan (Osaka and Tokyo), EU (France and Amsterdam), Australia (Melbourne and Sydney), Hong Kong, China, Canada (Toronto and Vancouver), and India (Mumbai and Hyderabad) regions.
In addition to the DNS record update, we will be decommissioning legacy DNS records in other regions that are no longer in use.
Effective Date: November 14, 2026
Action Required
To avoid service disruption, we recommend reviewing your CRC endpoint configurations as soon as possible, updating your DNS records with the new entries, and removing the older legacy records before November 14, 2026.If you have any questions or issues, please contact Zoom Support.
DNS Record Updates
Japan Region
We will update the country-level domain and data-center (DC) domains, along with their respective SRV-Records. An example of the change is as follows:zmjp.us >> jp.zoomcrc.com
os.zmjp.us >> kix.zoomcrc.com
ty.zmjp.us >> nrt.zoomcrc.comRecords to be replaced (A-Record and SRV-Record):
zmjp.us:_h323cs._tcp.zmjp.us
_sip._tcp.zmjp.us
_sips._tcp.zmjp.us
_sip._udp.zmjp.usos.zmjp.us:
_h323cs._tcp.os.zmjp.us
_sip._tcp.os.zmjp.us
_sips._tcp.os.zmjp.us
_sip._udp.os.zmjp.usty.zmjp.us:
_h323cs._tcp.ty.zmjp.us
_sip._tcp.ty.zmjp.us
_sips._tcp.ty.zmjp.us
_sip._udp.ty.zmjp.usNew records (A-Record and SRV-Record):
jp.zoomcrc.com:_h323cs._tcp.jp.zoomcrc.com
_sip._tcp.jp.zoomcrc.com
_sips._tcp.jp.zoomcrc.com
_sip._udp.jp.zoomcrc.comkix.zoomcrc.com:
_h323cs._tcp.kix.zoomcrc.com
_sip._tcp.kix.zoomcrc.com
_sips._tcp.kix.zoomcrc.com
_sip._udp.kix.zoomcrc.comnrt.zoomcrc.com:
_h323cs._tcp.nrt.zoomcrc.com
_sip._tcp.nrt.zoomcrc.com
_sips._tcp.nrt.zoomcrc.com
_sip._udp.nrt.zoomcrc.comCanada Region
We will update the country-level domain and data-center (DC) domains, along with their respective SRV-Records. An example of the change is as follows:zmca.us >> ca.zoomcrc.com
tr.zmca.us >> yyz.zoomcrc.com
vn.zmca.us >> yvr.zoomcrc.comRecords to be replaced (A-Record and SRV-Record):
zmca.us:_h323cs._tcp.zmca.us
_sip._tcp.zmca.us
_sips._tcp.zmca.us
_sip._udp.zmca.ustr.zmca.us:
_h323cs._tcp.tr.zmca.us
_sip._tcp.tr.zmca.us
_sips._tcp.tr.zmca.us
_sip._udp.tr.zmca.usvn.zmca.us:
_h323cs._tcp.vn.zmca.us
_sip._tcp.vn.zmca.us
_sips._tcp.vn.zmca.us
_sip._udp.vn.zmca.usNew records (A-Record and SRV-Record):
ca.zoomcrc.com:_h323cs._tcp.ca.zoomcrc.com
_sip._tcp.ca.zoomcrc.com
_sips._tcp.ca.zoomcrc.com
_sip._udp.ca.zoomcrc.comyyz.zoomcrc.com:
_h323cs._tcp.yyz.zoomcrc.com
_sip._tcp.yyz.zoomcrc.com
_sips._tcp.yyz.zoomcrc.com
_sip._udp.yyz.zoomcrc.comyvr.zoomcrc.com:
_h323cs._tcp.yvr.zoomcrc.com
_sip._tcp.yvr.zoomcrc.com
_sips._tcp.yvr.zoomcrc.com
_sip._udp.yvr.zoomcrc.comEU Region
We will update the data-center (DC) domains, along with their respective SRV-Records. An example of the change is as follows:am.zmeu.us >> ams.zoomcrc.com
fr.zmeu.us >> fra.zoomcrc.comRecords to be replaced (A-Record and SRV-Record):
am.zmeu.us:_h323cs._tcp.am.zmeu.us
_sip._tcp.am.zmeu.us
_sips._tcp.am.zmeu.us
_sip._udp.am.zmeu.usfr.zmeu.us:
_h323cs._tcp.fr.zmeu.us
_sip._tcp.fr.zmeu.us
_sips._tcp.fr.zmeu.us
_sip._udp.fr.zmeu.usNew records (A-Record and SRV-Record):
ams.zoomcrc.com:_h323cs._tcp.ams.zoomcrc.com
_sip._tcp.ams.zoomcrc.com
_sips._tcp.ams.zoomcrc.com
_sip._udp.ams.zoomcrc.comfra.zoomcrc.com:
_h323cs._tcp.fra.zoomcrc.com
_sip._tcp.fra.zoomcrc.com
_sips._tcp.fra.zoomcrc.com
_sip._udp.fra.zoomcrc.comDecommisioned Legacy Records
Hosted Zone: zmeu.usA-Records:
sip.zmeu.us
vip2.zmeu.us
sip2.zmeu.us
udp2.zmeu.us
udp.zmeu.usSRV-Records:
_h323cs._tcp.vip2.zmeu.us
_sip._tcp.vip2.zmeu.us
_sips._tcp.vip2.zmeu.us
_sip._udp.vip2.zmeu.usAustralia Region
We will update the country-level domain and data-center (DC) domains, along with their respective SRV-Records. An example of the change is as follows:zmau.us >> au.zoomcrc.com
me.zmau.us >> mel.zoomcrc.com
sy.zmau.us >> syd.zoomcrc.comRecords to be replaced (A-Record and SRV-Record):
zmau.us:_h323cs._tcp.zmau.us
_sip._tcp.zmau.us
_sips._tcp.zmau.us
_sip._udp.zmau.usme.zmau.us:
_h323cs._tcp.me.zmau.us
_sip._tcp.me.zmau.us
_sips._tcp.me.zmau.us
_sip._udp.me.zmau.ussy.zmau.us:
_h323cs._tcp.sy.zmau.us
_sip._tcp.sy.zmau.us
_sips._tcp.sy.zmau.us
_sip._udp.sy.zmau.usNew records (A-Record and SRV-Record):
au.zoomcrc.com:_h323cs._tcp.au.zoomcrc.com
_sip._tcp.au.zoomcrc.com
_sips._tcp.au.zoomcrc.com
_sip._udp.au.zoomcrc.commel.zoomcrc.com:
_h323cs._tcp.mel.zoomcrc.com
_sip._tcp.mel.zoomcrc.com
_sips._tcp.mel.zoomcrc.com
_sip._udp.mel.zoomcrc.comsyd.zoomcrc.com:
_h323cs._tcp.syd.zoomcrc.com
_sip._tcp.syd.zoomcrc.com
_sips._tcp.syd.zoomcrc.com
_sip._udp.syd.zoomcrc.comDecommisioned Legacy Records
Hosted Zone: zmau.usSRV-Records:
_h323cs._tcp.vip2.zmau.us
_sip._tcp.vip2.zmau.us
_sip._tcp.vip2.zmau.us
_sip._udp.vip2.zmau.us
_sips._udp.vip2.zmau.usChina Region
We will update the country-level domain and data-center (DC) domains, along with their respective SRV-Records. An example of the change is as follows:zmcn.us >> cn.zoomcrc.com
Records to be replaced (A-Record and SRV-Record):
zmcn.us:_h323cs._tcp.zmcn.us
_sip._tcp.zmcn.us
_sips._tcp.zmcn.us
_sip._udp.zmcn.usNew records (A-Record and SRV-Record):
cn.zoomcrc.com:_h323cs._tcp.cn.zoomcrc.com
_sip._tcp.cn.zoomcrc.com
_sips._tcp.cn.zoomcrc.com
_sip._udp.cn.zoomcrc.comDecommisioned Legacy Records
Hosted Zone: zmcn.usA-Records:
udp.zmcn.us
udp2.zmcn.us
vip2.zmcn.us
sip2.zmcn.us
sip.zmcn.usSRV-Records:
_h323cs._tcp.vip2.zmcn.us
_sip._tcp.vip2.zmcn.us
_sips._tcp.vip2.zmcn.us
_sip._udp.vip2.zmcn.usHong Kong Region
We will update the country-level domain and data-center (DC) domains, along with their respective SRV-Records. An example of the change is as follows:zmhk.us >> hkg.zoomcrc.com
Records to be replaced (A-Record and SRV-Record):
zmhk.us:_h323cs._tcp.zmhk.us
_sip._tcp.zmhk.us
_sips._tcp.zmhk.us
_sip._udp.zmhk.usNew records (A-Record and SRV-Record):
hkg.zoomcrc.com:_h323cs._tcp.hkg.zoomcrc.com
_sip._tcp.hkg.zoomcrc.com
_sips._tcp.hkg.zoomcrc.com
_sip._udp.hkg.zoomcrc.comDecommisioned Legacy Records
Hosted Zone: zmhk.usA-Records:
vip2.zmhk.us
udp2.zmhk.us
sip2.zmhk.us
udp.zmhk.us
sip.zmhk.usSRV-Records:
_sip._tcp.vip2.zmhk.us
_sip._udp.vip2.zmhk.us
_sips._tcp.vip2.zmhk.us
_h323cs._tcp.vip2.zmhk.usIndia Region
We will update the country-level domain and data-center (DC) domains, along with their respective SRV-Records. An example of the change is as follows:zmin.us >> in.zoomcrc.com
hy.zmin.us >> hy2.zoomcrc.com
mb.zmin.us >> mb2.zoomcrc.comRecords to be replaced (A-Record and SRV-Record):
zmin.us:_h323cs._tcp.zmin.us
_sip._tcp.zmin.us
_sips._tcp.zmin.us
_sip._udp.zmin.ushy.zmin.us:
_h323cs._tcp.hy.zmin.us
_sip._tcp.hy.zmin.us
_sips._tcp.hy.zmin.us
_sip._udp.hy.zmin.usmb.zmin.us:
_h323cs._tcp.mb.zmin.us
_sip._tcp.mb.zmin.us
_sips._tcp.mb.zmin.us
_sip._udp.mb.zmin.usNew records (A-Record and SRV-Record):
in.zoomcrc.com:_h323cs._tcp.in.zoomcrc.com
_sip._tcp.in.zoomcrc.com
_sips._tcp.in.zoomcrc.com
_sip._udp.in.zoomcrc.comhy2.zoomcrc.com:
_h323cs._tcp.hy2.zoomcrc.com
_sip._tcp.hy2.zoomcrc.com
_sips._tcp.hy2.zoomcrc.com
_sip._udp.hy2.zoomcrc.commb2.zoomcrc.com:
_h323cs._tcp.mb2.zoomcrc.com
_sip._tcp.mb2.zoomcrc.com
_sips._tcp.mb2.zoomcrc.com
_sip._udp.mb2.zoomcrc.comDecommisioned Legacy Records
Hosted Zone: zmin.usA-Records:
vip2.zmin.us
udp2.zmin.us
udp.zmin.us
sip2.zmin.us
sip.zmin.usSRV-Records:
_sips._tcp.vip2.zmin.us
_sip._udp.vip2.zmin.us
_sip._tcp.vip2.zmin.us
_h323cs._tcp.vip2.zmin.us
Changes Rewindex caught on this incident
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
f29b5ea6c5b0d1f9…
Rewindex captured a newer version after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).