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
Milestone
Comments
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. |
And as a workaround doing Also, this issue will be fixed before Beta and we will default this behavior to off. |
This was referenced Aug 30, 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.
CoreOS Version
1151.0.0
Environment
I have a SkyDNS container that uses
--net=host
and attempts to listen on0.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
etcdctl set /skydns/config {"dns_addr":"0.0.0.0:53"}
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.
The text was updated successfully, but these errors were encountered: