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?
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.
[1]: Example: https://rdap.db.ripe.net/domain/6.4.e164.arpa
-Cynthia
