112NG112.netNext generation emergency communications

NG112 reference

Dns Service Discovery

Structured NG112 reference page.

112 readiness

Policy, location, routing, and response quality connected in one operational model.

Core NG112 Architecture

DNS and Service Discovery

Emergency services depend on naming and discovery just like other IP services, but failure consequences are different. DNS design must account for resilience, split-horizon behavior, certificate names, disaster recovery and operational change control.

Emergency function name
->
DNS/service discovery
->
Reachable routing target
->
Session delivery

What it does

DNS and service discovery support reliable discovery of emergency services, routing elements and dependent network functions where architectures use them.

Naming and discovery glue together SIP routing, secure interconnect and service reachability.

How it works

  • Resolves service names or routing targets used by emergency systems.
  • Supports redundant endpoints and regional failover.
  • Aligns certificate identity with actual service names.

Key interfaces and protocols

  • DNS
  • NAPTR/SRV concepts where used
  • TLS certificate validation
  • Operational monitoring

Systems it interacts with

  • ESRP
  • BCF
  • ESInet
  • PSAP edge
  • Monitoring

Common failure modes

  • Stale records after failover
  • Certificate name mismatch
  • Resolver isolation
  • Untracked dependency on public DNS

Implementation considerations

  • Document authoritative DNS ownership.
  • Test resolver behavior during regional outage.
  • Avoid hidden single points of failure in naming.

Standards

  • IETF DNS and SIP service discovery practices
  • ETSI architecture references

Related NG112 technologies

Related country deployments

No country deployments are listed here until independently verified against official or high-confidence sources.

Related articles

Sources

Last verified: 2026-08-31

Advertisement