You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an user executes a query searching nameservers by name, if the query parameter is a ldhname, the rdap server doesn't bring any results. For example the following rdap query:
doesn't return any results (despite the fact that there is a valid ns with that name in BD) and it logs the following db query:
SELECT DISTINCT(nse.nse_id), nse.nse_handle,nse.nse_ldh_name, nse.nse_port43, nse.nse_unicode_name FROM rdap.nameserver nse WHERE nse.nse_ldh_name='ns1.fooア21.org' OR nse.nse_unicode_name='ns1.fooア21.org' ORDER BY 1 LIMIT 6;
The text was updated successfully, but these errors were encountered:
Verified. All the inputs used in nameservers and domains searchs are validated and parsed to unicode strings, in order to match the unique domain/nameserver name column in db (domain.dom_unicode_name, nameserver.nse_unicode_name)
When an user executes a query searching nameservers by name, if the query parameter is a ldhname, the rdap server doesn't bring any results. For example the following rdap query:
http://localhost:8080/rdap-server/nameservers?name=ns1.xn--foo21-pm4d.org
doesn't return any results (despite the fact that there is a valid ns with that name in BD) and it logs the following db query:
SELECT DISTINCT(nse.nse_id), nse.nse_handle,nse.nse_ldh_name, nse.nse_port43, nse.nse_unicode_name FROM rdap.nameserver nse WHERE nse.nse_ldh_name='ns1.fooア21.org' OR nse.nse_unicode_name='ns1.fooア21.org' ORDER BY 1 LIMIT 6;
The text was updated successfully, but these errors were encountered: