VoIP.infoThe independent guide to business communications.
VoIP.info Guide

DNS for SIP phones and trunks

Understand why a working IP connection can still fail to locate the intended calling service.

Reviewed 2026-10-26Foundational

Names are part of the deployment

Phones and PBXs can use DNS to locate registrars, proxies and supporting services. SIP server discovery can involve records beyond a simple host address, depending on URI, transport and implementation behavior. Confirm what the endpoint actually queries.

Diagnose at the failing client

Compare resolution from the phone's or PBX's configured resolver, not only from an administrator's laptop. Split DNS, VPN routing and cached answers can produce different destinations. Check both address family and selected transport.

Avoid a misleading workaround

Replacing a hostname with a fixed IP can bypass service discovery, failover and TLS identity expectations. Use it only as a bounded diagnostic when appropriate, then restore the supported naming design. A carrier's current address may not be its permanent service contract.

Validate changes over time

Record relevant TTLs and observe recovery after cache expiry or controlled resolver changes. Test incoming and outgoing behavior independently. Keep certificate names aligned with the configured service identity, and include DNS availability in the PBX recovery plan.

Diagnose the resolver Asterisk actually uses

For PJSIP, the Asterisk DNS guide separates authoritative data, recursive cache, resolver module, URI-driven SRV query, live transport connection and registration state. A command-line lookup from the same host is a control, not proof of the application's resolver path.

Compare authoritative, recursive and application cache state

The provider DNS diagnostic preserves each TTL and cache owner before a flush or restart.

Correlate Blink registration with the exact DNS answer set

The Blink registration diagnostic records discovery, selected address and retry-time resolution rather than pinning one observed server.

Preserve Commio names, answers and TTL at the failed time

The Commio route diagnostic keeps account-assigned hostnames, resolver evidence and route order distinct.

Bind Jitsi Desktop DNS evidence to the configured registrar

The Jitsi Desktop diagnostic records host, address family, answer and route before changing SIP credentials.

Resolve the endpoint time-server name at the observation time

The wrong-time diagnostic retains answers, TTLs, selected destination, request and response rather than inferring synchronization from DNS.

Do not confuse Sipnetic DNS over TLS with SIP over TLS

Sipnetic's Network setting protects the DNS resolver exchange when configured successfully. The Sipnetic diagnostic then checks SIP discovery, selected destination and SIP certificate trust as later stages.

Follow Orange DNS answers to the selected service target

The Orange Business Talk diagnostic preserves query, answer, selected target, certificate identity and first SIP transaction.

Correlate Vodafone DNS with the selected endpoint

The Vodafone Evolved Voice diagnostic preserves query, answer, selected target, transport and first SIP transaction.

Correlate Swisscom names with the ordered handoff

The Swisscom Enterprise SIP diagnostic preserves query, answer, selected peer, route and first signaling transaction rather than importing another offer.

Correlate Sunrise names with the ordered peer

The Sunrise Business Voice SIP diagnostic preserves query, answer, selected peer, route and first signaling transaction.

Correlate Proximus targets with the selected mode

The Proximus Business Trunking diagnostic preserves name resolution, network SBC selection, route and first SIP transaction.

Keep Crazytel SIP address and outbound proxy distinct

The Crazytel SIP trunk diagnostic preserves resolver answers, server field, regional proxy, route and selected edge.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Continue your research

Hub

VoIP networking

Trace signaling and audio through your actual topology before changing ports or prioritization.

Explore topic →
Troubleshooting · Asterisk 22 LTS · FreePBX 17 / Debian 12 checks

One-way VoIP audio

Trace the missing direction from advertised media address to receiving endpoint.

Read guide →
Interactive tool

VoIP bandwidth calculator

Estimate IP-layer voice traffic per direction from codec rate, packet duration and concurrent calls.

Open tool →
Reference · SIP standards; extension support depends on both peers

SIP DNS discovery: NAPTR, SRV and address records

Understand service selection and failover before hard-coding a SIP server IP address.

Read guide →
Guide · Current Asterisk PJSIP transport-selection, DNS API, res_resolver_unbound and outbound-registration documentation plus RFC 3263 and RFC 2782 were reviewed October 8, 2026; no Asterisk or FreePBX host, resolver, nameserver, DNS zone, cache, URI, proxy, registrar, transport, connection, registration, request, failover event, availability, compatibility or call was inspected or tested

