How to to filter for fakedns in RuleObject?

[ccaapton]

For example, when I have a mini config file like below, the "geosite:github" will be search twice for a fakedns request, one for fakedns resolve, another for routing decision.

{
    "dns": {
        "servers": [
            {
                "address": "fakedns",
                "domains": [
                    "geosite:github"
                ]
            },
            "223.5.5.5"
        ]
    },
    "fakedns": [
        {
            "ipPool": "198.18.0.0/15",
            "poolSize": 10000
        }
    ],
    "routing": {
        "domainStrategy": "IPIfNonMatch",
        "rules": [
            {
                "domain": [
                  "geosite:github"
                ],
                "outboundTag": "proxy",
                "type": "field"
              }
        ]
    }
}

Is there any way to write a RuleObject like this to avoid the duplication?

        "rules": [
            {
                "attrs": {
                  "fakedns": "1"
                },
                "outboundTag": "proxy",
                "type": "field"
              }
        ]

[Diligence0743]

To avoid this duplication and filter based on whether a request was resolved using fakedns, you can use the inboundTag field in your routing rules along with a specific inbound configuration for fakedns.

{
    "dns": {
        "servers": [
            {
                "address": "fakedns",
                "domains": [
                    "geosite:github"
                ],
                "tag": "fake-dns-in"
            },
            "223.5.5.5"
        ]
    },
    "fakedns": [
        {
            "ipPool": "198.18.0.0/15",
            "poolSize": 10000
        }
    ],
    "routing": {
        "domainStrategy": "IPIfNonMatch",
        "rules": [
            {
                "inboundTag": ["fake-dns-in"],
                "outboundTag": "proxy",
                "type": "field"
            }
        ]
    }
}

1. tag in DNS Server: added a tag field to your fakedns server configuration. This tag will be associated with any inbound requests that are handled by this DNS server.

2. inboundTag in Routing Rule: changed the matching condition in your routing rule to use inboundTag instead of attrs. This field specifically checks the tag of the inbound handler that processed the request.

[ccaapton]

@Diligence0743 From the protobuf config, it looks like "tag" is not at per-server level, but a global attribute for the whole dns config.

Could you give some reference documentation about this per-server level configuration?

[Diligence0743]

viable solution with current limitations:

{
  "routing": {
    "rules": [
      {
        "ip": ["198.18.0.0/15"],
        "outboundTag": "proxy",
        "type": "field"
      }
    ]
  }
}