GSM Association Non-confidential

Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

DNS and ENUM Guidelines for Service Providers and GRX

and IPX Providers
Version 15.0
29 June 2018

This is a Non-binding Permanent Reference Document of the GSMA

Security Classification: Non-confidential

Access to and distribution of this document is restricted to the persons permitted by the security classification. This document is confidential to the
Association and is subject to copyright protection. This document is to be used only for the purposes for which it has been supplied and
information contained in it must not be disclosed or in any other way made available, in whole or in part, to persons other than those permitted
under the security classification without the prior written approval of the Association.

Copyright Notice
Copyright © 2018 GSM Association

Disclaimer
The GSM Association (“Association”) makes no representation, warranty or undertaking (express or implied) with respect to and does not accept
any responsibility for, and hereby disclaims liability for the accuracy or completeness or timeliness of the information contained in this document.
The information contained in this document may be subject to change without prior notice.

Antitrust Notice
The information contain herein is in full compliance with the GSM Association’s antitrust compliance policy.

V15.0 Page 1 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

Table of Contents
1 Introduction 5
1.1 Overview 5
1.2 Scope 5
1.3 Document Cross-References 5
2 DNS As Used on the GRX/IPX 8
2.1 Introduction 8
2.2 Architecture 8
2.3 Domains 14
2.3.1 Introduction 14
2.3.2 General 14
2.3.3 Domain names used on the GRX/IPX DNS 15
2.3.4 Domain names used on the Internet DNS (and owned by GSMA) 24
2.3.5 Domain names used on the GRX/IPX DNS for UNI 31
2.4 Non-service specific hostnames and domains 31
2.5 Host names for the evolved packet Core (EPC) 32
2.6 Host names for the IP Multimedia Subsystem (IMS) 32
3 General DNS Configuration for Service Providers 32
3.1 Introduction 32
3.2 DNS Server Hardware 32
3.3 DNS Server Software 33
3.4 DNS Server naming 33
3.5 Domain Caching 33
3.6 Reverse Mapping 33
3.7 Use of DNS Interrogation Modes 34
3.8 Use of the GRX/IPX Root DNS Server 34
3.9 Provisioning of Service Provider's DNS servers 35
3.10 Resource Records 35
3.11 Support for IPv4 and IPv6 36
4 DNS Aspects for Standardised Services 36
4.1 Introduction 36
4.2 General Packet Radio Service (GPRS) 36
4.2.1 Introduction 36
4.2.2 APN resolution in PDP Context activation 36
4.2.3 Inter-SGSN handovers for active PDP Contexts 38
4.3 Multi-media Messaging Service (MMS) 40
4.3.1 Introduction 40
4.3.2 MM delivery based on MSISDN for the Direct Interconnect model 40
4.3.3 MM delivery based on MSISDN for the Indirect Interconnect model 42
4.3.4 MM delivery based on NAI/e-mail address 43
4.4 WLAN Inter-working 43
4.4.1 Introduction 43
4.5 IP Multi-media core network Sub-system (IMS) 44

V15.0 Page 2 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

4.5.1 Introduction 44
4.5.2 SIP server configuration 45
4.5.3 Domain Names used 47
4.6 Generic Authentication Architecture (GAA) 47
4.6.1 Introduction 47
4.7 Generic Access Network (GAN) 48
4.7.1 Introduction 48
4.8 Secure User Plane Location (SUPL) 48
4.8.1 Introduction 48
4.9 Enhanced Packet Core (EPC) 48
4.9.1 Introduction 48
4.10 IMS Centralised Services (ICS) 48
4.10.1 Introduction 48
4.11 Access Network Discovery Support Function (ANDSF) 48
4.11.1 Introduction 48
4.12 Mobile Broadcast Services (BCAST) 49
4.12.1 Introduction 49
4.13 The XCAP Root URI on Ut Interface for MMTEL/IMS profile for Voice and
SMS (XCAP) 49
4.13.1 Introduction 49
4.14 RCS - Rich Communication Suite 49
4.14.1 Introduction 49
4.15 Evolved Packet Data Gateway (ePDG) 50
4.15.1 Introduction 50
4.16 Network element self-configuration 50
4.16.1 Introduction 50
4.17 EPC and GPRS coexistence 50
4.17.1 Introduction 50
4.18 MBMS Service Announcement Bootstrapping 50
4.18.1 Introduction 50
5 Processes and Procedures relating to DNS 50
5.1 Introduction 50
5.2 Existing domains/sub-domains on the GRX/IPX network and their
Allocation 50
5.3 Procedures relating to new domain names on the GRX/IPX network 51
5.4 Description of the Master Root DNS service and modality of access 52
5.4.1 Master Root DNS services 52
5.4.2 Master Root DNS services 52
5.4.3 How to access Master Root DNS services 52
5.5 Delegation of sub-domains of “pub.3gppnetwork.org” 53
Annex A Sample BIND DNS Configuration for GPRS 55
A.1 Introduction 55
A.2 The "named.conf" file 55
A.2.1 The "named.conf" file for a PLMN Master Nameserver 55

V15.0 Page 3 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

A.2.2 The "named.conf" file for a PLMN Slave Nameserver 56

A.3 Zone Configuration Files 56
A.3.1 The "gprs.hint" file 56
A.3.2 The "0.0.127.in-addr.arpa" file 57
A.3.3 PLMN zone files 57
A.3.4 The "hosts" file 57
A.3.5 The "168.192.in-addr.arpa" file 59
Annex B Forms for transfer of sub-domain of “pub.3gppnetwork.org” 60
B.1 Request form 60
B.2 Letter of Authorization Template 62
Annex C Document Management 65
C.1 Document History 65
C.2 Other Information 71

V15.0 Page 4 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

1 Introduction
1.1 Overview
Inter Service Provider IP communications are starting to evolve to support services other
than GPRS Roaming. Many, if not all, of these services rely upon DNS. Therefore, it is of
utmost importance for the interworking and stability of such services that Service Providers
have all the necessary information to hand to ease configuration of their DNS servers upon
which such services rely.

This document is intended to provide guidelines and technical information for those who
need to set up and/or maintain DNS servers for inter Service Provider services. This
document is not intended to provide a general education on DNS. Thus, a reasonable level
of technical competence in DNS, and DNS server configuration is assumed throughout this
document.

1.2 Scope
This GSMA official document provides recommendations on DNS to facilitate successful
interworking of inter-Service Provider services. In particular, guidelines for general and
service specific configuration of DNS servers, GSMA processes and procedures relating to
formats, usage of domain names and sub-domain names, and updates to the GRX/IPX
Root DNS Server.

Particular attention is given to DNS servers connected to the private, inter-Service Provider
backbone network known as the "GRX" or "IPX", as described in GSMA PRD IR.34 [12].

Out of the scope of this document are vendor specific implementation/architecture options
and configuration of DNS servers used on the Internet (e.g. those DNS servers attached to
the Internet for web site hosting). The only exception to this is the guidelines for sub
domains used for any standardised services that specifically use the Internet i.e. those that
use the "pub.3gppnetwork.org" domain name.

Note that ENUM is out-of-scope of this document and is addressed in [56].

1.3 Document Cross-References Comment [A1]: The doc ref is now

missing No3 is this correct? It now looks
like a mistake in the document
Document
Ref Title
Number
1 IETF RFC 1034 "Domain Names - Concepts and Facilities"
2 IETF RFC 1035 "Domain Names - Implementation and Specification"

IETF RFC 3401 "Dynamic Delegation Discovery System (DDDS) Part One: The
4
Comprehensive DDDS"
IETF RFC 3402 "Dynamic Delegation Discovery System (DDDS) Part Two: The
5
Algorithm"
IETF RFC 3403 "Dynamic Delegation Discovery System (DDDS) Part Three: The
6
Domain Name System (DNS) Database"

V15.0 Page 5 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

Document
Ref Title
Number
IETF RFC 3404 "Dynamic Delegation Discovery System (DDDS) Part Four: The
7
Uniform Resource Identifiers (URI)"
3GPP TS 23.003 "Numbering, addressing and identification", Version 8.0.0 or
8
higher
9 GSMA PRD IR.52 "MMS Interworking Guidelines"
10 GSMA PRD IR.61 "WLAN Roaming Guidelines"
11 GSMA PRD IR.65 "IMS Roaming and Interworking Guidelines"
12 GSMA PRD IR.34 "Inter-Service Provider IP Backbone Guidelines"
13 IETF RFC 2821 "Simple Mail Transfer Protocol"
14 IETF RFC 2822 "Internet Message Format"
3GPP TS 23.140 "Multimedia Messaging Service (MMS); Functional description;
15
Stage 2", version 6.7.0 or higher
16 IETF RFC 2915 "The Naming Authority Pointer (NAPTR) DNS Resource Record"
17 IETF RFC 3263 "Session Initiation Protocol (SIP): Locating SIP Servers"
18 IETF RFC 2782 "A DNS RR for specifying the location of services (DNS SRV)"
3GPP TS 33.220 "Generic Authentication Architecture (GAA); Generic
19
bootstrapping architecture", version 6.9.0 or higher
3GPP TS 43.318 "Generic Access to the A/Gb interface; Stage 2", version 6.6.0 or
20
higher
3GPP TS 44.318 "Generic Access (GA) to the A/Gb interface; Mobile GA interface
21
layer 3 specification", version 6.5.0 or higher
3GPP TS 23.236 "Intra Domain Connection of RAN Nodes to Multiple CN Nodes",
22
version 6.3.0 or higher
3GPP TS 23.060 "General Packet Radio Service (GPRS); Service description;
23
Stage 2", version 6.14.0 or higher
24 IETF RFC 3824 "Using E.164 numbers with the Session Initiation Protocol (SIP)"
25 IETF RFC 1032 "Domain administrators guide"
3GPP TS 29.060 "General Packet Radio Service (GPRS); GPRS Tunnelling
26
Protocol (GTP) across the Gn and Gp interface"
OMA "Secure User Plane Location Architecture; Approved Version 1.0
27 OMA-AD-SUPL-V1_0-2 – 15 June 2007"
0070615-A
3GPP TS 23.401 "General Packet Radio Service (GPRS) enhancements for
28 Evolved Universal Terrestrial Radio Access Network (E-UTRAN)
access"
29 3GPP TS 23.402 "Architecture enhancements for non-3GPP accesses"
30 3GPP TS 23.292 "IP Multimedia System (IMS) centralized services; Stage 2" Comment [A2]: Same with 31, 32, 33,
34 should the numbers remain but with an
explanation as to why they are no longer in
use

V15.0 Page 6 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

Document
Ref Title
Number

3GPP TS 24.229 "IP Multimedia Call Control Protocol based on Session Initiation
35 Protocol (SIP) and Session Description Protocol (SDP); Stage 3",
version 7.13.0 or higher.
ITU-T Recommendation "The international identification plan for mobile terminals and
36
E.212 mobile users"
ITU-T Recommendation "The international public telecommunication numbering plan"
37
E.164
38 IETF RFC 3261 "SIP: Session Initiation Protocol"
39 GSMA PRD IR.33 "GPRS Roaming Guidelines"
OMA OMA-TS- "Service Guide for Mobile Broadcast Services"
40 BCAST_Service_Guide-
V1_1-20100111-D
41 ITU-T E.xxx TBC Comment [A3]: Shouldn’t this be
updated and the correct ITU document
GSMA PRD IR.40 "Guidelines for IP Addressing and AS Numbering for GRX/IPX number and title be added?
42
Network Infrastructure and User Terminals"
IETF RFC 4769 "IANA Registration for an Enumservice Containing Public
43
Switched Telephone Network (PSTN) Signalling Information"
IETF RFC 4825 "The Extensible Markup Language (XML) Configuration Access
44
Protocol (XCAP)"
3GPP TS24.623 "Extensible Markup Language (XML) Configuration Access
45 Protocol (XCAP over the Ut interface for Manipulating
Supplementary Services)"
46 GSMA PRD IR.92 "IMS Profile for Voice and SMS"
RCS Release Docs RCS 1-4 Release Documents
47 http://www.gsmworld.com/our-
work/mobile_lifestyle/rcs/rcs_release_docs.htm
[RCS 1.2.2] RCS-e – Advanced Communications: Server and Client
Specification Version 1.2.2
48
http://www.gsma.com/rcs/wp-content/uploads/2012/03/rcs-
e_advanced_comms_specification_v1_2_2_approved.pdf
GSMA PRD IR.21 GSM Association Roaming Database, Structure and Updating
49
Procedures
3GPP TS 32.501 Telecommunication management; Self-configuration of network
50
elements; Concepts and requirements
3GPP TS 36.300 Evolved Universal Terrestrial Radio Access (E-UTRA) and
51 Evolved Universal Terrestrial Radio Access Network (E-UTRAN);
Overall description; Stage 2

V15.0 Page 7 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

Document
Ref Title
Number
52 GSMA PRD IR.88 LTE and EPC Roaming Guidelines

3GPP TS 26.346 Multimedia Broadcast/Multicast Service (MBMS); Protocols and

53
codecs
3GPP TS 24.302 “Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP
54
access networks; Stage 3”
3GPP TS 24.379 Mission Critical Push To Talk (MCPTT) call control;
55
Protocol specification

56 GSMA NG.105 ENUM Guidelines for Service Providers and IPX Providers

2 DNS As Used on the GRX/IPX

2.1 Introduction
The Domain Name System is critical to such services as GPRS roaming, inter-PLMN MMS
delivery and IMS inter-working. DNS is defined in many IETF RFC documents; the most
notable ones are IETF RFC 1034 [1] and IETF RFC 1035 [2].

2.2 Architecture
The DNS on the inter-PLMN IP backbone network (known as the "GRX/IPX") is completely
separate from the DNS on the Internet. This is purposely done to add an extra layer of
security to the GRX/IPX network, and the nodes within it. The GRX/IPX Root DNS Servers
that network operators see are known as "Slave" Root DNS Servers and are commonly
provisioned by that Service Provider's GRX/IPX. However, these Slave Root DNS Servers
can be provisioned by operators themselves if they so wish.

Each Slave Root DNS Server is synchronised with a "Master" Root DNS Server. This
process of synchronisation is known as a "Zone Transfer" and ensures that the data is the
same in all GRX/IPX Service Providers' and Operators' Slave Root DNS Servers. The
following diagram depicts this:

V15.0 Page 8 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

Master
Zone
File

Master
Root
Zone Transfers Zone Transfers

Zone Transfers
Slave Slave Slave Slave
Root Root Root
Root
GRX 1 MNO 2 GRX 2 MNO 3

Queries/Responses

Local
DNS

MNO 1

Figure 1: Backbone Architecture

