Mirrors/coredns
1
0
Fork 0
mirror of https://github.com/coredns/coredns.git synced 2025-10-27 16:24:19 -04:00
Code Issues Packages Projects Releases Wiki Activity

dump travis to 1.8 (#606)

Browse Source
This commit is contained in:
Miek Gieben
2017-03-19 09:12:18 +00:00
committed by GitHub
parent 72f5a92d30
commit 757f49d8ff
2 changed files with 6 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.travis.yml
View File

@@ -7,7 +7,7 @@ services:
language: go language: go
go: go:
- 1.7 - 1.8
go_import_path: github.com/coredns/coredns go_import_path: github.com/coredns/coredns

11
README.md
View File

@@ -7,8 +7,9 @@
CoreDNS is a DNS server that started as a fork of [Caddy](https://github.com/mholt/caddy/). It has CoreDNS is a DNS server that started as a fork of [Caddy](https://github.com/mholt/caddy/). It has
the same model: it chains middleware. In fact it's so similar that CoreDNS is now a server type the same model: it chains middleware. In fact it's so similar that CoreDNS is now a server type
plugin for Caddy. CoreDNS is also a [Cloud Native Computing Foundation](https://cncf.io) inception plugin for Caddy.
level project.
CoreDNS is also a [Cloud Native Computing Foundation](https://cncf.io) inception level project.
CoreDNS is the successor to [SkyDNS](https://github.com/skynetservices/skydns). SkyDNS is a thin CoreDNS is the successor to [SkyDNS](https://github.com/skynetservices/skydns). SkyDNS is a thin
layer that exposes services in etcd in the DNS. CoreDNS builds on this idea and is a generic DNS layer that exposes services in etcd in the DNS. CoreDNS builds on this idea and is a generic DNS
@@ -17,10 +18,8 @@ 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 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 some middleware! are able to do what you want with your DNS data. And if not: write some middleware!
CoreDNS can listen for DNS request coming in over UDP/TCP (go'old DNS), TLS CoreDNS can listen for DNS request coming in over UDP/TCP (go'old DNS), TLS ([RFC
([RFC 7858](https://tools.ietf.org/html/rfc7858)) and gRPC (not 7858](https://tools.ietf.org/html/rfc7858)) and gRPC (not a standard.
a standard.
Currently CoreDNS is able to: Currently CoreDNS is able to: