The alias plugin eliminates CNAME records from zone apex by making the subsequent resolved records look like they belong to the zone apex. This behaves similarily to CloudFlare's Zone Flattening.
This plugin works only with plugins that produce A or AAAA records alongside the CNAME record. Examples include auto and file. However, you might need to adjust the order of this plugin to use it with other plugins.
Preferrably, this should not be used in favour of the RFC drafts for the new ANAME records, but the DNS library used by CoreDNS does not support ANAME records yet.
Release builds can be found here
alias
example.com {
file db.example.com
alias
}
# This is used to resolve CNAME records by the `file` plugin. Modify accordingly
. {
forward . 1.1.1.1 1.0.0.1
}
This will transform responses like this:
;; ANSWER SECTION:
example.com. 3600 IN CNAME two.example.org.
two.example.org. 3600 IN CNAME one.example.net.
one.example.net. 3600 IN A 127.0.0.1
into
;; ANSWER SECTION:
example.com. 3600 IN A 127.0.0.1
See example/ for a more extensive example.
As per CoreDNS docs, there are two ways.
$ git clone https://github.com/coredns/coredns
$ cd coredns
$ vim plugin.cfg
# Add the line alias:github.com/serverwentdown/alias before the file middleware
$ go generate
$ go build
$ ./coredns -plugins | grep alias
$ git clone https://github.com/serverwentdown/alias
$ cd alias/coredns
$ go build
$ ./coredns -plugins | grep alias
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent