功能请求：
1、DNS cache is not used to resolve trackers（解析tracker不使用DNS缓存）
2、UDP proxy tracker（UDP代理tracker）
3、A switch that takes effect immediately after moving the tracker（移动tracker后立即生效的开关）


Regarding the demand reasons for the problem ①, after the tracker updates the IP, it will not take effect immediately. The local DNS cache needs to be cleared, and sometimes it can even be done after restarting the client.
Example: nslookup domain.com 8.8.8.8
In China...many DNS resolvers will also cache domain name resolution IP, which does not take effect immediately like Google DNS (8.8.8.8), so a custom DNS resolution tracker domain name function is needed.
Tixati customizes a DNS used to resolve the tracker without using the system DNS and uses a custom DNS every time it resolves a domain name, because Windows 10 will still use the cache even if you modify the system DNS...even if you use Google DNS

Regarding the reason for the demand for problem ②, it is an advanced issue of the first problem. In mainland China, some trackers may be contaminated and resolution requires UDP proxy to resolve the tracker domain name in order to obtain the correct IP address.
I found a problem before, it seems that UDP proxy does not support IPV6 IP mode tracker?
Proxy resolution is a rather troublesome issue. Make sure that the proxy only parses but does not change the IP of the actual request. Otherwise, the reported IP will be wrong and uploading/downloading will not work properly.

Regarding the ③ issue (this may need a switch option) I found that moving the tracker does not work/take effect immediately.
Refer to this video: https://www.veed.io/view/61ed4aa4-16ba-4c7a-a637-1297fae3bae4?panel=share
------------------------------------------
关于①问题的需求原因 tracker更新IP后不会立即生效 需要清理本地DNS缓存,甚至有时候重启客户端后才可以
例子：nslookup domain.com 8.8.8.8
在中国……很多DNS解析商也会缓存域名解析的IP不像谷歌DNS(8.8.8.8)那样立即生效 所以需要一个自定义DNS解析tracker域名的功能
Tixati自定义一个解析tracker用的DNS不使用系统DNS 并且每次解析域名使用自定义DNS，因为windows10 即便你修改系统DNS还会使用缓存……哪怕你使用了谷歌DNS

关于②问题的需求原因 则是第一个问题的进阶问题 在中国大陆部分tracker可能被污染解析需要代理UDP来解析tracker域名 才能获取到正确的IP地址
之前我发现个问题似乎UDP代理不支持IPV6的IP模式的tracker？
代理解析是一个比较头疼的问题，要确保代理后只解析但不改变真实请求的IP 否则汇报的IP是错误的，上传/下载也无法正常工作。

关于③问题（这可能需要一个开关选项）我发现移动tracker后不会立即工作/生效。
参考这个视频：https://www.veed.io/view/61ed4aa4-16ba-4c7a-a637-1297fae3bae4?panel=share