Home / Registration, DNS, and routing / Locating a server with RFC 3263
Locating a server with RFC 3263
RFC 3263 turns a SIP domain into a transport, a port, and an address with NAPTR, SRV, and A or AAAA.
Learn in 5 minutes
- Order NAPTR, then SRV, then A or AAAA
- Name the SIP+D2U, SIP+D2T, and SIPS+D2T services
- Skip the name lookup when the Request-URI is already an IP address
Visual
An explicit transport or port skips the records that are no longer needed. A numeric IP skips the name.
Worked example
What happened before the INVITE The first note states the DNS result. The SIP itself contains no NAPTR records.
- Read the first hop note.
- Inspect the INVITE Request-URI.
- Name the record that would have supplied a port.
Fault
The peer moved in DNS. The SBC still sends to 192.0.2.40 because the dial-peer target is a literal address. Calls time out.
RFC 3263 runs on a domain. An address skips it.
Quiz
Ecosystem
Glossary, sister systems, and the integration seam for this room.
Quality management and recording QM scores interactions. The standardized way an SBC forks a session to a recorder is SIPREC.
Sources and go deeper
- RFC 3263 — last checked 2026-10
- RFC 3261 §18 — last checked 2026-10
- RFC 5737 — last checked 2026-10
- Cisco CUBE basic SIP configuration — last checked 2026-10