The data in the Master Root DNS Server is known as the Master Zone File. The population
of the data that goes into the Master Zone File has a number of sources, mainly Operators,
GRX/IPX Providers and GRX/IPX Providers acting on behalf of Operators. It is also policed
and validated by the Master Root DNS Server providers (under authority from GSMA) to
ensure such things as correct sub-domain allocation and usage etc. The following diagram
depicts this:

V15.0 Page 9 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

GRX
Providers
Info GSMA
NS
N S Info
Operators N S Info

Policing

Problems
Queries
Master Root DNS Server
Operational Problems
Support Queries

Master Administration Interfaces

Zone
File
DNS Interfaces

Zone Transfers

Slave Root
Zone Transfers
DNS Zone Transfers

DNS Queries/Responses
Slave Slave Root
GRX Provider 1 Root Zone Transfers DNS
Slave Root &
DNS
DNS Local
& DNS
Local
Local DNS GRX Provider 2
DNS

MNO 2 MNO 3
MNO 1

Figure 2: Overall Process Architecture

Finally, the following shows the architecture and the typical signalling involved in resolving
hostnames to IP addresses or vice versa. The numbered steps below in the diagram
correspond to the numbered message flows:

GRX 1
Or
MNO 1

Slave Root
DNS

2
3

4 GRX 1/2
Authoritative Or
MNO 1 DNS MNO 2
Local Caching
5
DNS
1

6
Resolver

Figure 3: Resolver Architecture

1. The Resolver (for example an SGSN trying to find out the IP address of a GGSN)
sends a query for the hostname (for example an APN) for which it wants the IP
address, to its local caching DNS server.

V15.0 Page 10 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