Asterisk PJSIP DNS resolution: SRV, TTL and live-state boundaries

Trace a SIP URI through Asterisk's resolver, SRV selection, address family, transport and live registration state without treating a DNS edit as immediate failover.

Read guide →
Diagnostic · Current Asterisk PJSIP transport-selection, DNS API, res_resolver_unbound and outbound-registration documentation plus RFC 3263 and RFC 2782 were reviewed October 8, 2026; no Asterisk or FreePBX host, resolver, nameserver, DNS zone, cache, URI, proxy, registrar, transport, connection, registration, request, failover event, availability, compatibility or call was inspected or tested

Asterisk PJSIP keeps using the old DNS target

Compare authoritative and recursive DNS, the exact PJSIP query path, TTL, selected target, live connection and registration retry state before flushing caches or restarting Asterisk.

Read guide →
Troubleshooting · Voip Unlimited SIP-trunk DNS descriptions and RFC 3263, RFC 2782 and RFC 3403 reviewed October 13, 2026; the exact account, service FQDN, URI, transport, port, resolver, NAPTR, SRV, address answers, TTL, client support, cached state, first target, failure class, next transaction, provider edge, PBX route and recovery remain deployment specific, and no account, resolver, PBX, SBC, packet, request, response, call, failover event or media stream was inspected or tested

Voip Unlimited SIP DNS failover does not try the next target

Trace one new SIP request from URI and client discovery behavior through NAPTR, SRV, address records, cached state, selected transport, qualifying failure and the next transaction.

Read guide →
Client research · Current Blink Windows/Linux manual pages for SIP accounts, the main interface, incoming-call alerts and audio calls, the platform-specific changelog, and RFC 3261 response and proxy-processing rules reviewed October 14, 2026; the documentation describes Blink sending 603 for Reject, 486 for Busy, and no SIP response when Escape only silences the local alert, but it does not prove the selected package, account, registrar, proxy, forked branches, PBX response handling, voicemail policy, forwarding policy or observed call result, and no package, workstation, account, credential, SIP trace, PBX, provider, branch, forwarding rule, voicemail destination, alert action or live call was inspected or tested; registration timeout, explicit service-unavailable and retry evidence refreshed October 19, 2026

Blink softphone: platform tracks, SIP accounts and negotiated protection

Evaluate AG Projects' separate Windows, Linux, Blink Pro for Mac and Mac beta artifacts, local SIP account ownership and negotiated protection.

Read guide →
Troubleshooting · Current first-party Blink product, account, troubleshooting, download and platform-changelog pages plus RFC 3261, RFC 3263 and RFC 5626 were reviewed October 19, 2026. Product track, operating system, package, SIP account, DNS answers, proxy override, transport, network policy, server response, retry timing and call behavior remain deployment specific. No package, workstation, account, credential, DNS answer, proxy, registrar, firewall, NAT device, SIP trace, packet, media stream or live call was inspected or tested

Blink registration shows 408 timeout, 503 unavailable or stays gray

Trace Blink account identity, DNS or manual proxy selection, transport, network reachability, SIP response and retry timing before changing codecs or security settings.

Read guide →
Provider research · Current first-party Commio outbound-trunk, inbound-routing, technical, identity, E911, number-management, porting and product material was reviewed October 23, 2026. Outbound trunk source authorization and optional Request-URI prefix, outbound routing profile, inbound number status, inbound routing preference, provider attempt, customer-edge receipt, PBX match, answer and media remain separate evidence. Documented propagation, route-advance, codec, port, capacity and emergency values require confirmation against the selected account and observed transaction. No Commio account, trunk, source address, prefix, routing profile, number, port order, caller identity, E911 site, PBX, DNS answer, firewall, packet, CDR, call, media stream, failover event, price, capacity, availability, compatibility or support response was inspected or tested

Commio SIP trunking: source IP, prefix, inbound routing and call evidence

Separate outbound source-IP and prefix authorization, routing profiles, inbound number destinations, caller identity, media and observed call results.

Read guide →
Troubleshooting · Commio's live inbound-routing, outbound-trunk, technical FAQ, INVITE, outbound-routing, E911 and support material was reviewed October 20, 2026. Exact account, number, active profile, route type, DNS answer, provider edge, source IP, PBX, response, timeout, channel control, emergency record and media path remain deployment specific. No Commio account, trunk, number, route, DNS answer, PBX, packet, response, media stream, emergency call, availability, compatibility, price or support response was inspected or tested

Commio inbound route does not advance or skips a backup

Trace one inbound number through its active profile, ordered destination types, DNS result, provider attempt and exact SIP response before changing the PBX.

Read guide →
Client research · The official Jitsi Desktop repository, release archive, legacy download and setup pages, historical product site, Jitsi security clarification, Jitsi Meet Electron repository and jit.si account end-of-life notice were reviewed October 23, 2026. Jitsi Desktop, Jitsi Meet and Jitsi Meet Electron are separate products. The Desktop repository says the SIP/XMPP client is not actively developed and that builds depend on community contributions. GitHub release labels are non-monotonic: 2.8.5426 carries the Latest badge, 2.10.5550 is a later-numbered release, and 2.11.5633 is marked pre-release. Exact artifact, tag, operating system, package channel, Java runtime, account, registrar, transport, certificate result, negotiated media and completed call remain separate evidence. Historical feature or security claims do not establish present support, vulnerability status, service compatibility or encryption. The old jit.si account service ended June 1, 2016. No installer, package, checksum, signature, operating system, Java runtime, account, credential, registrar, PBX, DNS answer, firewall, NAT path, certificate, microphone, speaker, headset, SDP, RTP stream, encrypted session, emergency workflow, price, availability, compatibility, support response or call was inspected or tested

Jitsi Desktop: legacy SIP client, release and security boundaries

Treat Jitsi Desktop as a community-maintained legacy SIP/XMPP client, distinct from Jitsi Meet, and bind every installer, account, certificate and media result to exact evidence.

Read guide →
Troubleshooting · The official Jitsi Desktop repository, release archive, legacy download and setup pages, historical product site, Jitsi security clarification, Jitsi Meet Electron repository and jit.si account end-of-life notice were reviewed October 23, 2026. Jitsi Desktop, Jitsi Meet and Jitsi Meet Electron are separate products. The Desktop repository says the SIP/XMPP client is not actively developed and that builds depend on community contributions. GitHub release labels are non-monotonic: 2.8.5426 carries the Latest badge, 2.10.5550 is a later-numbered release, and 2.11.5633 is marked pre-release. Exact artifact, tag, operating system, package channel, Java runtime, account, registrar, transport, certificate result, negotiated media and completed call remain separate evidence. Historical feature or security claims do not establish present support, vulnerability status, service compatibility or encryption. The old jit.si account service ended June 1, 2016. No installer, package, checksum, signature, operating system, Java runtime, account, credential, registrar, PBX, DNS answer, firewall, NAT path, certificate, microphone, speaker, headset, SDP, RTP stream, encrypted session, emergency workflow, price, availability, compatibility, support response or call was inspected or tested

Jitsi Desktop SIP registers but call, audio or certificate fails

Find the first mismatch in legacy-client identity, exact release, current SIP account, DNS and network path, certificate validation, call signaling, audio device or negotiated media.

Read guide →
Provisioning guide · Current NTP standards, best-current-practice, DHCP-option, Network Time Security, Yealink, Grandstream and Cisco endpoint documentation was reviewed October 24, 2026. UTC synchronization, displayed local time, time-zone and daylight-saving policy, manual time, DHCP options, configured servers, DNS answers, selected source, last successful synchronization, authenticated-time support, certificate validity, log timestamps and scheduled behavior remain separate evidence. Vendor examples, defaults, intervals and supported controls are model- and firmware-specific documentation rather than proof of an installed setting or result. No phone, base, PBX, DHCP server, DNS resolver, NTP server, NTS service, key, certificate, firewall, packet, provisioning job, scheduled task, call, alert, clock offset, availability, compatibility or support response was inspected or tested

IP phone NTP, time-zone and daylight-saving evidence

Separate clock synchronization from displayed local time, DHCP overrides, manual settings, authenticated time, certificate validity, logs and scheduled endpoint behavior.

Read guide →
Troubleshooting · Current NTP standards, best-current-practice, DHCP-option, Network Time Security, Yealink, Grandstream and Cisco endpoint documentation was reviewed October 24, 2026. UTC synchronization, displayed local time, time-zone and daylight-saving policy, manual time, DHCP options, configured servers, DNS answers, selected source, last successful synchronization, authenticated-time support, certificate validity, log timestamps and scheduled behavior remain separate evidence. Vendor examples, defaults, intervals and supported controls are model- and firmware-specific documentation rather than proof of an installed setting or result. No phone, base, PBX, DHCP server, DNS resolver, NTP server, NTS service, key, certificate, firewall, packet, provisioning job, scheduled task, call, alert, clock offset, availability, compatibility or support response was inspected or tested

IP phone time is wrong, scheduled behavior drifts or certificates fail

Find the first mismatch across DHCP, DNS, NTP reachability, source selection, UTC, time zone, daylight saving, manual overrides, certificate validity and device scheduling.

Read guide →
Client research · Sipnetic's developer site and Google Play listing, the September 25, 2026 Play update note, Android 16 change summary, DNS-over-TLS, SIP discovery, SIP, SIP-domain-certificate and TLS specifications were reviewed October 25, 2026. The Play update note does not publish one numeric installed build, and Android, device-vendor, SIP-service, PBX, resolver, entitlement and network behavior remain deployment specific. No application package, installation, device, Android build, account, QR artifact, credential, DNS answer, resolver, proxy, registrar, transport, certificate, REGISTER exchange, packet, media stream, privacy behavior, entitlement, emergency route or live call was inspected or tested

Sipnetic for Android: Android 16, DNS-over-TLS and SIP evidence

Evaluate the September 25, 2026 Android update while keeping the installed build, DNS privacy, SIP discovery, signaling transport, registration, media and background delivery separately observable.

Read guide →
Troubleshooting · Sipnetic's developer site and Google Play listing, the September 25, 2026 Play update note, Android 16 change summary, DNS-over-TLS, SIP discovery, SIP, SIP-domain-certificate and TLS specifications were reviewed October 25, 2026. The Play update note does not publish one numeric installed build, and Android, device-vendor, SIP-service, PBX, resolver, entitlement and network behavior remain deployment specific. No application package, installation, device, Android build, account, QR artifact, credential, DNS answer, resolver, proxy, registrar, transport, certificate, REGISTER exchange, packet, media stream, privacy behavior, entitlement, emergency route or live call was inspected or tested

Sipnetic registration or calls fail after Android 16 or DNS-over-TLS change

Locate the first changed state across package, Android runtime, DNS privacy service, SIP discovery, transport and trust, registration, call signaling, background delivery and media.

Read guide →
Provider research · Orange Business Talk product, service-document index, site-management assistance, certified eSBC and ecosystem guides and enterprise-voice material reviewed October 25, 2026; the selected country, order, site, access model, project documents and certified version govern, while the October 25, 2024 Patton guide remains guide-scoped evidence; no Orange account, order, portal, site, trunk, circuit, DNS answer, clock, certificate, SBC, PBX, number, route, packet, call, fax, media stream, failover event, emergency result, price, availability, compatibility or support response was inspected or tested

Orange Business Talk: site, eSBC, routing and media evidence

Qualify the ordered Business Talk or Business Talk IP site, access model, certified eSBC guide, routing policy and media behavior without treating one template as universal service state.

Read guide →
Troubleshooting · Orange Business Talk product, service-document index, site-management assistance, certified eSBC and ecosystem guides and enterprise-voice material reviewed October 25, 2026; the selected country, order, site, access model, project documents and certified version govern, while the October 25, 2024 Patton guide remains guide-scoped evidence; no Orange account, order, portal, site, trunk, circuit, DNS answer, clock, certificate, SBC, PBX, number, route, packet, call, fax, media stream, failover event, emergency result, price, availability, compatibility or support response was inspected or tested

Orange Business Talk site, trunk, routing or media is wrong

Find the first divergence across ordered site state, portal activation, DNS, time, certificate, eSBC guide, SIP routing and negotiated media.

