CoreDNS plugin for replacing CNAME records on zone apex
Home Page: https://coredns.io/explugins/alias/
License: Apache License 2.0
I am a software engineer, currently learning about building systems that scale, and I like to have fun building and taking apart hardware and software.
Talk to me about Kubernetes and Linux! I'm @serverwentdown on most social platforms.
Why @serverwentdown? Because a good cluster can tolerate node failures.
if we set CNAME to zone apex.
coredns returns only CNAME record with MX query.
example.com. 300 IN MX mx.example.org.
example.com. 300 IN CNAME some.magic.example.org.
some.magic.example.org. 300 IN A 123.123.45.67
$ dig example.org mx
;; ANSWER SECTION:
example.org. 300 IN CNAME some.magic.example.org.
Your plugin just remove the CNAME, so we get empty response. :-(
We've renamed middleware to plugin to have more consitant naming and keep in sync with caddy.
For the example plugin, this diff we needed; it is just renaming middleware to plugin:
see coredns/example@fe5e8f0
When I add this plugin and try to compile coredns I get the following error:
#8 92.73 go: github.com/coredns/coredns imports
#8 92.73 github.com/coredns/coredns/core/plugin imports
#8 92.73 github.com/jiachengxu/idetcd imports
#8 92.73 github.com/mholt/caddy/onevent: github.com/mholt/[email protected]: parsing go.mod:
#8 92.73 module declares its path as: github.com/caddyserver/caddy
#8 92.73 but was required as: github.com/mholt/caddy
The 1.8.0 coredns logs mention this in their release notes:
Caddy is now developing a version 2 and we are using version 1, we've internalized
Caddy into <https://github.com/coredns/caddy>. This means the `caddy` types change and *all* plugins
need to fix the import path from: `github.com/caddyserver/caddy` to `github.com/coredns/caddy` (this
can thankfully be automated).
Let's say I have the following dns file:
example.org. 3600 IN CNAME twitter.org.
And I have alias and forward plugins enabled:
. {
log
forward . 1.1.1.1 1.0.0.1
}
example.org {
file db.example.org
alias
}
When I dig example.org, I see that DNS response contains both CNAME and A records (resolved from twitter.com). Is it possible to remove CNAME records and just respond resolved A records?
I'm new to CoreDNS stuff, so sorry if I misunderstood something.
I have the following config:
// Corefile
spiral.sh {
file zones/spiral.sh
alias
}
; zone
http-pool.spiral.sh. 3000 IN A 128.116.205.8
http-pool.spiral.sh. 3000 IN A 45.61.184.138
spiral.sh. 3000 IN CNAME http-pool.spiral.sh.
dig output:
;; ANSWER SECTION:
spiral.sh. 3000 IN CNAME http-pool.spiral.sh.
http-pool.spiral.sh. 3000 IN A 128.116.205.8
http-pool.spiral.sh. 3000 IN A 45.61.184.138
What am I doing wrong? I would like to show just the A records and not the CNAME, as shown in the example on the README.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.