9seconds/mtg v2.1.13 on GitHub

This release addresses long-running confusion related to DNS-over-HTTP mandatory option. Now it is fixed. Unfortunately, old network.doh-ip option is deprecated now, please use new network.dns.

This is doh-ip you should move from

# DEPRECATED option:
#  If dns option is specified, it will be used instead. No default is defined
#  anymore. But if you set this option, this is literally the same providing
#  https:// URL to `dns`.
#
#  In other words:
#
#    doh-ip = "1.1.1.1"
#
# is literally the same as
#
#    dns = "https://1.1.1.1"
# doh-ip = "1.1.1.1"

# Starting from mtg v2.1.12 we have changed a configuration for DNS. Now it
# supports DNS-over-HTTPS, DNS-over-TLS, custom UDP resolver and system
# resolver.
#
# Here is how to define DNS-over-HTTPS:
#  - https://1.1.1.1
#  - https://1.1.1.1/dns-query
#  - https://cloudflare-dns.com/dns-query
#  - https://cloudflare-dns.com
#
# Here is how to define DNS-over-TLS:
#  - tls://1.1.1.1
#  - tls://cloudflare-dns.com
#
# Here is how to define a custom UDP resolver (we support only IPs here)
#  - 1.1.1.1
#  - udp://1.1.1.1
#
# If you set it to empty string, default resolver will be used.
# But please comment out doh-ip
dns = "https://1.1.1.1"

So, in general you can use 4 different options for DNS setting:

1. Default resolver.

In that case just set dns to empty string:

[network]
dns = ""

so mtg will use local stub resolver for getting DNS records.

2. DNS-over-HTTPS

Just have https:// prefix:

[network]
dns = "https://1.1.1.1"

This will mean that mtg will use https://1.1.1.1/dns-query URL to resolve DNS. If path is different, just specify a full URL:

[network]
dns = "https://1.1.1.1/my-path"

3. DNS-over-TLS

Just use tls:// prefix:

[network]
dns = "tls://dns.google"

4. Classic UDP DNS

Either provide IP address or optionally prefix it with udp://

[network]
dns = "8.8.8.8"

and

[network]
dns = "udp://8.8.8.8"

are both equivalent way of setting that.

Please be aware that if you have to setup DNS, it means that there are some restrictions implied. It could be a good idea to have socks5 upstream connectivity in that case.

What's Changed

Simplify network implementation by @9seconds in #346

Full Changelog: v2.1.12...v2.1.13