Read guide →
Provider research · Vodafone UK SIP-trunking product material, 2019 Converged Hybrid/Evolved Voice terms, current Vodafone storm terms, Hybrid Voice data sheet, tiered-support brochure and Vodafone Business UC terms were reviewed October 25, 2026; Vodafone Evolved Voice over Public Internet, Hybrid Voice, Vodafone Global SIP Trunking and storm SIP Trunking remain separate service identities, and the selected current order, site, access, number inventory, endpoint design and acceptance record govern; no Vodafone account, order, site, circuit, endpoint, SBC, PBX, address, number, port, trunk, call, packet, media stream, failover event, fraud alert, emergency result, price, availability, compatibility or support response was inspected or tested

Vodafone Evolved Voice: public-internet access, continuity and service boundaries

Evaluate Vodafone Evolved Voice over Public Internet without importing Hybrid Voice, GSIP or storm behavior, and keep order, access, endpoint, number, security, failover and emergency evidence separate.

Read guide →
Troubleshooting · Vodafone UK SIP-trunking product material, 2019 Converged Hybrid/Evolved Voice terms, current Vodafone storm terms, Hybrid Voice data sheet, tiered-support brochure and Vodafone Business UC terms were reviewed October 25, 2026; Vodafone Evolved Voice over Public Internet, Hybrid Voice, Vodafone Global SIP Trunking and storm SIP Trunking remain separate service identities, and the selected current order, site, access, number inventory, endpoint design and acceptance record govern; no Vodafone account, order, site, circuit, endpoint, SBC, PBX, address, number, port, trunk, call, packet, media stream, failover event, fraud alert, emergency result, price, availability, compatibility or support response was inspected or tested

Vodafone Evolved Voice trunk is down or calls fail

Find the first divergence across the exact Vodafone service, order, public access, endpoint diversity, number state, edge receipt, PBX routing, security and media.

Read guide →
Provider research · Swisscom Enterprise SIP product material, Enterprise SIP and Enterprise SIP Cloud factsheets, the July 2026 PBX compatibility list and Enterprise Connect operating documentation were reviewed October 25, 2026; Enterprise SIP, Enterprise SIP Cloud, Smart Business Connect and Enterprise Connect SIP-Trunk remain distinct service identities, and the selected current order, access variant, eSBC or SBC boundary, number inventory, PBX version and acceptance record govern; no Swisscom account, order, site, circuit, MPLS path, router, firewall, eSBC, SBC, PBX, address, number, port, trunk, channel, call, packet, media stream, failover event, emergency result, price, availability, compatibility or support response was inspected or tested

Swisscom Enterprise SIP: access, eSBC, continuity and service boundaries

Evaluate Swisscom Enterprise SIP without merging Enterprise SIP Cloud, Smart Business Connect or Enterprise Connect behavior, and keep access, eSBC, PBX, number, security, continuity and emergency evidence separate.

Read guide →
Troubleshooting · Swisscom Enterprise SIP product material, Enterprise SIP and Enterprise SIP Cloud factsheets, the July 2026 PBX compatibility list and Enterprise Connect operating documentation were reviewed October 25, 2026; Enterprise SIP, Enterprise SIP Cloud, Smart Business Connect and Enterprise Connect SIP-Trunk remain distinct service identities, and the selected current order, access variant, eSBC or SBC boundary, number inventory, PBX version and acceptance record govern; no Swisscom account, order, site, circuit, MPLS path, router, firewall, eSBC, SBC, PBX, address, number, port, trunk, channel, call, packet, media stream, failover event, emergency result, price, availability, compatibility or support response was inspected or tested

Swisscom Enterprise SIP trunk is down or calls fail

Find the first divergence across the exact Swisscom service, access variant, service access point, eSBC or SBC, PBX version, number state, routing option, signaling and media.

Read guide →
Provider research · Current Sunrise Business Voice SIP and portfolio pages plus dated 2016, 2017, 2018 and 2021 Sunrise documents were reviewed October 25, 2026. Business Voice SIP, Business Voice Direct, Business Voice for Microsoft Teams and Cloud Connect for Webex Calling remain separate offers; dated examples are not universal current settings. No Sunrise account, order, site, circuit, Internet or VPN path, router, firewall, SBC, PBX, address, number, port, trunk, channel, call, fax, packet, media stream, backup or emergency result, price, availability, compatibility or support response was inspected or tested

