Hi Cynthia,

On 31 Jul 2025, at 19:37, Cynthia Revström <me@cynthia.re> wrote:

Hi Ed and DB-WG,

I just noticed that the RIPE DB RDAP interface returns a 500 error when querying for ENUM domains[1] (except for specifically the top level e164.arpa domain, which results in a 400 error).

This seems to be due to an assumption that all domains in the RIPE DB are reverse DNS domains for IP addresses, which is not the case as ENUM domains are also in there.

Is this an intentional decision or was this just an oversight?

The RDAP Query Format RFC 9082 (was RFC 7482) does not include the e164.arpa zone : "Queries for domain information are of the form /domain/XXXX, where XXXX is a fully qualified (relative to the root) domain name (as specified in [RFC0952] and [RFC1123]) in either the in-addr.arpa or ip6.arpa zones (for RIRs) or a fully qualified domain name in a zone administered by the server operator (for DNRs)."

If it was just an oversight, consider this a bug report. :) If it was an intentional decision then I would be interested in hearing what the reasoning was.

I can't tell if this was intentional, I couldn't find any discussion of ENUM or e164.arpa in the WG archives: https://mailarchive.ietf.org/arch/browse/weirds/ https://mailarchive.ietf.org/arch/browse/regext/ If there is interest in supporting the e164.arpa zone in RDAP domain queries, I suggest the next step is to create a draft RFC, so we make it part of the standard and consider the impact on the protocol (e.g. how do we bootstrap the e1664.arpa zone, should other RIRs redirect e164.arpa to the RIPE NCC etc.).

[1]: Example: https://rdap.db.ripe.net/domain/6.4.e164.arpa

-Cynthia

Regards Ed Shryane RIPE NCC