FAQ: ENUM Glue
- How do I generate glue records for a DOMAIN object?
Here is an example:
descr: Example domain for the reserved prefix +888
nserver: ns184.108.40.206.e164.arpa 192.0.2.1
nserver: ns220.127.116.11.e164.arpa 192.0.2.129
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.
- 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.
- 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 email to ripe-dbm _at_ ripe _dot_ net.
- How long until an update appears in the DNS?
If you see a message saying that your update was successful, it will be visible in the DNS after around an hour.
- Which TTL value is used?
We will use the default value for the e164.arpa zone. If you need a specific TTL (Time to Live) value, send an email to enum-request _at_ ripe _dot_ net.