resolvconf uses wrong path for bind9 and resolvconf
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bind9 (Debian) |
Fix Released
|
Unknown
|
|||
bind9 (Ubuntu) |
Triaged
|
Medium
|
Serge Hallyn |
Bug Description
Binary package hint: apparmor
Hi,
The profile defined for named by aparmor is not correct (apparmor2.
in /etc/apparmor.
# support for resolvconf
/var/
but resolvconf generates this file as "/var/run/
Other ACLs also refer to the directory "/var/run/named/" wich does not even exist in ubuntu 10.10 (the correct path is /var/run/bind/"
this is the same problem for "/var/log/named/" direcorty, because of naming conventions in ubuntu : you'de rather log into "/var/log/bind/" instead
A possible solution :
substitute "/var/run/named/" to "/var/run/bind/" and "/var/log/named/" to "/var/log/bind/" in /etc/apparmor.
Another solution is tu use those "named" directories for logging/generating file with resolvconf
Cheers
affects: | apparmor (Ubuntu) → bind9 (Ubuntu) |
tags: | added: apparmor |
Changed in bind9 (Debian): | |
status: | Unknown → Won't Fix |
Changed in bind9 (Debian): | |
status: | Won't Fix → Fix Released |
summary: |
- apparmor rights bug with bind9 and resovconf + resolvconf uses wrong path for bind9 and resovconf |
tags: | removed: apparmor |
summary: |
- resolvconf uses wrong path for bind9 and resovconf + resolvconf uses wrong path for bind9 and resolvconf |
Thanks for taking the time to report this bug and helping to make Ubuntu better.
It appears as though the simplest solution is to edit etc/resolvconf/ update. d/bind to change RUN_DIR to /var/run/named. /var/run/named is being used by bind9 in Ubuntu at the moment, and resolvconf simply needs to know about the right location.