Skip to content

Conversation

@georgejhunt
Copy link
Contributor

@jvonau -- This seems like an obvious and required fix, but check me. Seems that installing a package starts it up. Would you rather install named, and then disable it?

@holta holta added this to the 6.7 milestone Nov 19, 2018
@holta
Copy link
Member

holta commented Nov 19, 2018

@jvonau can you review @georgejhunt 's suggestion here?

@holta
Copy link
Member

holta commented Nov 25, 2018

@georgejhunt have you tested this as solving the problem?

@mrdavidhaag seems to indicate the port 53 collision runs even deeper as he's described within #1306 ?

@georgejhunt
Copy link
Contributor Author

georgejhunt commented Nov 25, 2018 via email

@holta
Copy link
Member

holta commented Nov 30, 2018

@georgejhunt is this PR still necessary for #1306 etc?

Or has it been supplanted by other approaches e.g. @jvonau's PR #1311 or similar?

@holta
Copy link
Member

holta commented Dec 3, 2018

This is superseded by #1318 (choosing a smaller hammer, that allows folks to install both named/BIND9 and dnsmasq, and choose which to turn on later...)

@holta holta closed this Dec 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants