import-yuefeng/smartdns

smartDNS is a smart DNS server/forwarder/dispatcher written in Go.

En | 中文简体

smartDNS (based on overture)

---

smartDNS is a smart DNS server/forwarder/dispatcher written in Go.

smartDNS based on overture.

Please note: If you are using the binary releases, please follow the instructions in the README file with corresponding git version tag. The README in master branch are subject to change and does not always reflect the correct instructions to your binary release version.

Features

• Support DNSbunch(All DNS bundle)
• Support DNSbundle(A group of similar DNS server) example: HK-DNS, CN-DNS, US-DNS
• Support DNS cache update automatically(FastTable)
• Dispatcher
  • Custom domain
  • Custom IP network

Dispatch process

Overture can force custom domain DNS queries to use selected DNS when applicable.

For custom IP network, overture will query the domain with primary DNS firstly. If the answer is empty or the IP is not matched then overture will finally use the alternative DNS servers.

Structure

Installation

You can download binary releases from the release.

Usages

Start with the default config file -> ./config.json

$ ./smartDNS

Or use your own config file:

$ ./smartDNS -c /path/to/config.json

Verbose mode:

$ ./smartDNS -v

Log to file:

$ ./smartDNS -l /path/to/overture.log

For other options, please see help:

$ ./smartDNS -h

Tips:

• Root privilege is required if you are listening on port 53.

Configuration Syntax

Configuration file is "config.json" by default:

{
  "BindAddress": ":53",
  "DebugHTTPAddress": "127.0.0.1:5555",
  "DNSBunch": {
    "HK-DNS": [
      {
        "Name": "Microsoft-HK",
        "Address": "47.91.128.195:53",
        "Protocol": "udp",
        "SOCKS5Address": "",
        "Timeout": 6,
        "EDNSClientSubnet": {
          "Policy": "disable",
          "ExternalIP": "",
          "NoCookie": false
        }
      },
      {
        "Name": "Google-HK",
        "Address": "8.8.8.8:53",
        "Protocol": "udp",
        "SOCKS5Address": "",
        "Timeout": 3,
        "EDNSClientSubnet": {
          "Policy": "enable",
          "ExternalIP": "",
          "NoCookie": false
        }
      }
    ],
    "CN-DNS": [
      {
        "Name": "ChinaTelecom-CN",
        "Address": "114.114.114.114:53",
        "Protocol": "udp",
        "SOCKS5Address": "",
        "Timeout": 6,
        "EDNSClientSubnet": {
          "Policy": "disable",
          "ExternalIP": "",
          "NoCookie": false
        }
      },
      {
        "Name": "Baidu-CN",
        "Address": "180.76.76.76:53",
        "Protocol": "udp",
        "SOCKS5Address": "",
        "Timeout": 6,
        "EDNSClientSubnet": {
          "Policy": "disable",
          "ExternalIP": "",
          "NoCookie": false
        }
      }
    ]
  },
  "DNSFilter": {
    "HK-DNS": {
      "IPNetworkFile": "",
      "DomainFile": "configuration/hk.domain",
      "Matcher": "regex-list"
    },
    "CN-DNS": {
      "IPNetworkFile": "",
      "DomainFile": "configuration/cn.domain",
      "Matcher": "regex-list"
    }
  },
  "IPv6UseAlternativeDNS": false,
  "HostsFile": "./hosts",
  "MinimumTTL": 0,
  "DomainTTLFile": "./domain_ttl_sample",
  "CacheSize": 0,
  "RejectQType": [
    255
  ]
}```

Acknowledgements

• Fork:
  • overture: MIT
• Dependencies:
  • dns: BSD-3-Clause
  • logrus: MIT
• Code reference:
  • skydns: MIT
  • go-dnsmasq: MIT
• Contributors: https://github.com/import-yuefeng/smartDNS/graphs/contributors

License

This project is under the MIT license. See the LICENSE file for the full license text.

smartdns's Issues

Good project, I hope to maintain it, thank you.

Good project, I hope to maintain it, thank you.

Feature request: ability to set TTL for negative DNS replies (empty result or NXDOMAIN) in a separate way

Let's suppose I configured smartDNS for caching results for 7 days and a site I use to visit expires its domain registration.

/\ The negative response (NXDOMAIN) could be cached, if the site returns in 2 or 3 days, I will notice that the site is back only after 7 days as the cached negative answer would tell that.

An option to set a TTL for empty results or NXDOMAIN would be useful in this scenario.

这样设置会6个DNS都同时查询吗？

如果按下面这样设置，在DNS查询时，会对这6个DNS都进行并发查询吗？谢谢！

server-tcp 8.8.8.8
server-tcp 1.1.1.1

server-tls 8.8.8.8
server-tls 1.1.1.1

server-https https://1.1.1.1/dns-query
server-https https://8.8.8.8/resolve

smartDNS 无法感知 网络发生变化

smartDNS 无法感知 网络发生变化

当网络发生变化，例如从 WiFi 网络突然到无法访问网络的情况时，会因为无法请求远端DNS服务器，smartDNS 将不会停止请求远端，而将所有的DNS请求 均使用了默认 DNS，需新增处理网络变化的情况。

目标：当网络情况发生变化时，smartDNS 需要检测在新的网络情况下是否具有网络访问权限，如果没有，smartDNS 将进入轮询等待 查询网络情况，直到网络恢复，在此期间smartDNS 将不回应任何 DNS 请求。

智能学习是什么功能

rt

icmp 错误

一直提示这个 Error listening for ICMP packets: socket: permission denied
但我是root

smartDNS好像不支持119.29.29.29？显示请求失败，而overture可以

Dnspod-CN Fail: read udp 10.135.160.188:60723->119.29.29.29:53: i/o timeout

Feature request: Redis cache support

Overture already implemented: shawn1m/overture@5f9e7b1

But I think Overture is no more maintained.

If you accept my suggestion, a tip:

In go-redis packages there is an example file: https://github.com/go-redis/redis/blob/180f107add989d56d34734f1d429a83c6d4b9b91/example_test.go

The option for inserting the password and URL of Redis is: redis.ParseURL("redis://:qwerty@localhost:6379/1?dial_timeout=5s")

/\ Overture doesn't have an option for specifying a Redis password, you could implement this feature too.

smartDNS 数据持久化

目前 smartDNS 的 fastTable 所维护的 DNS Cache 无法持久化。

目标： 在下一个版本将会实现优雅处理 Ctrl+C 的退出信号，并且持久化 DNS Cache，在之后重载后正常运行。

这种 README 里的 gopher 的图片是怎么做的啊