Feedback dns issue, and request to update dns

Hello, I found that when Geekdns is selected as the upstream, it will not be resolved, but the direct access to the Doh address can be resolved.

Then we updated the DNS address and service:
WebSite:www.233py.com
We stopped recording filtered data very early.
We do not log, do not filter data, and support DNSSEC.
We provide a total of 6 servers, four in mainland China, and others in Hong Kong, China, and the United States.

Southern China [Guangdong]
IP: 119.29.107.85
DOH: https://sdns.233py.com/dns-query
Dnscrypt: sdns://AQMAAAAAAAAAEDExOS4yOS4xMDcuODU6MjIgCsUpkBu6ujbEDZ8PQI2wa3DCkDzxLlczLOwTyQTQM70ZMi5kbnNjcnlwd
DOT: sdns.233py.com

Eastern China [Shanghai]
IP: 47.101.136.37
DOH: https://edns.233py.com/dns-query
Dnscrypt:
sdns://AQMAAAAAAAAAEDQ3LjEwMS4xMzYuMzc6MjIgCRIqxqrF-npxg2-xjGLKvzuxvS7hCGgXx_x_4K85yHYZMi5kbnNjcnlwd
DOT: edns.233py.com

Northern China [Beijing]
IP: 114.115.240.175
DOH: https://ndns.233py.com/dns-query
Dnscrypt:
sdns://AQMAAAAAAAAAEjExNC4xMTUuMjQwLjE3NToyMiCLntDYEK0AwismFtMCM0YMkflJGNZiJnINFtDLcCLLwBkyLmRuc2Nye
DOT:ndns.233py.com

Western China [Chongqing]
IP: 118.24.208.197
DOH: https://wdns.233py.com/dns-query
Dnscrypt:
sdns://AQMAAAAAAAAAETExOC4yNC4yMDguMTk3OjIyIL66dzE0aNGlvYsF3RnukLk4AI3lQqSxeEo6PxHme-qZGTIuZG5zY3J5c
DOT: wdns.233py.com

China Hong Kong
IP: 150.109.74.164
DOH: https://hk-dns.233py.com/dns-query
Dnscrypt:
sdns://AQcAAAAAAAAAETE1MC4xMDkuNzQuMTY0OjIyIPcEBXJOU2jQys6br08P8yyn132SuDixQ8Oek3lhoRQoGTIuZG5zY3J5c
DOT: hk-dns.233py.com

United States
IP: 107.155.79.120
IPV6: 2604:880:398:0555:0000:0000:0000:0001
DOH: https://us-dns.233py.com/dns-query
Dnscrypt:
sdns://AQMAAAAAAAAAETEwNy4xNTUuNzkuMTIwOjIyIDzxhAPcjkUtLFGDWuU9rLKuuRzz2iKEoeO7TqqSpXkqGTIuZG5zY3J5c
DOT: us-dns.233py.com

Thank you

Non sono indicati file o test. Inizia dal punto di ingresso della configurazione e della selezione dell’upstream/provider, riproduci il fallimento della risoluzione di Geekdns e confrontalo con gli endpoint 233py.com forniti. Il lavoro è completato quando l’upstream selezionato viene risolto correttamente e i dettagli richiesti del provider sono rappresentati accuratamente.

Scritto dal modello di indicizzazione a partire dal testo della issue.