DNS server that chains plugins
CoreDNS is the successor to SkyDNS. SkyDNS is a thin layer that exposes services in etcd in the DNS. CoreDNS builds on this idea and is a generic DNS server that can talk to multiple backends (etcd, kubernetes, etc.).
CoreDNS aims to be a fast and flexible DNS server. The keyword here is flexible: with CoreDNS you are able to do what you want with your DNS data. And if not: write a plugin!
CoreDNS can listen for DNS request coming in over UDP/TCP (go'old DNS), TLS (RFC 7858) and gRPC (not a standard).
Currently CoreDNS is able to:
Serve zone data from a file; both DNSSEC (NSEC only) and DNS are supported (file).
Retrieve zone data from primaries, i.e., act as a secondary server (AXFR only) (secondary).
Sign zone data on-the-fly (dnssec).
Load balancing of responses (loadbalance).
Allow for zone transfers, i.e., act as a primary server (file).
Automatically load zone files from disk (auto).
Health checking endpoint (health).
Use etcd as a backend, i.e., a 101.5% replacement for SkyDNS (etcd).
Use k8s (kubernetes) as a backend (kubernetes).
Serve as a proxy to forward queries to some other (recursive) nameserver (proxy).
Provide metrics (by using Prometheus) (metrics).
Provide query (log) and error (error) logging.
Support the CH class: version.bind and friends (chaos).
Profiling support (pprof).
Rewrite queries (qtype, qclass and qname) (rewrite).
Echo back the IP address, transport and port number used (whoami). This is also the default plugin that gets loaded when CoreDNS can't find a Corefile to load.
Edit Corefile according your need in /opt/CoreDNS (default configuration proxy dns 18.104.22.168:53)
TS-X31 TS-X41 TS-ARM-X19 TS-X28A