Sunrise Business Voice SIP: access, PBX and continuity boundaries

Evaluate Sunrise Business Voice SIP without importing Business Voice Direct, Microsoft Teams or Webex behavior, and keep package, access, peer, PBX, number, media and continuity evidence separate.

Read guide →
Troubleshooting · Current Sunrise Business Voice SIP and portfolio pages plus dated 2016, 2017, 2018 and 2021 Sunrise documents were reviewed October 25, 2026. Business Voice SIP, Business Voice Direct, Business Voice for Microsoft Teams and Cloud Connect for Webex Calling remain separate offers; dated examples are not universal current settings. No Sunrise account, order, site, circuit, Internet or VPN path, router, firewall, SBC, PBX, address, number, port, trunk, channel, call, fax, packet, media stream, backup or emergency result, price, availability, compatibility or support response was inspected or tested

Sunrise Business Voice SIP trunk is down or calls fail

Find the first divergence across the exact Sunrise service and package, access path, peer model, PBX, number state, signaling, fax, media and continuity.

Read guide →
Provider research · The current Proximus product page, 15 January 2024 Business Trunking contractual service description, 1 January 2026 contract summary, legal-document index and large-organisation support page were reviewed October 25, 2026. Multi Standard, Multi Converged, Cloud Basic and Cloud Advanced retain different access, CPE and SBC scopes; the selected order and implementation records govern. No Proximus or BICS account, order, site, Explore path, access line, CPE, SBC, PBX, number, channel, call, packet, fax, media stream, redundancy event, emergency result, price, availability, compatibility or support response was inspected or tested

Proximus Business Trunking: flavour, SBC and service-boundary evidence

Evaluate Proximus Business Trunking without merging adjacent voice offers, and keep flavour, access, CPE, SBC, PBX, number, channel, redundancy, media and emergency evidence separate.

Read guide →
Troubleshooting · The current Proximus product page, 15 January 2024 Business Trunking contractual service description, 1 January 2026 contract summary, legal-document index and large-organisation support page were reviewed October 25, 2026. Multi Standard, Multi Converged, Cloud Basic and Cloud Advanced retain different access, CPE and SBC scopes; the selected order and implementation records govern. No Proximus or BICS account, order, site, Explore path, access line, CPE, SBC, PBX, number, channel, call, packet, fax, media stream, redundancy event, emergency result, price, availability, compatibility or support response was inspected or tested

Proximus Business Trunking is down or calls fail

Find the first divergence across the ordered flavour, access, CPE, SBC, PBX, number, channel, signaling, fax, media, redundancy and emergency boundaries.

Read guide →
Provider research · Crazytel Business SIP Trunking product and support records were reviewed October 26, 2026. Register-based, IP-authenticated, standard, Hybrid, CrazyPBX and call-centre services retain different authentication, transport, encryption, routing and commercial boundaries; the selected portal configuration and current order govern. No Crazytel account, trunk, credential, public IP, DID, caller ID, PBX, device, PoP, route, codec negotiation, packet, call, audio, failover, emergency outcome, price, availability, compatibility, status incident or support response was inspected or tested

Crazytel SIP Trunking: authentication, media and service-boundary evidence

Evaluate Crazytel Business SIP Trunking without merging registration, IP authentication, standard, Hybrid or CrazyPBX behavior, and keep portal, network, call and media evidence separate.

Read guide →
Troubleshooting · Crazytel Business SIP Trunking product and support records were reviewed October 26, 2026. Register-based, IP-authenticated, standard, Hybrid, CrazyPBX and call-centre services retain different authentication, transport, encryption, routing and commercial boundaries; the selected portal configuration and current order govern. No Crazytel account, trunk, credential, public IP, DID, caller ID, PBX, device, PoP, route, codec negotiation, packet, call, audio, failover, emergency outcome, price, availability, compatibility, status incident or support response was inspected or tested

Crazytel SIP trunk is down or calls fail

Find the first divergence across product, authentication, registration, public IP, DNS, proxy, PoP, DID, caller ID, channel, signaling, media, failover and emergency boundaries.

Read guide →