SVCB, Surge License Check and [Host]

owenlynda

Before upgrading to the latest version of Surge iOS, www.surge-activation.com follows the parameter "allow-dns-svcb" = false/true. As such, the domain: www.surge-activation.com obeys the Local DNS mapping in [Host] only when allow-dns-svcb = false with the following configuration:
[General]
always-real-ip = -www.surge-activation.com, *

[Rule]
DOMAIN-SUFFIX,surge-activation.com,DIRECT,extended-matching

[Host]
www.surge-activation.com = server:192.168.1.1

This configuration is necessary so that Surge License Upgrade/authorization/validation always works even when all policies or proxies fails or when encrypted DNS fails due to invalid outbound-mode policy

When the parameter "allow-dns-svcb" is set to "true", iOS is allowed to use svcb resolution but the target request does not follow local DNS mapping in [Host]. If "allow-dns-svcb" is set to "false", all the local DNS mapping becomes active, working and are matched.

@SurgeTeam please support matching of local DNS mapping in [Host] when allow-dns-svcb = true or let the activation domain: www.surge-activation.com go back to what it was. It is very important

SurgeTeam

www.surge-activation.com cannot be configured as [Host] item now, as it may cause unexpected errors.

owenlynda

SurgeTeam It was working fine in the previous version and I hope the error can be fixed in the next version.

Is it possible to support SVCB queries to follow Local DNS Mapping in [Host] just like A and AAAA?

Also, Please support in-line RULE-SET for [Host] matching efficiency just like external RULE-SET is supported in the new version. This is a very good way of reducing the items in [Host] thereby reducing system resources consumption by Surge