Wildcard DNS using Template Plugin #6349

patrickap · 2023-10-05T18:07:32Z

patrickap
Oct 5, 2023

I am experiencing a problem with the latest version of CoreDNS. I'm using the template plugin to create a wildcard DNS entry. It was working perfectly in version 1.10.1, but fails in version 1.11.1. I'm wondering if there's something I need to adjust. Additionally, the browser indicates an 'invalid request' error. Thank you in advance.

docker-compose.yml

version: "3.7"

services:
  coredns:
    container_name: coredns
    image: coredns/coredns:1.11.1
    environment:
      - HOST_IP=${HOST_IP?}
      - HOST_NAME=${HOST_NAME?}
    init: true
    restart: always
    ports:
      - 53:53
      - 53:53/udp
    volumes:
      - ./Corefile:/Corefile:ro

Corefile

. {
  forward . 8.8.8.8

  template IN A {$HOST_NAME} {
    match ^(.*)$
    answer "{{ .Name }} 300 IN A {$HOST_IP}"
    fallthrough
  }

  log
  health
  errors
}

patrickap · 2023-10-05T21:01:42Z

patrickap
Oct 5, 2023
Author

I may have found a solution. CoreDNS seems to require the configuration path to be specified. I added the following to the docker-compose.yml:

command: ["-conf", "/etc/coredns/Corefile"]

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Wildcard DNS using Template Plugin #6349

Uh oh!

{{title}}

Uh oh!

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Select a reply

Uh oh!

Wildcard DNS using Template Plugin #6349

Uh oh!

patrickap Oct 5, 2023

Replies: 1 comment

Uh oh!

Uh oh!

patrickap Oct 5, 2023 Author

patrickap
Oct 5, 2023

patrickap
Oct 5, 2023
Author