CPUHP takes port 53, now DNS will not run, cannot find way to disable or remove it
Posted: Tue Apr 30, 2024 6:49 pm
Brandnew MX install, swapping out older AV-linux as Enlightenment doesn't work for me.
I got it all set up and install my DNS server, DNSmasq, it would not bind to port 53 because CPUHP is now using it.
I cannot find a way to get rid of it. I have not and can conceive of no circumstances where I need to disable and enable CPU's.
I think most normal people (non-geeky) will echo this opinion.
I hear it's a new kernel parameter. Is it possible to get at least one kernel without it?
Since my houses have no DNS I am having to add host files to everybody's laptops and my wife's work Windows machine.
Isn't it a rule that new stuff is not supposed to break anything? Should this even be on port 53? Or did I miss the DNS server changing ports?
This should be a big deal if I didn't, looks like it will break every Linux DNS server that uses a kernel with it. Please tell me I'm wrong, that's a disaster.
Paul Kelly
Major MX tools fan
I got it all set up and install my DNS server, DNSmasq, it would not bind to port 53 because CPUHP is now using it.
I cannot find a way to get rid of it. I have not and can conceive of no circumstances where I need to disable and enable CPU's.
I think most normal people (non-geeky) will echo this opinion.
I hear it's a new kernel parameter. Is it possible to get at least one kernel without it?
Since my houses have no DNS I am having to add host files to everybody's laptops and my wife's work Windows machine.
Isn't it a rule that new stuff is not supposed to break anything? Should this even be on port 53? Or did I miss the DNS server changing ports?
This should be a big deal if I didn't, looks like it will break every Linux DNS server that uses a kernel with it. Please tell me I'm wrong, that's a disaster.
Paul Kelly
Major MX tools fan