<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>There's nothing to 'fix' in pdns-auth. Its behavior is based on the functions it performs.<br></div><div><br></div><div>If there is no SELinux policy for it, or there is one but it's not correct, then SELinux will interfere. The proper solution is to determine whether any of the actions that pdns-auth is taking are invalid. If they are invalid, those are bugs (but this is unlikely); if they are valid, the SELinux policy needs to permit them.<br></div><div><br></div><div>On Sat, Jul 29, 2023, at 11:11, lejeczek via Pdns-users wrote:<br></div><blockquote type="cite" id="qt" style=""><div><span class="size" style="font-size:13px;"><span class="font" style="">Hi guys.<br> <br> Setting master=yes - on Centos 9s - results in SE denials and
'pdns' fails to start.<br> ...<br> About to create 3 backend threads for UDP<br> Exiting because communicator thread died with error: Resolver
binding to local UDP socket on '0.0.0.0': Permission denied<br> Started PowerDNS Authoritative Server.<br> ...<br> <br> Would you know if there ia boolean I'm missing or perhaps pdns'
end can be "fixed"?<br> It'd be good not to have build dedicated se module for that.<br> <br> many thanks, L.<br></span></span></div><div>_______________________________________________<br></div><div>Pdns-users mailing list<br></div><div><a href="mailto:Pdns-users@mailman.powerdns.com">Pdns-users@mailman.powerdns.com</a><br></div><div><a href="https://mailman.powerdns.com/mailman/listinfo/pdns-users">https://mailman.powerdns.com/mailman/listinfo/pdns-users</a><br></div><div><br></div></blockquote><div><br></div></body></html>