2. The local caching DNS server checks to see if it has the answer to the query in its
cache. If it does it answers immediately (with message 6). Otherwise, it forwards the
query on to the Root DNS server. The Root DNS server may reside in Service
Provider 1's network or it may reside in the GRX/IPX provider's network (GRX1). The
address(es) of the Root DNS server may either be statically configured or be found
by using Host Anycasting (see below).
3. The Root DNS server returns a referral to the DNS server which is authoritative for
the queried domain name of the hostname (for example returns the authoritative
server for "mnc015.mcc234.gprs").
4. The local caching DNS server caches the response for a specified amount of time
(specified by the root DNS server) and then re sends the query but to the
authoritative DNS server as specified by the Root DNS server. The authoritative
DNS server may reside in the same GRX/IPX provider's network (GRX1), another
GRX/IPX provider's network (GRX2) or the network of the destination Mobile
Network Operator (Service Provider 2). (Indeed, it may even reside in the requesting
Service Provider's network!)
5. The Authoritative DNS server responds to the query with the address of the
hostname (or responds with a hostname, if a reverse lookup is being performed) to
the Local Caching server in the requesting network (Service Provider 1).
6. The Local Caching Server caches the response for a specified amount of time
(specified by the authoritative server) and forwards it on to the Resolver.

NOTE 1: The above shows only a typical message flow for DNS resolving on the
GRX/IPX. It may take extra queries when an MNO has Multiple levels of
authoritative DNS servers (see example below and section 3.1),. Please
refer to section 4 for more detailed information for each service.

NOTE 2: In clause 7.11.21 (Section 17) IR.21 [49] provides for MNOs to directly
exchange the IP addresses and DNS names of their authoritative DNS
servers. This gives the option for an MNO who has received such
information from another MNO to configure directly into their local caching
servers the authoritative DNS servers IP addresses for the corresponding
DNS names.
When this option is used, and a query matching a configured DNS name is
received, the interaction with the Root DNS server specified in steps 2-4
above is bypassed. Instead the query is sent directly to the other operators
authoritative DNS server, after which steps 5 and 6 follow. However if the
local caching DNS server has cached the answer to the query, the answer
is sent directly as specified in step 2.

Instead of having a single Authoritative DNS, an Operator may choose to split the DNS into
several levels of DNS for example a First Level DNS which may be authoritative for some of
the domain names “owned” by the MNO, and one or more Second Level Authoritative
DNSes, which may be authoritative for different “subdomainnames”, where for example a
Second Level DNS may be outsourced to 3rd party service provider for a particular service.

V15.0 Page 11 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

GRX 1
Or
MNO 1

Slave Root
DNS

2
3
GRX 1/2
4 1st Level
Or
Authoritative
MNO 2
DNS
MNO 1 Local Caching 5
DNS
1
8

Resolver 6

7 GRX 1/2
Or
2nd Level MNO 2
Authoritative Or
DNS 3rd Pty SP

Figure 4: Resolver Architecture with multiple levels of Authoritative DNS

1. Same as step 1 in the example above

2. Same as step 2 in the example above
3. Same as step 3 in the example above
4. Same as step 4 in the example above
5. The First Level Authoritative DNS server may be authoritative for the queried domain
name, in which cases it responds to the query with the address of the hostname (or
responds with a hostname, if a reverse lookup is being performed) to the Local
Caching server in the requesting network (Service Provider 1). In this case the
following step process continues with step 8.
Alternatively for certain “subdomain names”, a second level DNS may be
authoritative. In this case The First Level Authoritative DNS server returns a referral
to the Second Level DNS server which is authoritative for the queried domain name
of the hostname (for example returns the authoritative server for
"<subdomainname>.mnc015.mcc234.gprs")
6. The local caching DNS server caches the response for a specified amount of time
(specified by the First Level Authoritative DNS server) and then re - sends the query
to the Second Level Authoritative DNS server as specified by the First Level
Authoritative DNS server. The 2nd Level Authoritative DNS server may reside in the

V15.0 Page 12 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

same GRX/IPX provider's network (GRX1), another GRX/IPX provider's network

(GRX2), the network of the destination Mobile Network Operator (Service Provider
2), or in a 3rd Party Service Providers Network.
7. The Second Level Authoritative DNS server may respond to the query with the
address of the hostname (or responds with a hostname, if a reverse lookup is being
performed) to the Local Caching server in the requesting network (Service Provider
1).
8. The Local Caching Server caches the response for a specified amount of time
(specified by the authoritative server) and forwards it on to the Resolver.

NOTE 3: It is recommended that no more than two Levels of Authoritative DNS (that
is First Level and Second Level) are provisioned in a resolution "chain".

NOTE 4: In case the option to directly configure the IP address of another operators
DNS server is used as discussed in NOTE 2 above, only IP addresses of
First Level Authoritative DNS Server should be configured.

Some IPX services are offered on different network segments (VLANs) that are application
aware and that may not provide end-to-end IP connectivity, i.e. as shown in Fig 4 below,
MNO2 can either be a On-net MNO or a Off-net via IPX2. The DNS architecture is required
to take this into account. (See IR.34). A resolver architecture where the DNS service is
“fronted” with a DNS cache/forwarder is required.

Figure 5 Service aware network resolver architecture

V15.0 Page 13 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

1. The Resolver sends a query, to its local caching DNS server for the hostname for
which it wants the IP address.

2. The local caching DNS server checks to see if it has the answer to the query in its
cache. If it does, it answers immediately (with message 8). Otherwise, it forwards the
query on to the IPX proxy/DNS
3. Based on the requested domain, the IPX DNS/Cache, either sends the query to the
root DNS (in case MNO2 is on-net) or to the next IPX provider proxy (if MNO2 is off-
net) to resolve the query.
4. The root slave DNS returns the authoritative DNS for the requested domain in MNO 2
or (message 4-bis) the IPX 2 proxy returns the query response.
5. (Case of on-net only: ) The IPX proxy/cache sends the query to the authoritative DNS
in MNO 2 network.
6. (Case of on-net only: ) The authoritative DNS in MNO 2 returns the response to the
query.
7. The IPX proxy/cache returns the response to the query to the cache in MNO 1
network.
8. The response is returned from the local cache to the resolver.

2.3 Domains

2.3.1 Introduction
The following sub-sections detail the domain names that can and cannot be used on the
GRX/IPX network.

In addition to this, the 3GPP have designated a specific sub domain for usage on the
Internet's DNS to enable user equipment to locate a specific server on the Internet
(terminals cannot see the GRX/IPX therefore a whole new sub domain had to be
introduced). For more information on which domains used by 3GPP are intended for which
network, see 3GPP TS 23.003 [8], Annex D.

2.3.2 General
Unlike the DNS on the Internet, the DNS on the GRX/IPX network is currently much "flatter".
That is, there are not so many domains (and sub-domains of thereof), supported and
provisioned in the GRX/IPX Root DNS Server. This inherently means that all domain names
used by Service Providers and GRX/IPX Providers in any service that utilises the GRX/IPX
network are limited to just the domain names detailed in 2.3.3 below. No other domain
name formats are currently supported on the GRX/IPX network! This effectively means
a limitation of domain names of ".gprs" and ".3gppnetwork.org" at the higher level, and
limited beneath to sub-domains of a format based on ITU-T recommendation E.212 [36]
number ranges.

For the ".gprs" domain name, so called "human friendly" sub-domains are also allowed, as
specified in 3GPP TS 23.003 [8], section 9. This consists of simply an FQDN reserved in the
Internet domain name space e.g. serviceprovider.fi, serviceprovider.co.uk. However, such
sub-domains of ".gprs" are not generally used in the GRX/IPX network and it is

V15.0 Page 14 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

recommended not to use these as they can negatively affect GPRS/3G PS roaming. See
section 2.3.3 below for more details.

More information on processes and procedures relating to domain names can be found in
section 6.

2.3.3 Domain names used on the GRX/IPX DNS

The following provides a summary of the domain names that are used by Service Providers
on private IP inter-connects and on the GRX/IPX network. These domain names are only
resolvable by network equipment and not by end users. That is, they are exclusively used
on the Network-Network Interface (NNI) and not on the User-Network Interface (UNI).

Additional domain names that are resolvable on the GRX/IPX network's DNS may be added
in the future. See section 6 for more details.

For more details about each domain name and/or sub-domain name, refer to the referenced
documents.

V15.0 Page 15 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX Providers

Domain name Sub-domain(s) Explanation Rules of Usage Resolvability

Each Service Provider
is allowed to use only
sub-domains
consisting of MNC(s)
Service Provider domains of the form:
Used in GPRS for the and MCC(s) that are
<Network_Label>.mnc<MNC>.mcc<MCC>.gprs
Operator ID in APNs. allocated to them by
See section 4.2 and ITU-T and their local
Where <Network Label> is the Network Label part of national numbering Domain needs to be
also 3GPP TS 23.003
the Access Pont Name (APN) as defined in 3GPP TS authority. resolvable by at
[8], section 9, for more
23.003 [8], section 9, and <MNC> and <MCC> are least all GPRS/PS
information.
the MNC and MCC of the Service Provider roaming partners.
For Support of 2G/3G Service Providers
represented in decimal (base 10) form, with any 2
and EPC coexistence, should avoid using
digit MNC padded out to 3 digits by inserting a zero
see also section 4.17 Network Labels
("0") on the beginning e.g. 15 becomes 015.
consisting of any of the
below defined
.gprs sub-domains, in order
to avoid clashes.
rac<RAC>.lac<LAC>.mnc<MNC>.mcc<MCC>.gpr Used in inter-SGSN
s handovers (i.e. Routing Domains need to be
Area Updates) by the resolvable by at
new SGSN (possibly in Each Service Provider
Where <RAC> and <LAC> are the Routing Area least all SGSNs to
a new PLMN) to route is allowed to use only
Code and Location Area Code (respectively) which a UE can
to the old SGSN sub-domains
represented in hexadecimal (base 16) form, and hand over (which
(possibly in the old consisting of MNC(s)
<MNC> and <MCC> are the MNC and MCC of the may be in other
PLMN). See section and MCC(s) that are
Service Provider represented in decimal (base 10) networks, if inter
4.2 and also 3GPP TS allocated to them by
form, with any 2 digit MNC padded out to 3 digits by network GPRS/PS
23.003 [8], Annex C.1, ITU-T and their local
inserting a zero ("0") on the beginning e.g. 15 handovers are
for more information. national numbering
becomes 015. supported in a
authority.
nri<NRI>.rac<RAC>.lac<LAC>.mnc<MNC>.mcc Used in Routing Area Service Provider's
<MCC>.gprs Updates by the new network).
SGSN (possibly in a

V15.0 Page 16 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX Providers

Domain name Sub-domain(s) Explanation Rules of Usage Resolvability

Where <NRI>, <RAC> and <LAC> are the Network new PLMN) to route to
Resource Identifier, Routing Area Code and Location the old SGSN (possibly
Area Code (respectively) represented in hexadecimal in the old PLMN),
(base 16) form, and <MNC> and <MCC> are the where Intra Domain
MNC and MCC of the Service Provider represented Connection of RAN
in decimal (base 10) form, with any 2 digit MNC Nodes to Multiple CN
padded out to 3 digits by inserting a zero ("0") on the Nodes (also known as
beginning e.g. 15 becomes 015. "RAN flex" – see 3GPP
TS 23.236 [22]) is
applied. See section
4.2 and also 3GPP TS
23.003 [8], Annex C.1,
for more information.

rnc<RNC>.mnc<MNC>.mcc<MCC>.gprs Used in SRNS

relocation to route to
the target RNC in the
Where <RNC> is the RNC ID represented in
new SGSN (possibly in
hexadecimal (base 16) form, and <MNC> and
a new PLMN). See
<MCC> are the MNC and MCC of the Service
section 4.2 and also
Provider represented in decimal (base 10) form, with
3GPP TS 23.003 [8],
any 2 digit MNC padded out to 3 digits by inserting a
Annex C.3, for more
zero ("0") on the beginning e.g. 15 becomes 015.
information.
Domain needs to be
mms.mnc<MNC>.mcc<MCC>.gprs Used in MMS for the resolvable by at
domain name part of least all directly
Where <MNC> and <MCC> are the MNC and MCC the FQDN for MMSCs. connected MMS
of the Service Provider represented in decimal (base See section 4.3 and interworking
10) form, with any 2 digit MNC padded out to 3 digits also 3GPP TS 23.140 partners/Service
by inserting a zero ("0") on the beginning e.g. 15 [15], section 8.4.5.1, Providers and
becomes 015. for more information. directly connected
MMS Hub

V15.0 Page 17 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX Providers

Domain name Sub-domain(s) Explanation Rules of Usage Resolvability

Providers.
The domain name(s)
used must be owned
by that Service
Provider on the
Used as an alternative
<Internet_assigned_domain_name>.gprs Internet. If the domain
Operator ID in APNs
name(s) expire on the Domain needs to be
(also known as
Internet, they also resolvable by at
Where <Internet_assigned_domain_name> is a "Human Readable
expire on the least all GPRS/PS
domain name reserved by the Service Provider on APNs"). See 3GPP TS
GRX/IPX. Care should roaming partners.
the Internet. An example is "example.com.gprs" 23.003 [8], section 9,
be taken to ensure
for more details.
there is no clash with
the other sub-domains
for ".gprs" as defined
above.
Each Service Provider Domain needs to be
Used in IMS in SIP
ims.mnc<MNC>.mcc<MCC>.3gppnetwork.org is allowed to use only resolvable by at
addressing; specifically
sub domains least all SIP/IMS
in the Private and
consisting of MNC(s) based service inter
Where <MNC> and <MCC> are the MNC and MCC Public Identities used
and MCC(s) that are working
of the Service Provider represented in decimal (base in SIP registration. See
allocated to them by partners/Service
10) form, with any 2 digit MNC padded out to 3 digits section 4.5 and 3GPP
ITU T and their local Providers, as well
by inserting a zero ("0") on the beginning e.g. 15 TS 23.003 [8], section
national numbering as roaming partners
.3gppnetwork.org becomes 015. 13, for more
authority. where a visited P-
information.
CSCF is used.
wlan.mnc<MNC>.mcc<MCC>.3gppnetwork.org Used in WLAN Sub domains within Since this is a
inter-working for NAI the Service Provider's realm, not a domain
Where <MNC> and <MCC> are the MNC and MCC realms. See section domain (i.e. name, it does not
of the Service Provider represented in decimal (base 4.4 and 3GPP TS mnc<MNC>.mcc<MC necessarily have to
10) form, with any 2 digit MNC padded out to 3 digits 23.003 [8], section 14, C>) are documented in be resolvable by
by inserting a zero ("0") on the beginning e.g. 15 for more information. 3GPP TS 23.003 [8]. It external entities.

V15.0 Page 18 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX Providers

Domain name Sub-domain(s) Explanation Rules of Usage Resolvability

becomes 015. is recommended that The only time this is
Service Providers do used in DNS is
not use other sub when Diameter is
domains that are not used and the next
specified in 3GPP, hop is determined
OMA or in this PRD as by DNS rather than
this could potentially a look up table.
cause a clash of sub Since this is a
domain usage in the realm, not a domain
Used in the Generic future. name, it does not
gan.mnc<MNC>.mcc<MCC>.3gppnetwork.org Access Network for
necessarily have to
Full Authentication NAI
be resolvable by
realms and Fast
Where <MNC> and <MCC> are the MNC and MCC external entities.
Re-authentication NAI
of the Service Provider represented in decimal (base The only time this is
realms. See section
10) form, with any 2 digit MNC padded out to 3 digits used in DNS is
4.7 and 3GPP TS
by inserting a zero ("0") on the beginning e.g. 15 when Diameter is
23.003 [8], section
becomes 015. used and the next
17.2, for more
hop is determined
information.
by DNS rather than
a look up table.
Used in the Enhanced
Packet Core (EPC)
epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org architecture (previously
known as Service Domain and
Where <MNC> and <MCC> are the MNC and MCC Architecture Evolution sub-domains need
of the Service Provider represented in decimal (base – SAE) for NAIs and to be resolvable by
10) form, with any 2 digit MNC padded out to 3 digits FQDNs of EPC related EPC/SAE roaming
by inserting a zero ("0") on the beginning e.g. 15 nodes. See section 4.9 partners.
becomes 015. and 3GPP TS 23.003
[8], section 19, for
more information.

V15.0 Page 19 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX Providers

Domain name Sub-domain(s) Explanation Rules of Usage Resolvability

For support of EPC
and 2G/3G
coexistence see also
section 4.17
Domain should only
ics.mnc<MNC>.mcc<MCC>.3gppnetwork.org Used in the IMS
be resolvable for
Centralised Services
CS roaming
feature in SIP
Where <MNC> and <MCC> are the MNC and MCC partners where an
addressing. See
of the Service Provider represented in decimal (base MSC (Server)
section 4.10 and 3GPP
10) form, with any 2 digit MNC padded out to 3 digits enhanced for ICS is
TS 23.003 [8], section
by inserting a zero ("0") on the beginning e.g. 15 allowed to be used
20, for more
becomes 015. in that visited
information.
partner's network.
Used by Service
Each Service Provider
node.mnc<MNC>.mcc<MCC>.3gppnetwork.org Providers to provide
is allowed to use only Domain needs to be
FQDNs to non-service
sub-domains resolvable by at
specific nodes/hosts
Where <MNC> and <MCC> are the MNC and MCC consisting of MNC(s) least all
e.g. DNS/ENUM
of the Service Provider represented in decimal (base and MCC(s) that are roaming/interworkin
servers, routers,
10) form, with any 2 digit MNC padded out to 3 digits allocated to them by g partners for the
firewalls etc. See
by inserting a zero ("0") on the beginning e.g. 15 ITU-T and their local services used by
section 2.4 of this
becomes 015. national numbering this domain name.
document for more
authority.
information.

oam.mnc<MNC>.mcc<MCC>.3gppnetwork.org Used by eNBs and Each Service Provider Domain should only
possibly other network is allowed to use only be resolvable by
entities in network sub-domains entities within an
Where <MNC> and <MCC> are the MNC and MCC
element self- consisting of MNC(s) operator’s network,
of the Service Provider represented in decimal (base
configuration to and MCC(s) that are or in the case of
10) form, with any 2 digit MNC padded out to 3 digits
discover an Operations allocated to them by network sharing,
by inserting a zero ("0") on the beginning e.g. 15
and Maintenance ITU-T and their local within the shared
becomes 015.
(OAM) system. See national numbering operator’s network.

V15.0 Page 20 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX Providers

Domain name Sub-domain(s) Explanation Rules of Usage Resolvability

section 4.16 and also authority.
3GPP TS 23.003 [8]
section 23, for more
information.
Used by the MCPTT
Each Service Provider
service in an XML text
is allowed to include
where confidentiality
this domain name
protection of a URI as
when confidentiality Intentionally not
specified in TS 24.379
mc1-encrypted.3gppnetwork.org protection of a URI as resolvable by any
[x] is required. See
specified in TS 24.379 entity.
Rel-13 version of
[x] is required and the
3GPP TS 23.003 [8],
URI is not used for
section 26.2, for more
routing.
information.
Used in WLAN
inter-working,
specifically as a realm Neither a Service
in the Alternative NAI. Provider, a GRX/IPX
Its purpose is to enable Provider nor any other Intentionally not
unreachable.3gppnetwork.org the UE to retrieve a list entity should use this resolvable by any
of PLMNs behind a domain name. It is entity.
WLAN Access Point. simply reserved to
See 3GPP TS 23.003 never be used!
[8], section 14.6, for
more information.
spn<SPN>.ipxsp.org
Not used in any Domain needs to be
Each Service Provider
particular service, resolvable by at
is allowed to use only
Where <SPN> is the Service Provider Number (as however, can be used least all
.ipxsp.org SPNs that are
defined in ITU-T E.xxx [41]) of the Service Provider. by any Service roaming/interworkin
allocated to them by
An example is: "spn001.ipxsp.org". Provider for any g partners for the
ITU-T.
service they see fit. services used by

V15.0 Page 21 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX Providers

Domain name Sub-domain(s) Explanation Rules of Usage Resolvability

Further sub-domains under this are the responsibility The main intention is to this domain name.
of the owning Service Provider. However, it is provide a domain
recommended to use/reserve the sub-domains name that Service
defined above for the domain Providers without an
"mnc<MNC>.mcc<MCC>.3gppnetwork.org". E.212 number range
allocation can use
when connecting to the
IPX network.
.e164enum.net Used as the domain Each Service Provider
name for ENUM is allowed to use only
The sub-domains of this domain name correspond to
queries to the GRX/IPX sub-domains relating See section 5 for
reversed ITU-T E.164 numbers (as defined in ITU-T
Carrier ENUM as to their subscribers. more information.
Recommendation E.164 [37]).
defined in section 5 of See section 5 for more
the present document. information.
.in-addr.arpa Used for reverse
lookups for IPv4
addresses i.e. mapping
names to IPv4
addresses. This is Domain should be
useful when resolvable by at
troubleshooting Each Service Provider
least all
The sub-domains of this domain name correspond to shall populate this
inter-PLMN interworking
reversed IPv4 addresses that belong to the Service domain for IP
connections. Due to partners/Service
Provider. addresses assigned to
available tools being Providers, roaming
pre-configured to use them only (except with
partners and
this hierarchy for permission of the
directly connected
reverse look-ups, it actual owner).
GRX/IPX Providers.
would not be feasible
to use any different
TLD.
.ip6.arpa The sub-domains of this domain name correspond to Used for reverse

V15.0 Page 22 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX Providers

Domain name Sub-domain(s) Explanation Rules of Usage Resolvability

reversed IPv6 addresses that belong to the Service lookups for IPv6
Provider. addresses i.e. mapping
names to IPv6
addresses. This is
useful when
troubleshooting
inter-PLMN
connections. Due to
available tools using
this hierarchy for
reverse look-ups, it
would not be feasible
to use any different
TLD.

<IPXN>.ipxnetwork.org Not used in any

particular service,
Domain needs to be
however, can be used
resolvable by at
by any IPX Provider for One subdomain per
Where IPXN is the IPX provider company name or least all roaming/
any service they see IPX provider. An IPX
ipxnetwork.org acronym. It is agreed amongst IPX/GRX providers interworking
fit. The main intention provider shall not use
and assigned on a first come – first served basis (see partners for the
is to provide a domain two subdomains.
section 6.2). services used by
name that IPX provider
Further subdomains under this are the responsibility this domain name.
can use for IPX proxies
of the owning IPX provider. or other equipment.

Table 1: Definitive list of domain names owned by GSMA that are used on the GRX/IPX DNS

V15.0 Page 23 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

2.3.4 Domain names used on the Internet DNS (and owned by GSMA)
The following provides a summary of the domain names owned by GSMA that are used by
Service Providers on the Internet for 3GPP specific services. For more detail about each
domain name and/or sub-domain name, refer to the referenced documents.

V15.0 Page 24 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX Providers

Domain name Sub-domain(s) Explanation Rules of Usage Resolvability

Each Service Provider is
allowed to use only
sub-domains consisting of
Used in the Generic MNC(s) and MCC(s) that
gan.mnc<MNC>.mcc<MCC>.pub.3gppnetwork
Access Network for are allocated to them by
.org
home network ITU-T and their local
domain names in national numbering
Where <MNC> and <MCC> are the MNC and authority.
node identifiers.
MCC of the Service Provider represented in
See section 4.7 and
decimal (base 10) form, with any 2 digit MNC
3GPP TS 23.003 The host names "psegw"
padded out to 3 digits by inserting a zero ("0") on
[8], section 17.3, for and "pganc" under this
the beginning e.g. 15 becomes 015.
more information. sub-domain are reserved
for special use, as detailed
in 3GPP TS 23.003 [8],
pub.3gppnetwork.o Domains need to be
section 17.3
rg resolvable on the
w-apn.mnc<MNC>.mcc<MCC>.pub.3gppnetwo Each Service Provider is Internet.
rk.org Used in WLAN allowed to use only
inter-working for sub-domains consisting of
PDG addressing. MNC(s) and MCC(s) that
Where <MNC> and <MCC> are the MNC and
See section 4.4 and are allocated to them by
MCC of the Service Provider represented in
3GPP TS 23.003 ITU-T. The same rules
decimal (base 10) form, with any 2 digit MNC
[8], section 14, for apply for APN constructs,
padded out to 3 digits by inserting a zero ("0") on
more information. as defined in GSMA PRD
the beginning e.g. 15 becomes 015.
IR.34.
h- Used in the Secure Each Service Provider is
slp.mnc<MNC>.mcc<MCC>.pub.3gppnetwork User Plane allowed to use only
.org Location feature for sub-domains consisting of
Home SUPL MNC(s) and MCC(s) that
Where <MNC> and <MCC> are the MNC and Location Platform are allocated to them by
MCC of the Service Provider represented in addressing. See ITU-T and their local

V15.0 Page 25 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX Providers

Domain name Sub-domain(s) Explanation Rules of Usage Resolvability

decimal (base 10) form, with any 2 digit MNC section 4.8 and national numbering
padded out to 3 digits by inserting a zero ("0") on OMA-AD-SUPL-V1 authority.
the beginning e.g. 15 becomes 015. _0-20070615-A [27]
section 7.2.2, for
more information.
Used in the Generic
bsf.mnc<MNC>.mcc<MCC>.pub.3gppnetwork Authentication
.org Architecture for
BSF addressing
Where <MNC> and <MCC> are the MNC and when USIM is used
MCC of the Service Provider represented in in bootstrapping.
decimal (base 10) form, with any 2 digit MNC See section 4.6 and
padded out to 3 digits by inserting a zero ("0") on 3GPP TS 23.003
the beginning e.g. 15 becomes 015. [8], section 16, for
more information.
andsf.mnc<MNC>.mcc<MCC>.pub.3gppnetwo
rk.org

Where <MNC> and <MCC> are the MNC and

Used in EPC and
MCC of the Service Provider represented in
WLAN inter working
decimal (base 10) form, with any 2 digit MNC
(3GPP Rel 8) home
padded out to 3 digits by inserting a zero ("0") on
agent addressing.
the beginning e.g. 15 becomes 015.
See 3GPP TS
ha- Each Service Provider is
23.003 [8], section
apn.mnc<MNC>.mcc<MCC>.pub.3gppnetwork allowed to use only
21, for more
.org sub-domains consisting of
information.
MNC(s) and MCC(s) that
Where <MNC> and <MCC> are the MNC and are allocated to them by
MCC of the Service Provider represented in ITU T. The same rules
decimal (base 10) form, with any 2 digit MNC apply for APN constructs,

V15.0 Page 26 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX Providers

Domain name Sub-domain(s) Explanation Rules of Usage Resolvability

padded out to 3 digits by inserting a zero ("0") on as defined in GSMA PRD
the beginning e.g. 15 becomes 015. IR.34 [12].
Used in the OMA
Mobile Broadcast
Services (BCAST)
bcast.mnc<MNC>.mcc<MCC>.pub.3gppnetwo enabler, version
Each Service Provider is
rk.org 1.1, for Service
allowed to use only
Guide discovery by
sub-domains consisting of
a client with access
Where <MNC> and <MCC> are the MNC and MNC(s) and MCC(s) that
to an IMSI. See
MCC of the Service Provider represented in are allocated to them by
section 4.12 and
decimal (base 10) form, with any 2 digit MNC ITU-T and their local
OMA-TS-
padded out to 3 digits by inserting a zero ("0") on national numbering
BCAST_Service_G
the beginning e.g. 15 becomes 015. authority.
uide-
V1_1-20100111-D
[40] for more
information.
Used for the
RCS/RCS-e
service.
rcs.mnc<MNC>.mcc<MCC>.pub.3gppnetwork Each Service Provider is
.org allowed to use only
Where <MNC> and <MCC> are the MNC and RCS/RCS-e service sub-domains consisting of
MCC of the Service Provider represented in may use further MNC(s) and MCC(s) that
decimal (base 10) form, with any two (2) digit MNC subdomain names are allocated to them by
padded out to three (3) digits by inserting a zero depending on the ITU-T and their local
("0") on the beginning for example 15 becomes RCS/RCS-e service national numbering
015. evaluation and authority.
developments (for
example
config.rcs.mnc

V15.0 Page 27 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX Providers

Domain name Sub-domain(s) Explanation Rules of Usage Resolvability

<MNC>.mcc<MCC
>.pub.3gppnetwork.
org). The
description and the
use of the
subdomain names
will be referenced
in the RCS/RCS-e
specifications
where this domain
can be used by all
RCS/RCS-e
versions.
Used in the Generic
bsf.ims.mnc<MNC>.mcc<MCC>.pub.3gppnet Authentication Each Service Provider is
work.org Architecture for allowed to use only
BSF addressing sub-domains consisting of
Where <MNC> and <MCC> are the MNC and when ISIM is used MNC(s) and MCC(s) that
MCC of the Service Provider represented in in bootstrapping. are allocated to them by
decimal (base 10) form, with any 2 digit MNC See section 4.6 and ITU-T and their local
padded out to 3 digits by inserting a zero ("0") on 3GPP TS 23.003 national numbering
the beginning e.g. 15 becomes 015. [8], section 16, for authority.
more information.
xcap.ims.mnc<MNC>.mcc<MCC>.pub.3gppne Used in Each Service Provider is
twork.org supplementary allowed to use only
service sub-domains consisting of
Where <MNC> and <MCC> are the MNC and configuration using MNC(s) and MCC(s) that
MCC of the Service Provider represented in XCAP as specified are allocated to them by
decimal (base 10) form, with any 2 digit MNC in IR.92 [46]. Also ITU-T and their local
padded out to 3 digits by inserting a zero ("0") on see section 4.13 national numbering

V15.0 Page 28 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX Providers

Domain name Sub-domain(s) Explanation Rules of Usage Resolvability

the beginning e.g. 15 becomes 015. and 3GPP TS authority.
23.003 [8], section
13.9, for more
information.
Used in
epdg.epc.mnc<MNC>.mcc<MCC>.pub.3gppne inter-working
twork.org Each Service Provider is
untrusted non-
allowed to use only
3GPP access
sub-domains consisting of
Where <MNC> and <MCC> are the MNC and network to EPC.
MNC(s) and MCC(s) that
MCC of the Service Provider represented in See section 4.15
are allocated to them by
decimal (base 10) form, with any 2 digit MNC and 3GPP TS
ITU-T and their local
padded out to 3 digits by inserting a zero ("0") on 23.003 [8], section
national numbering
the beginning e.g. 15 becomes 015. 19.4.2.9, for more
information.
mbmsbs.mnc<MNC>.mcc<MCC>.pub.3gppnetw Used by a UE for
ork.org MBMS Service Each Service Provider is
Announcement allowed to use only
Where <MNC> and <MCC> are the MNC and Bootstrap. sub-domains consisting of
MCC of the Service Provider See section 4.18 MNC(s) and MCC(s) that
represented in decimal (base 10) and 3GPP TS are allocated to them by
form, with any 2 digit MNC padded out 23.003 [8], section ITU-T and their local
to 3 digits by inserting a zero ("0") 15.5, for more national numbering
on the beginning e.g. 15 becomes 015. information.

epdg.epc.mcc<MCC>.visited- Used by a roaming

country.pub.3gppnetwork.org UE to determine
Details of usage is defined
whether visited
in Release 13 version of
country mandates
Where <MCC> is the MCC of the country in which 3GPP TS 23.402 [29],
the selection of an
the UE is located represented in decimal (base 10) section 4.5.4.5.
ePDG in this
form.
country.

V15.0 Page 29 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX Providers

Domain name Sub-domain(s) Explanation Rules of Usage Resolvability

See 3GPP TS
23.003 [8], section
19.4.2.9.3 for more
information.

Table 2: Definitive list of domain names owned by GSMA that are used on the Internet DNS

V15.0 Page 30 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

2.3.5 Domain names used on the GRX/IPX DNS for UNI

Only the domain name "ipxuni.3gppnetwork.org" is defined for domain names of this type
(see 3GPP TS 23.003 [8]). However, there are currently no sub-domains reserved under this
domain name.

2.4 Non-service specific hostnames and domains

Having a consistent naming convention makes it easier for tracing and trouble-shooting as
well as easing the maintenance of Service Provider's DNS. The following convention is
recommended to achieve these goals. Although the usage of this naming methodology is
highly recommended, it is not mandated.

Service Provider nodes should have names for each interface with the following format:

<city>-<type>-<nbr>

where:

 <city> is the name, or shortened name, of the city/town (or closest, where applicable)
where the node is located
 <nbr> is a running number of similar devices at the same city (for DNS servers, use 0
to indicate the primary DNS Server)
 <type> describes device type and should be one of the following for GRX/IPX
connected hosts:

 dns - DNS servers

 ggsn
 sgsn
 rtr - router
 fw - firewall

Additional values for the <type> parameter are for further study for the GRX/IPX. For
example, the following are valid hostnames for interfaces on Service Provider nodes:

 helsinki-ggsn-4

The domain name to append to hostnames for nodes belonging to Service Providers should
be the following (see section 2.3 for more details on the domain name formats):

 node.mnc<MNC>.mcc<MCC>.3gppnetwork.org
 node.spn< SPN>.ipxsp.org

A combination of the above domain names could be used by a Service Provider; however,
for consistency it is better to use only one.

The following are thus example Fully Qualified Domain Names (FQDNs) for interfaces on
Service Provider nodes:

 helsinki-ggsn-4.node.mnc015.mcc234.3gppnetwork.org

V15.0 Page 31 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

 london-dns-23.node.spn001.ipxsp.org

Note that usage of the hostnames and sub-domains specified within this section under
"mnc<MNC>.mcc<MCC>.gprs" is now deprecated, and Service Providers are recommended
to use either of "mnc<MNC>.mcc<MCC>.3ppgnetwork.org" or "spn<SPN>.ipxsp.org"
domains at their earliest convenience. Of course, usage of "mnc<MNC>.mcc<MCC>.gprs"
for the uses as stated in section 2.3.3, is not deprecated and should continue as per normal.

2.5 Host names for the evolved packet Core (EPC)

The naming of Nodes for the Evolved Packet Core is specified in clause 19 of 3GPP TS
23.003 [8]

2.6 Host names for the IP Multimedia Subsystem (IMS)

Withn the IP Multimedia Subsystem (IMS) the following Naming Convention for IMS Nodes
shall be used <Node name>.<SP Domain Name>, where

 <Node name> may consist of one or more lables that uniquely identifies the IMS
node within the Service Provider network.

To avoid conflicts with future other subdomains to the <SP Domain Name> it can be
considered good practice to include “.node” as the right-most label of the <Node
Name>

 <SP Domain Name> is a Domain Name that is owned by the Service provider.

“ims.mnc<MNC>.mcc<MCC>.3gppnetwork.org” is the recommended <SP Domain

Name> for all IMS Nodes.

“ims.mnc<MNC>.mcc<MCC>.3gppnetwork.org” must be used as <SP Domain Name> for

IMS Nodes that are individually addressable over the IPX network by SIP or any other
protocol, and where those Node Names need to be resolved over the IPX DNS system.

Examples of IMS nodes that may need to be individually addressable, are all nodes that are
addressed using a SIP Route Header, such as the nodes hosting the functionalities of a P-
CSCF, S-CSCF, TRF, ATCF, and eMSC-S for I2.

3 General DNS Configuration for Service Providers

3.1 Introduction
This section gives some general information on DNS server configuration for operators. For
information on configuring DNS servers for specific services, see sections 4 and 5.

3.2 DNS Server Hardware

It is recommended that operators have physically separate Primary and Secondary DNS
servers. This helps provide the greatest service availability and allows for e.g. upgrading
DNS Servers without any service interruption.

V15.0 Page 32 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

3.3 DNS Server Software

Most commonly ISC BIND (usually version 4 or version 9) is the chosen software supplied
by equipment vendors with any new service equipment that utilises a DNS Nameserver.
Service Providers and IPX Providers should ensure that only the most secure version is
used in their live networks, and all security patches are applied. Note that no particular
version of BIND is recommended, because to do so here would provide potentially out of
date information to the reader.

Use of ISC BIND is fine for services which do not necessarily have a large data-fil (for
example: GPRS, MMS).

Such commercial DNS Namesserver solutions can also support legacy DNS data-fil (for
example, that used for GPRS roaming), thereby consolidating all operator DNS needs. Note
that it is out of the scope of this document, and the GSMA, to provide any recommendations
on commercial DNS Nameservers. In fact, diversity of DNS software used by Service
Providers and IPX Providers gives a better overall robustness of the DNS on GRX/IPX
network.

3.4 DNS Server naming

All DNS servers need to have an FQDN assigned to them. For Service Provider DNS
servers connected to the GRX/IPX, the naming conventions as specified in section 2.4 shall
be used.

3.5 Domain Caching

Since each service (e.g. GPRS, MMS etc.) has its own domain, a separate TTL value can be
set per service.

When setting the TTL value for a zone, careful consideration must be taken to ensure that
the right trade-off is made between performance and consistency. A small TTL value results
in a greater signalling overhead, greater processing overhead for the authoritative name
server(s) and greater time for a returning a result (an example: GPRS PDP Context set-up
time), but the data will be more up-to-date therefore allowing updates to propagate much
more quickly. A large TTL value results in a smaller signalling overhead, smaller processor
overhead for the authoritative name server(s) and usually shorter time for returning a result
to the requesting entity, but the data will be more likely to be out of date and therefore
resulting in updates taking longer to propagate.

It is highly recommended that negative caching is also used (available in ISC BIND versions
4.9, 8.x and 9.x and should be available in most commercial DNS solutions). Again, careful
consideration should be taken, considering factors such as the frequency of updates,
signalling overhead and processing overhead of the authoritative DNS server for the domain.

3.6 Reverse Mapping

Each operator is strongly recommended to provide PTR (Pointer) records for all IP
addresses that FQDNs refer to, for example for APNs, MMSC addresses and so on. This is
not needed for inter-working to be successful, but rather, is recommended as it aids in
trouble shooting/debugging activities such as performing a "traceroute".

V15.0 Page 33 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

Reverse mapping for IPv4 addressing uses the "in-addr.arpa" domain, and reverse mapping
for IPv6 addressing uses "ip6.arpa". See section 2.3.3 for more information.

3.7 Use of DNS Interrogation Modes

Two interrogation modes are defined in the DNS specifications: iterative and recursive.

In Iterative mode, a DNS server interrogates each DNS server in the hierarchy itself, in order
to resolve the requested domain name. In Recursive Mode, a DNS server interrogates only
the next DNS server in the DNS hierarchy. That DNS Server then takes on responsibility for
resolving the requested domain name and provides a final answer back to the original
requesting DNS server. Figure 6 below depicts both iterative and recursive queries:

1 1
2 6

2
5
3
4

5
3
4

Figure 6: Iterative (left) and Recursive (Right) modes of DNS querying

In non-service aware IPX (Example: GRX), only Iterative DNS queries shall be used within
the GRX/IPX. This not only saves on DNS Server load but also to enables visibility of the
source of the original request at the destination, which is lost when using recursive queries.

If any recursive DNS queries are received by a DNS Server then they should be ignored.
The only elements that should issue recursive DNS queries are service nodes issuing DNS
requests to their Local Caching DNS Servers e.g. an SGSN querying its Local Caching DNS
Server for an APN (see section 4.2 for more information on GPRS, including APN
resolution).

3.8 Use of the GRX/IPX Root DNS Server

There are two possibilities to arrange DNS hierarchy. The first is for each Service Provider to
configure their own authoritative DNS Server for each domain name that needs to be
resolved for all inter-working and roaming partner Service Providers. The draw-back of this
approach is that it is not scalable because every time a new inter-working and/or roaming
partner agreement is made, or even any existing inter-working and/or roaming partner's DNS
Server details change, the aforementioned authoritative DNS Server must be updated

V15.0 Page 34 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

accordingly. Thus, this could be a potential operational intensive task, and most likely a
frequent source for inter-working and roaming problems. This alternative may be fine for
small Service Providers with few interworking and/or roaming partners, but is not
recommended due to the reasons stated. Therefore, this alternative is not further detailed in
the present document.

Another alternative is to use the common GRX/IPX Root DNS Server, as provided for by the
GRX/IPX service provider (see section 2.2 for more detail on this architecture). Using the
GRX/IPX Root DNS Server enables modified DNS Server details for a Service Provider to
automatically propagate to all interworking and roaming partners (subject to caching time).
This alternative is the recommended one, and is thus the assumed deployment of
authoritative DNS Servers in the rest of the present document.

3.9 Provisioning of Service Provider's DNS servers

Service Providers should take care to share all appropriate data to enable all
roaming/inter-working partners routing to an authoritative DNS Server, that is a DNS Server
where their own domain names can be resolved by others. GSMA IR.21 (PRD or GSMA
InfoCentre database) and the GRX/IPX Root DNS should be used to ease such sharing of
data, wherever possible.

Service Providers can provision authoritative DNS Servers themselves or outsource to

another entity for example their GRX/IPX Provider.

Service providers may have all appropriate data available in a single level of authoritative
DNS servers, where each authoritative DNS server holds all the appropriate data for the
Service Provider.

Alternatively, Service Providers may choose to divide the appropriate data between a First
level Authoritative DNS Servers and 2nd Level Authoritative DNS Servers whereby each
2nd-level Authoritative DNS server only holds a subset of the appropriate data for the
Service provider.

When information about DNS servers are exchanged with the GRX/IPX Root DNS and other
Service Providers for example via PRD IR.21, and when 2nd-Level Authoritative DNS server
are used, it is essential to make a clear distinction between the First level Authoritative DNS
servers and 2nd-Level Authoritative DNS servers. This is to ensure that only First level
Authoritative DNS server are published in the GRX/IPX Root DNS such that the first query to
an Operators DNS always goes the First level Authoritative DNS and that the second level
DNS servers are reached only by means of referrals from the First Level Authoritative DNS
server.

3.10 Resource Records

Service Providers and IPX Providers should take care to provision only the DNS Resource
Records (RRs) that are necessary for service interworking, trouble shooting and O&M
(Operations & Maintenance).

V15.0 Page 35 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

3.11 Support for IPv4 and IPv6

Support for IPv4 and IPv6 on Service Provider DNS Nameservers is twofold: the ability to
serve data relating to IPv4 and IPv6 addresses, and connectivity to/from the nameserver.

For configuration information in a Nameserver, both IPv4 and IPv6 information can coexist
together. Service Providers just need to ensure that the Nameserver software used is
capable of supporting the relevant Resource Records (RR) required. The "A" RR is used to
hold IPv4 address information and the "AAAA" RR for IPv6 address information. Details on
reverse mapping (IPv4/IPv6 address to domain name) are specified in section 3.6.

For connectivity to a Nameserver, it is highly recommended that all Service Provider

Nameservers be reachable using IPv4. Any Nameservers serving IPv6 information should
also be reachable using IPv6.

See GSMA PRD IR.34 [12] and GSMA PRD IR.40 [42] for more information on
recommendations relating to IPv4 and IPv6 routing and addressing.

4 DNS Aspects for Standardised Services

4.1 Introduction
This section describes the DNS aspects of standardised services that utilise DNS.
Recommendations are made, where appropriate, beyond what is defined in the referenced
specifications in order to promote easier service interworking for Service Providers. The list
of services below is not exhaustive and other services that utilise DNS on the GRX/IPX can
be used.

If there are discrepancies between the description of the services and the referenced
specifications in the following sub-sections, what is stated in the referenced specifications
shall prevail.

4.2 General Packet Radio Service (GPRS)

4.2.1 Introduction
GPRS provides for a packet switched bearer in GSM/UMTS networks. Packets are tunnelled
between core network nodes that may or may not be in different PLMNs, using the GPRS
Tunnelling Protocol (GTP) as defined in 3GPP TS 29.060 [24].

Note that in UMTS, GPRS is referred to as "Packet Switched" access, however, this is just a
naming convention, and the mechanism remains the same.

For more information on GPRS/Packet Switched access, see GSMA PRD IR.33 [39], 3GPP
TS 23.060 [26], and 3GPP TS 29.060 [24].

4.2.2 APN resolution in PDP Context activation

PDP Context activations occur between the SGSN and the GGSN. PDP Contexts are
activated to an Access Point Name either provided by the MS, or derived by the network
(such as when the MS instructs the SGSN to use a "default" APN). It is the APN that

V15.0 Page 36 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

determines to which interface on which GGSN the PDP Context is to be established. See
section 2.3 for the format of APNs. Further details on the APN can be found in GSMA PRD
IR.33 [39].

An SGSN and a GGSN can be located in either the HPLMN or VPLMN. Both are in the
same network when the subscriber is in the HPLMN and also when the subscriber is
roaming in a VPLMN and is using a GGSN in the VPLMN (vGGSN). However, the SGSN
and GGSN are in different networks when the subscriber is roaming but using a GGSN in
the HPLMN (hGGSN).

GPRS roaming means the extension of packet switched services offered in the Home PLMN
to Visited PLMNs with which the HPLMN has a predefined commercial roaming agreement.

The necessary DNS queries for resolving an APN in order to activate a PDP Context are
described below. Note that the Authoritative DNS Server is usually located in the same
PLMN as the GGSN, but can be located elsewhere, for example, in the HPLMN's GRX/IPX
provider's network (due to the HPLMN outsourcing the Authoritative DNS Server).

VPLMN GRX/IPX Network VPLMN or HPLMN

Local Caching Root DNS Authoritative

SGSN GGSN
DNS Server Server DNS Server

PDP Context establishment procedure

Figure 7: DNS message flow for PDP Context activations

1. Upon receiving a "PDP Context Activation" message from the MS, the SGSN checks the
APN (if one was provided) against the user subscription record it previously obtained
from the HLR when the MS attached, and then sends a recursive DNS Query to the DNS
Local Caching DNS server.

V15.0 Page 37 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

2. The Local Caching DNS Server checks its local cache for the IP address of the
requested FQDN. If it has this, processing skips to step 6. Otherwise, the Local Caching
DNS Server checks its local cache for the IP address of the Authoritative DNS Server. If
it does not already have this IP address, it then issues an iterative DNS Query to the
Root DNS Server otherwise, processing skips to step 4.
3. The Root DNS Server replies to the DNS Query received from the Local Caching DNS
with the details of the Authoritative DNS Server (for example, the FQDN and/or IP
address(es).
4. The Local Caching DNS Server sends an iterative DNS Query to the Authoritative DNS
Server (which will reside in the VPLMN, for vGGSN connection, and will reside in the
HPLMN for hGGSN connection).
5. The Authoritative DNS Server replies to DNS Query received from the Local Caching
DNS Server with the IP address of the GGSN.
6. The Local Caching DNS Server replies to the DNS Query received from the SGSN (in
step 1) with the result obtained from the Authoritative DNS Server. The SGSN then
commences GTP tunnel establishment and, all being well, data flow starts.
As can be seen in the above steps, there are less DNS queries for a subscriber using a
GGSN in the VPLMN as the Root DNS Server is not interrogated.

Note also that the Local Caching DNS Server could also be the Authoritative DNS Server for
the requested FQDN, in which case a final result can be given immediately to the SGSN.

4.2.3 Inter-SGSN handovers for active PDP Contexts

When an MS has one or more PDP Contexts activated and moves to a new Routing Area
that is serviced by a new SGSN, the new SGSN needs to connect to the old SGSN in order
to download the PDP Context information and any data that is still to be delivered to the MS.
It can do this by either using a mapping table which has SGSN addresses against a finite set
of Routing Areas, or it can translate the old Routing Area Code (as received from the MS)
into a FQDN upon which to resolve to an IP address using DNS.

The former method is most commonly used for intra-PLMN SGSN handovers, and the latter
is used for inter-PLMN SGSN handovers. However, both methods can be used for both
types of handovers.

The latter of the two aforementioned methods is depicted below for inter- and intra-PLMN
SGSN handovers. The FQDN created by the SGSN depends upon whether the SGSN
handover is a Routing Area Update, Routing Area Update in a network which has Intra
Domain Connection of RAN Nodes to Multiple CN Nodes or is an SRNS Relocation (see
3GPP TS 23.060 [23], section 6.9, for more information).

V15.0 Page 38 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

New VPLMN or HPLMN GRX/IPX Network Old VPLMN or HPLMN

New Local Caching Root DNS Authoritative

Old SGSN
SGSN DNS Server Server DNS Server

PDP Context handover procedure

Figure 8: DNS message flow for PDP Context handovers between SGSNs

7. The new SGSN creates an FQDN using the old Routing Area Code (and the Network
Resource Identifier, if available) or the old RNC ID and then issues a recursive DNS
Query to the DNS server address configured in the SGSN (Local Caching DNS server).
8. The Local Caching DNS Server checks its local cache for the IP address of the
requested FQDN. If it has this, processing skips to step 6. Otherwise, the Local Caching
DNS Server checks its local cache for the IP address of the Authoritative DNS Server. If
it does not already have this IP address, it then issues an iterative DNS Query to the
Root DNS Server, otherwise, processing skips to step 4.
9. The Root DNS Server replies to the DNS Query received from the Local Caching DNS
with the details of the Authoritative DNS Server (for example, the FQDN and/or IP
address(es)).
10. The Local Caching DNS Server sends an iterative DNS Query to the Authoritative DNS
Server (which will reside in the VPLMN, for inter-PLMN handover, and will reside in the
HPLMN for intra-PLMN handover).
11. The Authoritative DNS Server replies to DNS Query received from the Local Caching
DNS Server with the IP address of the old SGSN.
12. The Local Caching DNS Server replies to the DNS Query received from the SGSN (in
step 1) with the result obtained from the Authoritative DNS Server. The New SGSN then
commences handover with the Old SGSN.

V15.0 Page 39 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

As can be seen in the above steps, there are less DNS queries for an intra-PLMN SGSN
handover as the Root DNS Server is not interrogated.

Note also that the Local Caching DNS Server could also be the Authoritative DNS Server for
the requested FQDN, in which case a final result can be given immediately to the New
SGSN.

4.3 Multi-media Messaging Service (MMS)

4.3.1 Introduction
MMS inter-working is where a subscriber of one operator has the ability to send and receive
Multimedia Messages (MMs) to and from a subscriber of another operator. Unlike SMS inter-
working, the MM is always sent to the user via his “home” service centre. This means that in
all MMS inter-working scenarios, the MM is always transferred from the source operator’s
MMSC to the destination operator’s MMSC. Thus, MMS interworking requires use of a
standardised inter-MMSC protocol. This protocol is defined as SMTP (defined in IETF RFC
2821[13]) as profiled in the MMS specification 3GPP TS 23.140 [15].

DNS is used in MMS in order for the source MMSC to resolve the destination MMSC/SMTP
server. DNS MX Resource Records, as defined in IETF RFC 1035 [2], are required for
SMTP based Multimedia Message routeing and relaying. It should be noted that GSMA PRD
IR.34 [12] recommends that the ".gprs" TLD should be used when utilising the GRX/IPX
network as the interworking network between MMSCs. This format of FQDN, including
allowed sub-domains, is defined in section 2.3 of the present document.

The selection of a DNS tree/hierarchy to use (e.g. Internet or GRX/IPX) ultimately depends
on the interconnection network used. The interconnection network used can in turn depend
on where the MM is to be sent e.g. Internet for when delivering to an e-mail user, GRX/IPX
network for when delivering to another MMS subscriber. Thus, the resolution process may
differ depending on whether the MM is addressed to an MSISDN/E.164 number or to an
NAI/e-mail address.

There are also different commercial models for MMS inter-working between Operators.
These are essentially the "Direct Interconnect" model, where MMs are sent from Operator A
to Operator B directly, and the "Indirect Interconnect Model", where MMs are sent from
Operator A to an MMS Hub (and the MMS Hub then takes care of delivering the MM to
Operator B).

More information on MMS interworking can be found in GSMA PRD IR.52 [9].

4.3.2 MM delivery based on MSISDN for the Direct Interconnect model

The following figure and associated numbered steps describe the direct interconnect only
scenario for MMS inter-working of MMs addressed to an MSISDN/E.164 number:

V15.0 Page 40 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

Operator A GRX/IPX Network Operator B

Local Caching Root DNS Authoritative

MMSC MMSC
DNS Server Server DNS Server

SMTP Message Transfer procedure

Figure 9: MMS Direct Inter-network Delivery

1. Upon receiving a Multimedia Message (MM) from the MS, the MMSC converts the
destination MSISDN to an MMS FQDN (commonly of the form
"mms.mnc<MNC>.mcc<MCC>.gprs") by using one of the following methods:
 An HLR look-up using e.g. the MAP_SRI_For_SM operation. This returns the IMSI, of
which the MNC and MCC are extracted to create the MMS FQDN.

The MMSC then sends a recursive DNS query for the derived FQDN to the Local
Caching DNS Server.

2. The Local Caching DNS Server checks its local cache for the IP address of the
requested FQDN. If it has this, processing skips to step 6. Otherwise, the Local Caching
DNS Server checks its local cache for the IP address of the Authoritative DNS Server. If
it does not already have this IP address, it then issues an iterative DNS Query to the
Root DNS Server, otherwise processing skips to step 4.
3. The Root DNS Server replies to the DNS Query received from the Local Caching DNS
Server with the details of the Authoritative DNS Server (for example, the FQDN and/or IP
address(es)).
4. The Local Caching DNS Server sends an iterative DNS Query to the Authoritative DNS
Server.
5. The Authoritative DNS Server replies to the DNS Query received from the Local Caching
DNS Server with the IP address of the MMSC, or, a list of FQDNs and/or IP addresses if
the query was for an MX record.

V15.0 Page 41 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

6. The Local Caching DNS Server replies to the DNS Query received from the MMSC (in
step 1) with the result obtained from the Authoritative DNS Server. The MMSC then
commences an SMTP session with Operator B's MMSC to transfer the MM.
Note that the Local Caching DNS Server could also be the Authoritative DNS Server for the
requested FQDN, in which case a final result can be given immediately to the MMSC.

4.3.3 MM delivery based on MSISDN for the Indirect Interconnect model

The following figure and associated numbered steps describe the MMS hub model of
interconnect for MMS inter-working of MMs addressed to an MSISDN/E.164 number:

Operator A Operator B or
GRX/IPX Network

Local Caching Authoritative MMSC or

MMSC
DNS Server DNS Server MMS Hub 1

SMTP Message Transfer procedure

Figure 10: MMS Inter-operator Delivery

1. Upon receiving a Multimedia Message (MM) from the MS, the MMSC converts the
destination MSISDN to an MMS FQDN (commonly of the form
"mms.mnc<MNC>.mcc<MCC>.gprs") by using one of the following methods:
 An HLR look-up using e.g. the MAP_SRI_For_SM operation. This returns the
IMSI, of which the MNC and MCC are extracted to create the MMS FQDN.

The MMSC then sends a recursive DNS query for the derived FQDN to the Local
Caching DNS Server.

2. The Local Caching DNS Server checks its local cache for the IP address of the
requested FQDN. If it has this, processing skips to step 4. Otherwise, the Local Caching
DNS Server checks its local cache for the IP address of the Authoritative DNS Server. In
this model, the Authoritative DNS Server is always known.

V15.0 Page 42 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

3. The Authoritative DNS Server replies to the DNS Query received from the Local Caching
DNS Server with either the IP address of the MMS Hub to use or the destination MMSC,
or, a list of FQDNs and/or IP addresses if the query was for an MX record.
4. The Local Caching DNS Server replies to the DNS Query received from the MMSC (in
step 1) with the result obtained from the Authoritative DNS Server. The MMSC then
commences an SMTP session either with Operator B's MMSC, or, to an identified MMS
Hub, to transfer the MM.
Note that there is more flexibility in the MMS Hub architecture than shown above, depending
on the MMS Hub provider used e.g. some Hub providers offer MSISDN/E.164 number
conversion/resolving, some offer complete hosting of the MMSC, and so on. See GSMA
PRD IR.52 [9] for more information on MM delivery using an MMS Hub, including a more full
description of the flexibility available in the architecture.

Note also that the Local Caching DNS Server could also be the Authoritative DNS Server for
the requested FQDN, in which case a final result can be given immediately to the MMSC.

4.3.4 MM delivery based on NAI/e-mail address

For MMs addressed to an NAI/e-mail address (as defined in IETF RFC 2822 [15]), the
message flow is the same as in Figure 7 except that the Internet's root DNS servers and
authoritative DNS servers are used, possibly with the use of referral DNS servers too.

4.4 WLAN Inter-working

4.4.1 Introduction
Figure 9 shows how local login and roaming login differ; it also demonstrates how Roaming
Partners actually connect to each other via inter-operator network. Case 1 is an example of
normal local login in the hot spot of Visited PLMN, where the user inserts his username &
password and is authenticated in the Visited PLMN. In this case, the RADIUS Roaming
Network is not utilised.

Case 2 in Figure 9 refers to a roaming login, where the user inserts his username (with
realm) and password in the hot spot of the Visited PLMN and authentication and request is
sent by way of a proxy to Home PLMN. The User is then authenticated in the Home PLMN.
Necessary RADIUS messages are transferred between RADIUS Roaming Proxies using the
IP based Inter-PLMN network, that is, the GRX/IPX.

Figure 9 shows also in principle the difference between the following two authentication
methods:

 Web Based Authentication

 SIM Based Authentication

Web Based (that is, using username/password) authentication is considered as an existing

first phase solution for the WLAN authentication. However, in the future there will be a target
solution utilising EAP solutions, where the Home PLMN HLR is involved.

V15.0 Page 43 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

Figure 11: WLAN user authentication mechanism

The GRX/IPX network is used for transporting RADIUS authentication and accounting
messages for WLAN roaming services only, WLAN user data is not carried over GRX/IPX.

The IP address of the WLAN Roaming Proxy must be reachable via the GRX/IPX. Please
note that the first phase of WLAN roaming will not use the GRX/IPX Root DNS at all since
the IP addresses of the Home PLMN RADIUS server is statically configured in the Visited
PLMNs RADIUS server (the "next hop" list). In fact, RADIUS does not provide for a DNS
type solution for realm to AAA entity mapping. The utilising of Root DNS may be required in
future WLAN roaming solutions where Diameter instead of RADIUS is used, as Diameter
does provide for an optional realm to AAA entity mapping.

More information on WLAN roaming can be found in GSMA PRD IR.61 [10].

4.5 IP Multi-media core network Sub-system (IMS)

4.5.1 Introduction
The IP Multi-media core network Sub-system (IMS) provides a standardised architecture for
providing feature rich multimedia services/applications, such as speech communication,
real-time and turn-based gaming, shared online whiteboards etc. IMS services/applications
rely on sessions managed by the Session Initiation Protocol (SIP), as defined in IETF RFC
3261 [38], and profiled in 3GPP TS 24.229 [35] (which includes a set of standardised
extensions) for use by Service Providers.

V15.0 Page 44 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

Diameter is also used on some interfaces in the IMS architecture, however, these are
intra-Service Provider interfaces and so are outside the scope of this PRD.

Figure 10 shows an end-to-end IMS session. Only the basic architecture of involved IMS
network elements is shown. Please note that signalling and user data of an IMS session are
separated. Signalling and user data make use of different PDP contexts, but use the same
(originating) IP address.

Home Network Home Network

IM Subsystem IM Subsystem
S-CSCF S-CSCF
Home Network A Mm Home Network B
Mm
P-CSCF I-CSCF I-CSCF P-CSCF
Inter-PLMN
Inter-Network
BG BG
IM Backbone
IP Backbone

UE SGSN GGSN GGSN SGSN UE

Gi Gi

Figure 12: IMS Session Inter-working

IMS subscribers are addressed by SIP URIs or E.164 numbers represented as Tel URIs or
SIP URIs with the "user=phone" option. ENUM is specified in IMS as the means to convert
an E.164 number into a SIP URI. See [56] for more information on ENUM Guidelines for
Service Providers and IPX Providers.

For resolving SIP URIs to SIP Servers (see IETF RFC 3263 [17]), support of the NAPTR
Resource Record functionality (as defined in IETF RFC 3404 [6]) and SRV Resource Record
functionality (as defined in IETF RFC 2782 [18]) is needed in a Service Provider's DNS
servers.

More information on IMS roaming and interworking can be found in GSMA PRD IR.65 [11].

4.5.2 SIP server configuration

There are several RFCs covering use of SIP in the DNS. These include IETF RFC 3824
[24], IETF RFC 3263 [17], and IETF RFC 3403 [6].

The reason this configuration is needed is as follows:

When a SIP session is initiated by a user, they address the session to either a SIP URI (e.g.
[email protected]) or an E.164 number. In both cases, the IMS needs to know the IP
address of the SIP server to which it can route the session. The SIP server information
contains the detail needed to provide the destination network's SIP server IP address to the
calling network based on the information in the SIP URI.

V15.0 Page 45 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

The approach described in this section is compliant with these RFCs and consists of 4
separate steps. It is consequently known as the “4-step approach”.

In order to improve performance/session establishment time, use of explicit IP addresses

instead of FQDNs eliminates the need for some DNS lookups and retains compatibility with
existing standards. However, using IP addresses instead of FQDNs is more restrictive.

4.5.2.1 Step 1
This is the ENUM related step and is performed only for cases where the service has been
addressed to an E.164 number. An IMS call to a user using the format [email protected]
would not require this step. Example of DNS data for a particular SIP URI and its servers
can be found in section 4.5.2.

4.5.2.2 Step 2
Having obtained the destination domain name the DNS is asked to provide matching SIP
Server Location Information. One or more NAPTR records may be retrieved and the calling
application examines these records to find the best match based on priorities and the
desired SIP protocol variant:
mnc001.mcc234.3gppnetwork.org. IN NAPTR 50 100 "s" "SIP+D2U" "" _sip._udp.example.com.
mnc001.mcc234.3gppnetwork.org. IN NAPTR 90 100 "s" "SIP+D2T" "" _sip._tcp.example.com.
mnc001.mcc234.3gppnetwork.org. IN NAPTR 90 100 "s" "SIPS+D2T" "" _sips._tcp.example.com.

In the above example, “D2U” indicates UDP-based SIP, “D2T” indicates TCP-based SIP,
and “SIPS+D2T” indicates UDP-based unencrypted SIP.

The presence of these fields indicates what variations of SIP are supported on a given SIP
server.

The "s" flag means the next stage is to look up an "SRV" record

4.5.2.3 Step 3
An example set of SIP server SRV records is as follows:

_sip._tcp.example.com. SRV 0 1 5060 sipserv1.example.com.

_sip._tcp.example.com. SRV 0 2 5060 sipserv2.example.com.
_sip._udp.example.com. SRV 0 1 5060 sipserv1.example.com.
_sip._udp.example.com. SRV 0 2 5060 sipserv2.example.com.
_sips._tcp.example.com. SRV 0 1 5060 sipserv3.example.com.
_sips._tcp.example.com. SRV 0 2 5060 sipserv4.example.com.

For each of the variations of the SIP protocols supported the SRV records describe:

 name of the server;

 which port number SIP uses; and
 where there are multiple servers, the weights & priorities to allow rough load
balancing.

V15.0 Page 46 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

The calling network asks the DNS for a SRV record for the host corresponding to the specific
service/protocol/domain combination that was returned in Step 2

If there are multiple records with the same service/protocol/domain combination, the caller
must sort the records based on which has the lowest priority. If there is more than one
record with the same priority, the record with the highest weight is chosen.

From the SRV record get the corresponding server name.

There is potential flexibility in this step for the destination operator to receive the SIP traffic
on different servers depending on the desired variation of the SIP protocol – TCP, UDP,
encrypted, unencrypted.

4.5.2.4 Step 4
For the server name returned in Step 3, do a standard DNS lookup to finds its IP address

This is a normal "A" (address) record lookup

sipserv1.example.com. IN A 101.1.2.3
sipserv2.example.com. IN A 101.1.2.4

4.5.3 Domain Names used

The domain names used for IMS based services are SIP Server names, however, there are
no restrictions in the standards as to what these domain names shall be (other than the
normal FQDN rules, as specified in the likes of IETF RFC 1034 [1] and IETF RFC 1035 [2]).
However, for service providers interconnecting across the GRX/IPX network, it is
recommended to use an MCC/MNC sub domain of ".3gppnetwork.org" as this is supported
already on the GRX/IPX DNS and also allows for SIP URIs returned using ENUM on the
GRX/IPX as specified in section 5.

It should be noted that right now, more "user friendly" domain names are not yet directly
supported on the GRX/IPX DNS. Work on supporting a much wider set of domain names is
ongoing.

4.6 Generic Authentication Architecture (GAA)

4.6.1 Introduction
The Generic Authentication Architecture is defined in 3GPP TS 33.220 [19]. It is a
standardised mechanism for securely distributing shared keys for later use by applications
on the UE.

NOTE: The address of the Bootstrapping Server Function (BSF) used by the UE is
dependent on whether USIM or ISIM is used in bootstrapping. See 3GPP TS
23.003 [8], section 16.

V15.0 Page 47 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

4.7 Generic Access Network (GAN)

4.7.1 Introduction
The Generic Access Network is defined in 3GPP TS 43.318 [20] and 3GPP TS 44.318 [21].
It provides for using unlicensed radio spectrum for accessing the GSM core network in order
to provide normal GSM services including both CS and PS. It was based on the work done
by the UMA forum.

4.8 Secure User Plane Location (SUPL)

4.8.1 Introduction
The Secure User Plane Location feature is defined in OMA
OMA-AD-SUPL-V1_0-20070615-A [27]. It provides a mechanism for carrying location
information between a user's SUPL Enabled Terminal (SET) and SUPL Location Platform
(SLP) in a Service Provider's network, in a way that does not rely on modifications to any
network interfaces or elements between the SET and SPL. This information can then be
used by the Service Provider to calculate the SET's location.

4.9 Enhanced Packet Core (EPC)

4.9.1 Introduction
The Enhanced Packet Core is defined in 3GPP TS 23.401 [28] and 3GPP TS 23.402 [29]. It
provides for a new and much more efficient PS core network to support E-UTRAN and
serves as part of the Enhanced Packet System (EPS).

It should be noted that EPC used to be known as SAE (Service Architecture Evolution) and
E-UTRAN used to be known as LTE (Long Term Evolution) RAN.

4.10 IMS Centralised Services (ICS)

4.10.1 Introduction
The IMS Centralised Services feature is defined in 3GPP TS 23.292 [30]. It enables the
provisioning of Supplementary Services and value added services (such as those offered
today via CAMEL) to the CS domain from IMS.

4.11 Access Network Discovery Support Function (ANDSF)

4.11.1 Introduction
The Access Network Discovery Support Function (ANDSF) is defined in 3GPP TS 23.402
[29]. It contains data management and control functionality necessary to provide network
discovery and selection assistance data according to Service Provider policy. The ANDSF
responds to requests from the UE for access network discovery information and may be able
to initiate data transfer to the UE, based on network triggers.

V15.0 Page 48 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

4.12 Mobile Broadcast Services (BCAST)

4.12.1 Introduction
Mobile Broadcast Services is a service enabler defined by the OMA in
OMA-TS-BCAST_Service_Guide-V1_1-20100111-D [40]. This enables service/content
providers to describe the services and content available (either free, subscription or one-off
fee) and how to access them as Mobile Broadcast services either over a Broadcast Channel
or over an Interaction Channel. From the user perspective the Service Guide can be seen as
an entry point to discover the currently available or scheduled services and content, and to
filter those based on their preferences.

Discovery of a Service Guide Function is performed using DNS SRV records, or optionally,
using an FQDN derived from the IMSI, as specified in section 6.2.1 of
OMA-TS-BCAST_Service_Guide-V1_1-20100111-D [40]. The domain name to use when
deriving the FQDN from the IMSI is specified in section 2.3 of the present document.

4.13 The XCAP Root URI on Ut Interface for MMTEL/IMS profile for Voice and
SMS (XCAP)

4.13.1 Introduction
XCAP is a protocol defined in IETF RFC 4825 [44], 3GPP TS 24.623 [45], and is part of the
IMS profile for Voice and SMS documented in IR.92 [46]. This is used in manipulation of
supplementary service configuration.

The XCAP Root URI is defined in IETF RFC 4825 [44], and is used to identify the XCAP
Root, which is a context that contains all the documents across all application usages and
users that are managed by the XCAP server.

The XCAP Root URI takes the following format: "http://xcap.domain"

The domain part of the XCAP Root URI is derived in accordance with 3GPP TS 23.003 [8],
section 13.9.

4.14 RCS - Rich Communication Suite

4.14.1 Introduction
RCS/RCS-e as specified in the RCS/RCS-e specifications [48] is a simple and interoperable
evolution to voice and text, which enables customers to send instant messages, video chat
and exchange files in real time, that is rich call with content sharing, chat, file sharing etc. All
functions are built into the address book of mobile devices. RCS/RCS-e focuses on the
communications service aspects building on established interoperability principles within the
mobile operator ecosystem providing service definition, functional description and technical
realisation to develop new service packages for today's 'always-on' mobile users enabling
seamless user experience.

The description and the use of the reserved subdomain names will be referenced in the
RCS/RCS-e specifications where this domain can be used by all RCS/RCS-e specification
versions.

V15.0 Page 49 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

4.15 Evolved Packet Data Gateway (ePDG)

4.15.1 Introduction
The Evolved Packet Data Gateway is defined in 3GPP TS 23.402 [29]. It provides PDN
connectivity to the Evolved Packet Core (EPC) over untrusted non-3GPP IP access
networks.

4.16 Network element self-configuration

4.16.1 Introduction
The concept of network element self-configuration is described in 3GPP TS 32.501 [50]. The
network elements self-configuration can be applied e.g. for eNBs that is defined in 3GPP TS
36.300 [51].

4.17 EPC and GPRS coexistence

4.17.1 Introduction
When configuring the authoritative DNS server, a mobile operator supporting both GPRS
and EPC roaming must consider that different DNS query procedures can be used in GPRS
(A/AAAA-record queries) compared with EPC (S-NAPTR queries).

GSMA PRD IR.88 [52] provides further details on the DNS configuration requirements for
different GPRS (2G/3G) and EPC coexistence scenarios.

4.18 MBMS Service Announcement Bootstrapping

4.18.1 Introduction
The method for bootstrapping for MBMS service announcement is described in 3GPP TS
26.346 [53]

5 Processes and Procedures relating to DNS

5.1 Introduction
This section describes the processes and procedures relating to DNS that apply to Service
Providers and GRX/IPX Providers.

5.2 Existing domains/sub-domains on the GRX/IPX network and their

Allocation
The domain names for use by Service Providers on the GRX/IPX network are the following:

 .gprs
 .3gppnetwork.org
 .ipxsp.org
 .e164enum.net

Only the sub-domains listed in section 2.3.3 for each of the above domains should be used.

V15.0 Page 50 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

The domain name ".e164enum.net" is used only for Carrier ENUM on the GRX/IPX; see [56]
for more information.

The domain names for use by GRX/IPX Providers on the GRX/IPX are the same as those
above, when a GRX/IPX Provider is hosting services on behalf of a Service Provider. For all
other services and also for GRX/IPX network equipment (for example routers, MMS Hubs,
etc.), it is recommended to use ipxnetwork.org, see section 2.3.3. The ".grx" domain name
also is commonly used, but should be reserved for legacy equipment on the GRX network.
The sub-domains on “.grx” and “ipxnetwork.org” are agreed amongst other GRX/IPX
Providers and assigned on a first come – first served basis in order to guarantee uniqueness
(a good place to discuss this with other GRX/IPX Providers is the GRX Working Party).

5.3 Procedures relating to new domain names on the GRX/IPX network

New domain names may be added to the GRX/IPX network's DNS by any Service Provider
or GRX/IPX Provider, in order to enable further services to be used on the NNI provided by
the GRX/IPX network. This could be to allow such things as resolution of domain names
used for national interconnect agreements, and so on. However, wherever possible, the
existing sub-domains of the domain names specified in section 2.3.3 should be reused.

It is recommended that new domain names to be added to the GRX/IPX network's DNS are:

 a sub-domain of a Country Code Top Level Domain (ccTLD);

 registered/reserved on the Internet, in order to prevent any issues of ownership;
 not provisioned on the Internet (that is. not resolvable, at least no more than is
absolutely necessary for example to retain ownership as per the rules of some ccTLD
authorities);
 hosted in their own authoritative DNS server(s) on the GRX/IPX network, which is
linked from the GRX/IPX Root DNS that is by using NS record entries (this eases
administration of the new domain name and also prevents the GRX/IPX Root DNS
becoming unmanageable); and
 used by an entity in addition to either their
"mnc<MNC>.mcc<MCC>.3gppnetwork.org" domain name or "spn<SPN>.ipxsp.org"
domain name, as specified in section 2.3.3 (amongst other things, this enables
network node naming as per section 2.4).

The hosting authoritative DNS server(s) need to be reachable and respond to queries from
all Service Providers and/or GRX/IPX Providers that need to resolve associated FQDNs.
Ideally, access should be allowed to all entities on the GRX/IPX network, but only those who
need to should have their queries properly serviced; the rest should be returned a standard
DNS or ICMP error.

Care should be taken to not inadvertently force another entity who is denied
access/resolvability of the domain name into (automatically or otherwise) trying to resolve it,
including (but not necessarily limited to):

 by using only the new domain name in general network node naming (network node
naming should still be done as per section 2.4, using the domain names
recommended therein); and

V15.0 Page 51 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

 by returning it in a NAPTR and/or SRV record (for example as used in IMS/SIP,

ENUM, EPC).

For domain names that need to be resolvable on the UNI, the Internet DNS should always
be used. By design, the GRX/IPX DNS provides resolution only for entities connected to the
NNI.

5.4 Description of the Master Root DNS service and modality of access

5.4.1 Master Root DNS services

5.4.2 Master Root DNS services

The Master Root DNS provides authoritative naming management and address resolution
mechanisms for the GSMA community that includes GRX Providers, IPX Providers and
Mobile Network Operators. This translates into two main functions:

 Assignment and administration of domain names according to IR67 specification

 DNS zone transfer and query resolution services

In the SOA record of the root DNS a refresh timer of 900 seconds and a retry timer of 900
seconds is configured for the zones GPRS and 3GPPNETWORK.ORG. The root slaves
DNS servers will try to update the configuration once every 15 minutes.

The Root DNS is currently available at three peering locations (Amsterdam in the
Netherland, Singapore and Ashburn in the United States). Additional locations can be added
as necessary.

5.4.3 How to access Master Root DNS services

For an entity (GRX/IPX Provider or Mobile Network Operator) to connect to the Root DNS
and access its services it is required to first register and become a “participant”. The
registration involves a light accreditation process to verify the identity the entities connecting
to system and the intended use of the services.

The accreditation process is simple and usually requires five working days. As part of the
accreditation process the entity is required to fill in a form called the “participating
agreement”. The participating agreements contains the terms and conditions for the use of
the service and some basic information of the applying entity such company name, technical
and administrative contract, GRX/IPX peering points.

Once it has been completed the form is sent to the Master Root DNS operator (Neustar) that
is responsible to check and verify the information provided using appropriate sources
including the IR21 database. If the verification is passed a contract is sent to the applying
entity to be signed. If information is missing or incorrect the applying entity is required to
resubmit the participating agreement.

If an application request is either controversial or unsuccessful, it is escalated to GSMA staff

for their consideration and their final decision. The applying entity can appeal against a
rejection by contacting the GRX/IPX chair.

V15.0 Page 52 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

Once the accreditation process has been completed and the contract has been signed, the
Root DNS customer is activated. As part of the activation process a customer account is
created in the system and a secureID Token is send to the “participant” with password
activation to allow the customer access the system through a secure web portal interface
over the Internet. The peering between the customer and the Root DNS is established and
tested. As final step of the activation process the customer’s name servers are provisioned
in the Master Root DNS system.

Once the activation process is completed the customer can start provisioning information in
the Root DNS through the web portal. The customer then can create, delete, modify and
transfer domain names on behalf of Mobile Operators and its other customers according to
the rules defined in IR67.

For any administrative, technical and operation issue regarding the service, including the
form required for the accreditation process, please contact [email protected].

5.5 Delegation of sub-domains of “pub.3gppnetwork.org”

GSMA can delegate a sub-domain of pub.3gppnetwork.org to DNS of an MNO. The routine
specified by GSMA operations, that the MNO needs follow to do this, consists of the
following steps:

1. Identify MCC and MNC values for the MNO.

2. Identify CNAME record for the domain to be transferred.

The CNAME record shall be in format of:

<ABC>.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org

where

acceptable values of <ABC> are defined in 2.3.4 (other values might be added as
needed; see also NOTE 2 below)

<MNC> and <MCC> have to be replaced by respective values of the home network in
decimal format, with a 2-digit MNC padded out to 3 digits by inserting a 0 at the
beginning.

NOTE 1: For RCS configuration server CNAME record should be in format of

http://config.rcs.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org

NOTE 2: An operator may wish to delegate the entire

mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org sub-domain.

3. Create the Zone File on the MNO’s own NameServer/DNS with the CNAME record
specified in step 2.

4. Complete the Request Form in Annex D.1 and - if required for your use of the sub-
domain - also the Letter of Authorization in Appendix D.2, and send both to GSMA
at [email protected]

V15.0 Page 53 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

NOTE 3: the Letter of Authorization format (Annex D.2) may need to be adapted
dependent on your selected Certificate Body’s requirements. If in doubt,
please contact a Certificate Body of your choice, and obtain a necessary
template to be filled in by MNO and signed by GSMA as the registrant of
3gppnetwork.org domain.

5. GSMA will process the request, delegate the requested subdomain to MNO’s
DNS, and return a signed copy of the Letter of Authorization to MNO.

NOTE 4: the typical maximum lead time to process the Request Form and sign the
Letter is five (5) working days.

NOTE 5: the requesting MNO is responsible for submitting the Letter to their
Certificate Authority.

V15.0 Page 54 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

Annex A Sample BIND DNS Configuration for GPRS

A.1 Introduction
All sample configurations of this annex are in valid syntactical format for the ISC BIND DNS
server software. However, the samples are not from actual DNS configuration and contain
only example information, including sample IP addresses which are not valid. They are
provided for illustration purposes only. It is therefore highly recommended NOT to use these
samples in live networks! The GSM Association takes no responsibility of the usage of these
configurations in any operators DNS servers and/or live networks.

A.2 The "named.conf" file

The "named.conf" file has configuration information for BIND software. Following is only the
necessary configuration to get DNS running. There are many more options that may also be
useful, but which are not shown here, simply for making the examples as simple as possible.

A.2.1 The "named.conf" file for a PLMN Master Nameserver

options {
directory "/var/named";
}; // where the files reside
zone "." in {
type hint;
file "gprs.hint";
}; // gprs root servers
zone "0.0.127.in-addr.arpa" in {
type master;
notify no;
file "master/0.0.127.in-addr.arpa";
}; // only contains information about localhost.
/*
* PLMN domain information
*/
zone "mnc091.mcc244.gprs" in {
type master;
file "master/mnc091.mcc244.gprs";
};
zone "sonera.fi.gprs" in {
type master;
file "master/sonera.fi.gprs";
}; // human readable operator id
zone "168.192.in-addr.arpa" in {
type master;
file "master/168.192.in-addr.arpa";
};

V15.0 Page 55 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

A.2.2 The "named.conf" file for a PLMN Slave Nameserver

options {
directory "/var/named";
}; // where the files reside
zone "." in {
type hint;
file "gprs.hint";
}; // gprs root servers
zone "0.0.127.in-addr.arpa" in {
type master;
notify no;
file "master/0.0.127.in-addr.arpa";
}; // only contains information about localhost.
/*
* PLMN domain information
*/
zone "mnc091.mcc244.gprs" in {
type slave;
file "slave/mnc091.mcc244.gprs";
masters {192.168.1.2;} // address of master nameserver
};
zone "sonera.fi.gprs" in {
type master;
file "slave/sonera.fi.gprs";
masters {192.168.1.2;} // address of master nameserver
}; // human readable operator id;
zone "168.192.in-addr.arpa" in {
type slave;
file "slave/168.192.in-addr.arpa";
masters {192.168.1.2;} // address of master nameserver
};

A.3 Zone Configuration Files

Recommended values for SOA records are as specified in ripe-203.

A.3.1 The "gprs.hint" file

This file contains ".gprs" root nameservers needed to initialise cache of ".gprs" nameservers.
Note that the “.” character is indeed significant.

. 518400 IN NS dns0.root.gprs.
dns0.root.gprs. IN A 172.22.1.5
. 518400 IN NS dns1.root.gprs.
dns1.root.gprs. IN A 10.254.243.7
. 518400 IN NS dns2.root.gprs.
dns2.root.gprs. IN A 192.168.17.232

V15.0 Page 56 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

A.3.2 The "0.0.127.in-addr.arpa" file

This file contains only information about localhost i.e. 127.0.0.1

$TTL 172800
@ IN SOA localhost.. hostmaster.localhost. (
2000030701 ; serial (YYYYMMDDvv)
86400 ; refresh (24 hours)
7200 ; retry (2 hours)
3600000 ; expire (1000 hours)
172800 ) ; minimum time to live (2 days)
1 IN PTR localhost.

A.3.3 PLMN zone files

PLMN may configure both mnc.mcc.gprs and operaror.cc.gprs type domains that will share
exactly the same host information. In addition, early versions of GTPv0 did not have leading
zeroes to make mnc code always 3 digits long. In order to minimise both configuration work
and possible errors, zone files may include a common host configuration.

A.3.3.1 The "mnc091.mcc244.gprs" file

$TTL 172800
@ IN SOA mnc091.mcc244.gprs. hostmaster.mnc091.mcc244.gprs. (
2000030701 ; serial (YYYYMMDDvv)
86000 ; refresh (24 hours)
7200 ; retry (2 hours)
3600000 ; expire (1000 hours)
172800 ) ; minimum time to live (2 days)
IN NS dns0
IN NS dns1
$INCLUDE master/hosts

A.3.3.2 The "sonera.fi.gprs" file

$TTL 172800
@ IN SOA sonera.fi.gprs. hostmaster.sonera.fi.gprs. (
2000030701 ; serial (YYYYMMDDvv)
86400 ; refresh (24 hours)
7200 ; retry (2 hours)
3600000 ; expire (1000 hours)
172800 ) ; minimum time to live (2 days)
IN NS dns0
IN NS dns1
$INCLUDE master/hosts

A.3.4 The "hosts" file

This file contains IP address records for all hosts in the PLMN. The origin changes
depending on which file includes the contents i.e. after the names not ending at dot, the
current domain name is appended automatically.

Load balancing may be performed configuring same access point with several IP addresses
that actually are on different GGSNs. In this case, addresses are used in round-robin

V15.0 Page 57 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

fashion. However, DNS information is cached and a new query is performed only when the
TTL (time-to-live) has expired. Therefore TTL of 0 seconds is configured for load balanced
access points.

dns0 IN A 192.168.1.2
dns1 IN A 192.168.2.2
;
; router
helsinki-rtr-1-fe-0-0 IN A 192.168.1.254
helsinki- rtr-1-fe-0-1 IN A 192.168.2.254
helsinki- rtr-1-fe-0-2 IN A 192.168.3.254
helsinki- rtr-1-s-1-0 IN A 172.22.5.6
;
; access point
ibm.com IN A 192.168.1.5
;
; load balanced access point
compaq.com 0 IN A 192.168.1.5
0 IN A 192.168.2.5
;
; service access point
internet IN A 192.168.2.2
;
; GGSN
helsinki-ggsn-15 IN A 192.168.1.5
helsinki- ggsn-25 IN A 192.168.2.5
helsinki- ggsn-22 IN A 192.168.2.2
;
; SGSN
helsinki-sgsn-1 IN A 192.168.3.3
; SGSN with RAI
racF1.lac12EF IN A 192.168.3.3

V15.0 Page 58 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

A.3.5 The "168.192.in-addr.arpa" file

There may be several PTR records so that each name associated with and address may
have reverse mapping also. Note that IP address is reversed in in-addr.arpa domain i.e.
192.168.1.254 will be 254.1.168.192.in-addr.arpa.

$TTL 172800
@ IN SOA dns0.sonera.fi.gprs. hostmaster.sonera.fi.gprs. (
2000030701 ; serial (YYYYMMDDvv)
86400 ; refresh (24 hours)
7200 ; retry (2 hours)
3600000 ; expire (1000 hours)
172800 ) ; minimum time to live (2 days)
IN NS dns0.sonera.fi.gprs.
IN NS dns1.sonera.fi.gprs.
5.1 IN PTR ibm.com.sonera.fi.gprs.
PTR ibm.com.mnc091.mcc244.gprs.
PTR compaq.com.sonera.fi.gprs.
PTR compaq.com.mnc091.mcc244.gprs.
PTR helsinki-ggsn-15.sonera.fi.gprs.
PTR helsinki- ggsn-15.mnc091.mcc244.gprs.
254.1 IN PTR helsinki-rtr-1-fe-0-0.sonera.fi.gprs.
PTR helsinki- rtr-1-fe-0-0.mnc091.mcc244.gprs.
2.2 IN PTR internet.sonera.fi.gprs.
PTR internet.mnc091.mcc244.gprs.
PTR helsinki-ggsn-2.sonera.fi.gprs.
PTR helsinki- ggsn-2.mnc091.mcc244.gprs.
5.2 IN PTR compaq.com.sonera.fi.gprs.
PTR compaq.com.mnc091.mcc244.gprs.
PTR helsinki-ggsn-25.sonera.fi.gprs.
PTR helsinki-ggsn-25.mnc091.mcc244.gprs.
254.2 IN PTR helsinki-rtr-1-fe-0-1.sonera.fi.gprs.
PTR helsinki-rtr-1-fe-0-1.mnc091.mcc244.gprs.
3.3 IN PTR helsinki-sgsn-1-fe.sonera.fi.gprs.
PTR helsinki-sgsn-1-fe.mnc091.mcc244.gprs.
PTR racF1.lac12EF.sonera.fi.gprs.
PTR racF1.lac12EF.mnc091.mcc244.gprs.
254.3 IN PTR helsinki-rtr-1-fe-0-2.sonera.fi.gprs.
PTR helsinki-rtr-1-fe-0-2.mnc091.mcc244.gprs.

V15.0 Page 59 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

Annex B Forms for transfer of sub-domain of

“pub.3gppnetwork.org”

B.1 Request form

V15.0 Page 60 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

Request Form for Transfer of sub-domain of pub.3gppnetworks.org

Organisation:

Title:
IT Contact at MNO Name:

Email:

Mobile Number:

MNO Name:
MNO Information MCC Value:

MNC Value:

*CNAME record for provisioning

domain for an MNO shall follow the
format:

<ABC>.mnc<MNC>.mcc<MCC>.pub.3
gppnetwork.org
CNAME record for MNO ___.mnc___.mcc___.pub.3gppnetwork.org
where <MNC>=mnc value of MNO,
<MCC>=mcc value of MNO,
both values padded to 3 digits with
a leading "0" if it is 2-digit long.

Is Zone File for the identified

ZONE file for CNAME CNAME record created on MNO's YES / NO
DNS servers?

Name / IP Address

Please provide MNO's DNS server

DNS Server Details
details, where the ZONE file for
(IP Address & FQDN)
CNAME record had been created.

Please fill in and email "Letter of

Authorization for the transfer of the
Letter of Authorization domain" document to
3gppnetwork.org_delegation@gsm
a.com

Organisation:

Title:

Name:
Requestee Email Address:

Mobile Number:

Date:

Signature:

V15.0 Page 61 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

B.2 Letter of Authorization Template

Please fill out all required fields in the template and replace <ABC>, <MNC> and <MCC> as
specified in 6.5.

This letter can be adapted as per MNO’s selected Certificate Body’s requirement. The letter
must be signed by GSMA.

V15.0 Page 62 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

<Certificate Organisation Name>

<Contact Name at Certificate Organisation>

<Certificate Organisation Address>

<Certificate Organisation Fax Number/Email address>

Date: <Please type date>

To whom it may concern,

Dear Sir/Madam,

Re: Domain Authorization Letter

I confirm that:

Organization enrolling for the Digital Certificate set out below is: <Please type your MNO’s
full company name here> (“Certificate Applicant”)

Domain to be included in the certificate is:

<ABC>.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org (“Domain”)

Registrant of the Domain is: GSM Association (“Registrant”)

Digital Certificate is the certificate relating to the Domain.

I am employed by the Registrant and am duly authorized to sign this Domain Authorization
Letter and to deal with all matters related to the registration of the Domain.

Certificate Applicant desires to install the Digital Certificate on its web server(s) for the
domain and ultimately to enable secure communications with its users.

V15.0 Page 63 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

Registrant acknowledges that it has granted the Certificate Applicant the right to use the
Domain as a common name in the Digital Certificate request referenced above and to
otherwise use the Domain in connection with its business.

Regards,

Full Name: Javier sendin

Job Title: Technical Director

Organization: GSM Association

Signature:__________________________

V15.0 Page 64 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

Annex C Document Management

C.1 Document History

Approval Editor /
Version Date Brief Description of Change
Authority Company
0.1.0 14 October First draft – skeleton. Nick Russell,
-
2004 Vodafone
0.2.0 10 May Second draft, with most sections Nick Russell,
-
2005 filled in, or at least with place holders. Vodafone
0.2.1 11 May Changed the underlying Word Nick Russell,
-
2005 template to the new one. Vodafone
0.3.0 15 Enhancements of ENUM section,
November including addition of Number Nick Russell,
-
2005 Portability in ENUM, plus minor Vodafone
corrections and update of template.
0.9.0 16 Final draft for publication; contains
Nick Russell,
December only minor corrections to formatting -
Vodafone
2005 since previous version.
16
Nick Russell,
1.0 December Approved for publication. DAG
Vodafone
2005
26 January Nick Russell,
1.1 Minor formatting corrections. IREG
2006 Vodafone
Moved in the DNS information from
IR.34, ENUM section updated with
the agreements made in the ENUM
adhoc, updated the list of domains to
provide a list with those defined in
4 April IREG Nick Russell,
1.2 and/or before 3GPP specification set
2006 Packet Vodafone
Rel-6.

This version of the present document

is the first version to be classified as
"Unrestricted".
Clarification of references to 3GPP
documents (to show which specific
release is being referenced), addition
of health warnings about the old
9 August IREG Nick Russell,
1.3 MMS URI prefix and ENUMservice
2006 Packet Vodafone
field values, addition of health
warning about SIP URI provisioning
and some general
tidying-up/consolidation of text.
2.0 30 April Addition of the "No Root" ENUM
Nick Russell,
2007 architecture, plus some other DAG
Vodafone
miscellaneous corrections.

V15.0 Page 65 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

Approval Editor /
Version Date Brief Description of Change
Authority Company
2.1 18 October Minor restructuring to move ENUM
2007 material into own section, clarification
in GPRS section and MMS section
on using iterative rather than
recursive DNS queries, clarification in IREG Nick Russell,
MMS section of DNS usage when Packet Vodafone
utilising one or more MMS Hubs and
direct interconnects, and renaming of
"No Root" ENUM model to "Multiple
Root".
2.2 14 April Addition of information on OMA's
2008 SUPL feature, including domain
name used and a new section giving
a brief overview of the feature (CR
#10). Also, some minor corrections to IREG Nick Russell,
the ENUM section are provided (CR Packet Vodafone
#11). Finally, a global replacement of
"MNO" to "Service Provider" has
been done, in-line with IPX
terminology.
3.0 26 Includes new GSMA logo on
September coversheet, change of "Operators" to
2008 "Service Providers" in the spec title,
and implementation of the following
CRs:
CR #12 (major): Implementation of
the conclusion from the ENUM White
Paper (EWP), plus other minor
corrections/enhancements. This
includes corrections to domain
names in sub-sections of 5.7
CR #13 (minor): Addition of EPC and
ICS specific sub-domains for DAG and
Nick Russell,
.3gppnetwork.org. IREG
Vodafone
CR #14 (minor): Addition of new sub- Packet
section to ENUMservices section to
specify the content of the
ENUMservices field for services
other than just those based on
IMS/SIP and MMS.
CR #15 (minor): Addition of
information about domain names,
including clearer indication of the
current limitations of the GRX/IPX
domain names currently supported.
Some minor editorial, non-technical
impacting corrections are also made.

V15.0 Page 66 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

Approval Editor /
Version Date Brief Description of Change
Authority Company
3.1 8 Corrections to footer, plus
December implementation of the following CRs:
2008 CR #16 (minor): Addition of the
definition of the "user=phone" SIP
URI parameter in URIs returned in IREG Nick Russell,
IMS related ENUM responses. Packet Vodafone
CR #17 (minor): Correction to 4.5.1
(IMS section) to state that support of
NAPTR RRs are required in order to
support SIP/IMS.
3.2 6 May 2009 Implementation of CR # 18 (minor):
editorial enhancements to sections 1-
4, and implementation of the recently
IREG Nick Russell,
approved sub-domains of
Packet Vodafone
3gppnetwork.org (as requested by
3GPP and approved at Packet #37
and on email).
3.3 21 July Implementation of the following CRs:
2009 CR #19 (minor): Add Internet
assigned domain names to be used
as a sub-domain under
"3gppnetwork.org", in order to save
all Service Providers connected to
the IPX network to have to obtain an
E.212 number range in order to be
addressable. Also, the procedures
section is updated to reflect this
change, and also better describe the
current state-of-the-art.
CR #20 (minor): Add IR.33 (GPRS
Roaming Guidelines) in the
IREG Nick Russell,
references section, add a new
Packet Vodafone
domain name to be used for naming
of non-service specific nodes, add a
new section on hostnames and
domains (based on content from
IR.33), provide extra detail on DNS
Server software (also based on
content from IR.33), add new section
on DNS Server naming, add new
section on Resource Record usage,
and add references to IR.33 and the
GTP spec (3GPP TS 29.060) in
section 4.2 (GPRS). Also, some
instances of "operator" are corrected
to "Service Provider".
4.0 10 Implementation of CR #21 (Major):
December To document the lessons learned
2009 after the ENUM trial, and to make the
whole specification of the GRX/IPX Nick Russell,
DAG #64
Carrier ENUM take a more top-down Vodafone
approach.

New template also applied.

V15.0 Page 67 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

Approval Editor /
Version Date Brief Description of Change
Authority Company
4.1 3 March Implementation of CR #22 (Minor):
2010 addition of "bcast" sub-domain to
"mnc<MNC>.mcc<MCC>.pub.3gppn
IREG
etwork.org". Minor editorial
Packet Nick Russell,
corrections also made, including
(email Vodafone
clarification on a zero being inserted
approval)
on the left side of any 2 digit MNCs
used in domain names e.g. 15
becomes 015.
5.0 21 July Implementation of CR#23 (Major):
2010 Updates to domain names used on Nick Russell,
DAG #71
the GRX/IPX network and inter-SP Vodafone
links
5.1 13 August Implementation of the following CRs:
IREG
2010 CR #24 (Minor): Support of IP
Packet Nick Russell,
versions in DNS
(email Vodafone
CR #25 (Minor): ENUMservice field
approval)
value for SIP-I/PVI
6.0 1 Implementation of CR#26 (Major):
December Addition of new '.ipxuni' domain
2011 name and sub-domain name used for Gert Öster,
DAG#86
"well known" XCAP Root URI to Ericsson
"mnc<MNC>.mcc<MCC>.ipxuni.3gpp
network.org"
7.0 Implementation of the following CRs
- CR #28 (Major): Addition of new
subdomain for RCS/RCS-e as
“rcs.mnc>mnc>.mcc<mcc>.pub.3gpp
network.org”
CR #29 (Major): Removal of sub
domain name for the “XCAP root
IREG#62 Gert Öster,
URI” from the “ipxuni” domain name
DAG#92 Ericsson
and adding a new sub domain as
xcap.ims.mnc<mnc>.mcc<mcc>.pub.
3gppnetwork.org, and adding a new
subdomain for bootstrapping when
ISIM is used as
bsf.ims.mnc<mnc>.mcc<mcc>.
pub.3gppnetwork.org,

V15.0 Page 68 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

Approval Editor /
Version Date Brief Description of Change
Authority Company
8.0 23/11/2012 Implemetation of the Following CRs
 CR 29 (Major) To briefly
describe how GRX/IPX
providers can subscribe to the
RootDNS and access its
services
 CR 30(Major) Adding the
possibility to provide Non-
authoritative final ENUM
responses for ported-out users
based on Legacy Number
Portability Information
 CR 31(Major) Adding examples
of Number portability solutions
allowing the IPX/GRX ENUM to
work for countries without a
national Tier-1 ENUM DNS
server, as requested by IWG
IMQ and RCS-e.
 CR 32(Major) Removal of text IREG#63 Gert Öster,
not considering that Local DAG#99 Ericsson
Breakout for it specified method
for IMS roaming in relation to
VoLTE
 CR 33(Major) Adding a further
example of ENUM NAPTR
records with regular
expressions where part of the
result shall be substituted by the
“original” E.164 number.
 CR 34(Major) To show that a
Service provider does not need
to provide all data for domain
names the Service provider is
authoritative for one DNS but
that they may choose to imply
multiple levels of Authoritative
DNSs where a First level may
refer to the Second level
Authoritative DNS severs.

V15.0 Page 69 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

Approval Editor /
Version Date Brief Description of Change
Authority Company
9.0 21/10/2013 Implemtation of the following CRs
 CR1001 (Major) To add the
“ipxnetwork.org” TLD for IPX
providers that need a
subdomain to identify their
equipment and realms.
 CR1002 (Major) To add the
subdomain used for
interworking untrusted non-
3GPP access networks to the
EPC using the ePDG.
 CR1003 (Major) to clarify that
text on provisioning in clause Gert Öster,
5.4.3 only relates to ENUM and IREG#65
Ericsson
not HSS.
 CR1004 (Major) To describe the
routine for delegation of
"pub.3gppnetwork.org" sub-
domains
 CR1005 (Major) To provide
information on DNS resolution
when IR.21 information is used.
 CR 1006 (Major) To correct the
e-mail address for Root DNS
questions to reflect the new
“gsma.com” e-mail address
10.0 24/04/2014 Implemetation of the following CRs
 CR 1007 (Major) To add the
subdomain for the “OAM
System Realm” that can be
used for IP autoconfiguration
services e.g. in case Self-
Organizing Networks (SON) as Gert Öster,
IREG#66
defined by 3GPP Ericsson

 CR 1008 (Major) To provide

guidance on naming of IMS
Nodes, and to inform where
guidance on EPC node name
can be found

V15.0 Page 70 of 71
GSM Association Non-confidential
Official Document IR.67 - DNS and ENUM Guidelines for Service Providers and GRX and IPX
Providers

Approval Editor /
Version Date Brief Description of Change
Authority Company
11.0 16/04/2015 Implemetation of the following CRs
 CR 1009 (Major) To add
pointers to IR.88 for DNS
configuration requirements in
various 2G/3G and LTE
coexistence scenarios. Gert Öster,
NG#01
 CR 1010 (Major) To add the Ericsson
subdomain for “Bootstrapping of
MBMS service Announcements”
 CR 1011 (Major) To correct e-
mail address to Delegation of
“pub.3gppnetwork.org”
12.0 01/02/2016 IR.67 CR1012 Resolver architecture Frederic
for service aware IPX Paquette Tata
NG
Communicatio
ns
13.0 06/09/2016 CR1013 Sub-domain for ePDG
Frederic
selection with DNS-based Discovery
Paquette Tata
of Regulatory requirements NG
Communicatio
CR1014 SOA Refresh Timer
ns
alignment on root DNS
14.0 21/11/2016 IR.67 CR1015 DNS and ENUM Frederic
Guidelines for Service Providers and Paquette
NG
GRX and IPX Providers Tatacommuni
cations
15.0 27/07/2017 IR.67 CR1017 DNS Guidelines for Frederic
service providers – removal of ENUM Paquette
NG
content now in NG.105 Tatacommuni
cations

Other Information

Type Description
Document Owner NG Packet
Editor / Company Frederic Paquette Tata Communications

It is our intention to provide a quality product for your use. If you find any errors or omissions,
please contact us with your comments. You may notify us at [email protected]

Your comments or suggestions & questions are always welcome.

V15.0 Page 71 of 71