#1036299 unbound: can't bind to 127.0.0.1:53

Package:
unbound
Source:
unbound
Description:
validating, recursive, caching DNS resolver
Submitter:
andrej
Date:
2026-08-09 07:43:01 UTC
Severity:
normal
Tags:
#1036299#5
Date:
2023-05-18 22:05:08 UTC
From:
To:
Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
     With our unbound configuration file unbound couldn't start

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
     Place the unbound apparmor profile into complain mode rather than enforcing

   * What was the outcome of this action?
     Managed to launch both unbond and bgpd

   * What outcome did you expect instead?
     I would have expected unound to be allowed to bind to a port out of the box

*** End of the template - remove these template lines ***
#1036299#10
Date:
2023-08-30 09:38:04 UTC
From:
To:
Control: tag -1 + moreinfo unreproducible

What's the apparmor error message(s) when it blocks unbound from using the given
address?  It works here just fine.

/mjt
#1036299#19
Date:
2026-08-09 07:40:41 UTC
From:
To:
[...]

Almost 3 years and no answer.  Assuming the bug is fixed now.
Feel free to reopen the issue and provide more information if you think
this is incorrect.

Thanks,

/mjt