Latency test doesn't work with custom DNS object

[madjxatw]

I have the DNS object settings as below:

{
    "disable_cache": false,
    "disable_expire": false,
    "fakeip": {
    },
    "final": "dns-proxy",
    "independent_cache": false,
    "reverse_mapping": false,
    "rules": [
        {
            "action": "route",
            "rule_set": [
                   "geosite-cn",
                    "geosite-geolocation-cn"
            ],
            "server": "dns-direct"
        }
    ],
    "servers": [
        {
            "server": "223.5.5.5",
            "server_port": 853,
            "tag": "dns-direct",
            "type": "tls"
        },
        {
            "server": "1.1.1.1",
            "server_port": 853,
            "tag": "dns-proxy",
            "type": "tls"
        }
    ],
    "strategy": ""
}

The proxy works fine, but the Url test and speed test fail with the error message:

start service: initialize DNS rule[0]: rule-set not found: geosite-cn

Anybody knows how to fix this?

[0-Kutya-0]

Anybody knows how to fix this?

I don't know if this is a bug or not, but if you specify a rule_set in a custom DNS object, that same rule_set must be included in the routing rules. In your case, you need to have a routing profile like this, and everything will work.

[madjxatw]

I am using the Bypass China routing profile, adding these two rulesets to this profile gives me duplicate rule-set error.

[0-Kutya-0]

If you're using “Bypass_China,” then yes, you don't need to change the rules as I suggested earlier. Your problem is due to the version of Throne you're using—1.1.6 or earlier. I tested it on the latest beta, and it works as intended. Wait for the official release or update to the beta.

[madjxatw]

Thanks, I will be waiting for a new official release.

[0-Kutya-0]

The release was released yesterday, did you have time to test your problem on the new version?

[madjxatw]

Thank you for the reminder. I tried out the new release and noticed the UI has changed quite a bit. As you said before, the URL latency testing now works with custom DNS object.