Skip to content
Phone Guides

Check DNS and SRV dependencies before changing voice discovery

List the SIP service names configured on phones, the A or AAAA records they resolve to, and any SRV targets, priorities, weights and ports. Check the provider’s current documentation.

DNS and SRV dependencies before changing voice discovery

  1. Save existing records and note TTLs before changing them. Plan tests from the voice VLAN’s resolver, not only from an administrator’s laptop.
  2. Agree on a fallback and a time window that allows cached answers to expire. Test registration and a call after the new answer is visible.

A healthy web lookup does not prove phones see the same DNS answer.

Check the wider path

Check every target named by an SRV answer, not only the record itself. Phones still need a usable address and transport to that target. Note whether IPv6 answers are published and supported on the route before assuming a dual-stack result.

Use the DNS and SRV records for VoIP to confirm terms and settings before the change.