Skip to content
This repository has been archived by the owner. It is now read-only.

SkyDNS can't listen on 0.0.0.0:53 in CoreOS 1151.0.0 #1545

Closed
steveeJ opened this issue Aug 29, 2016 · 3 comments
Closed

SkyDNS can't listen on 0.0.0.0:53 in CoreOS 1151.0.0 #1545

steveeJ opened this issue Aug 29, 2016 · 3 comments

Comments

@steveeJ
Copy link

@steveeJ steveeJ commented Aug 29, 2016

CoreOS Version

1151.0.0

$ cat /etc/os-release
NAME=CoreOS
...
BUG_REPORT_URL="https://github.com/coreos/bugs/issues"

Environment

I have a SkyDNS container that uses --net=host and attempts to listen on 0.0.0.0:53.

Expected Behavior

SkyDNS works.

Actual Behavior

SkyDNS doesn't work, because systemd-resolved is listening on 127.0.0.53:53, causing SkyDNS to fail.

Reproduction Steps

  1. Boot CoreOS 1151.0.0
  2. etcdctl set /skydns/config {"dns_addr":"0.0.0.0:53"}
  3. sudo /usr/bin/rkt run --debug --net=host docker://skynetservices/skydns --insecure-options=image

Other Information

This has worked in the past without any configuration change.

Feature Request

Disable systemd-resolved by default, or revert whatever caused it to claim that socket.

@steveeJ steveeJ changed the title SkyDNS can't listen on 0.0.0.0:53 since CoreOS 1151.0.0 SkyDNS can't listen on 0.0.0.0:53 in CoreOS 1151.0.0 Aug 29, 2016
@crawford crawford added this to the CoreOS Alpha 1165.0.0 milestone Aug 30, 2016
@dm0- dm0- self-assigned this Aug 30, 2016
@dm0-
Copy link

@dm0- dm0- commented Aug 30, 2016

We discussed this, and I will send a PR upstream shortly to make enabling the stub resolver configurable. I'll leave it enabled by default for upstream consistency, but we will disable it on CoreOS.

@philips
Copy link

@philips philips commented Aug 30, 2016

And as a workaround doing systemctl mask systemd-resolved works if you are running your own full resolver. However, if you rely on /etc/resolv.conf entries from DHCP it will break.

Also, this issue will be fixed before Beta and we will default this behavior to off.

@dm0-
Copy link

@dm0- dm0- commented Sep 6, 2016

We are unconditionally disabling the DNS stub resolver's listening ports on the next alpha and beta, until upstream agrees on a configurable option.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

4 participants