This project is mirrored from https://github.com/coredns/coredns.git. The repository failed to update .
Repository mirroring has been paused due to too many failed attempts, and can be resumed by a project maintainer.
Last successful update .
  1. 14 Mar, 2019 4 commits
  2. 13 Mar, 2019 6 commits
  3. 12 Mar, 2019 5 commits
  4. 10 Mar, 2019 1 commit
  5. 08 Mar, 2019 6 commits
    • Miek Gieben's avatar
      plugin/health: remove ability to poll other plugins (#2547) · c778b3a6
      Miek Gieben authored
      * plugin/health: remove ability to poll other plugins
      
      This mechanism defeats the purpose any plugin (mostly) caching can still
      be alive, we can probably forward queries still. Don't poll plugins,
      just tell the world we're up and running.
      
      It was only actually used in kubernetes; and there specifically would
      mean any network hiccup would NACK the entire server health.
      
      Fixes: #2534
      Signed-off-by: default avatarMiek Gieben <miek@miek.nl>
      
      * update docs based on feedback
      Signed-off-by: default avatarMiek Gieben <miek@miek.nl>
      c778b3a6
    • Miek Gieben's avatar
      Add *ready* plugin (#2616) · db0b16b6
      Miek Gieben authored
      Add a ready plugin that allows plugin to signal when they are ready.
      Once a plugin is ready it is not queried again.
      
      This uses same mechanism as the health plugin: each plugin needs to
      implement an interface.
      
      Implement readines for the *erratic* plugin to aid in testing.
      
      Add README.md and tests moduled after the health plugin; which will be
      relegated to just providing process health. In similar vein to health
      this is a process wide setting.
      
      With this Corefile:
      ~~~
      . {
          erratic
          whoami
          ready
      }
      
      bla {
          erratic
          whoami
      }
      ~~~
      
      ready will lead to:
      
      ~~~ sh
      % curl localhost:8181/ready
      % dig @localhost -p 1053 mx example.org
      % curl localhost:8181/ready
      OK%
      ~~~
      
      Meanwhile CoreDNS logs:
      
      ~~~
      .:1053
      bla.:1053
      2019-02-26T20:59:07.137Z [INFO] CoreDNS-1.3.1
      2019-02-26T20:59:07.137Z [INFO] linux/amd64, go1.11.4,
      CoreDNS-1.3.1
      linux/amd64, go1.11.4,
      2019-02-26T20:59:11.415Z [INFO] plugin/ready: Still waiting on: "erratic"
      2019-02-26T20:59:13.510Z [INFO] plugin/ready: Still waiting on: "erratic"
      ~~~
      
      *ready* can be used in multiple server blocks and will do the right
      thing; query all those plugins from all server blocks for readiness.
      This does a similar thing to the prometheus plugin.
      Signed-off-by: default avatarMiek Gieben <miek@miek.nl>
      db0b16b6
    • Miek Gieben's avatar
      Remove internal loop detection (#2647) · 2b7e84a0
      Miek Gieben authored
      * Remove internal loop detection
      
      I can't actually think of a situation where we can create an internal
      loop. Sure externally triggered cycles can happen, but this is where the
      *loop* plugin comes in that detects those.
      
      Fixes #2602
      Signed-off-by: default avatarMiek Gieben <miek@miek.nl>
      
      * Remove test
      Signed-off-by: default avatarMiek Gieben <miek@miek.nl>
      2b7e84a0
    • Ruslan Drozhdzh's avatar
      18d305f4
    • Xiao An's avatar
      Add deprecation notice for NO_RELOAD (#2643) · 89a4b9bd
      Xiao An authored
      Signed-off-by: default avatarXiao An <hac@zju.edu.cn>
      89a4b9bd
    • Francois Tur's avatar
      - remove caddy event, It is now triggered directly by Caddy in the Start... · 97e2a53a
      Francois Tur authored
      - remove caddy event, It is now triggered directly by Caddy in the Start function of the Instance (#2656)
      
      97e2a53a
  6. 04 Mar, 2019 5 commits
  7. 03 Mar, 2019 4 commits
  8. 02 Mar, 2019 1 commit
  9. 01 Mar, 2019 2 commits
  10. 28 Feb, 2019 1 commit
  11. 27 Feb, 2019 5 commits