ENUM Glue - Frequently Asked Questions

1. How do I generate glue records for a domain object?
2. What are the restrictions on using glue for reverse domains?
3. How will I know what to fix if the domain object update failed?
4. My update succeeded. How long will it take before it's visible in the DNS?
5. Which ‘Time to Live’ (TTL) value will be used?

1. How do I generate glue records for a domain object?

Here is an example:

domain: 8.8.8.e164.arpa
descr: Example domain for the reserved prefix +888
[...]
nserver: ns1.8.8.8.e164.arpa 192.0.2.1
nserver: ns2.8.8.8.e164.arpa 192.0.2.129
nserver: ns1.example.net
nserver: ns2.example.net
[...]

In this example, the first two "nserver:" attributes contain one glue IP address. The last two "nserver:" attributes do not need glue, as they are in a different domain – example.net.

2. What are the restrictions on using glue for reverse domains?

In addition to the usual restrictions for reverse delegations, the following restrictions apply:

• The domain delegated needs to be a sub-domain of e164.arpa.
• The name server needs to be within the domain delegated.
• The IP address needs to be a public IPv4 address.
• You can only specify one IPv4 glue address for each name server.

We are working towards providing support for IPv6 and multiple addresses for each name server.

3. How will I know what to fix if the domain object update failed?

The responses from our server will include diagnostic messages. You can get further help by sending an e-mail to ripe-dbm@ripe.net.

4. My update succeeded. How long will it take before it's visible in the DNS?

It will take up to 1 hour.

5. Which ‘Time to Live’ (TTL) value will be used?

We will use the default value for the e164.arpa zone. If you need a specific TTL value, send an e-mail to enum-request@ripe.net.