Bind9: man file for rndc utility mentions wrong config file location
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bind9 (Debian) |
Fix Released
|
Unknown
|
|||
bind9 (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bionic |
Won't Fix
|
Medium
|
Unassigned | ||
Focal |
Won't Fix
|
Medium
|
Unassigned | ||
Groovy |
Won't Fix
|
Medium
|
Unassigned | ||
Hirsute |
Won't Fix
|
Medium
|
Unassigned | ||
Impish |
Won't Fix
|
Medium
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
Kinetic |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Man page for the rndc utility mentions that /etc/rndc.key and /etc/rndc.conf are default locations for config files. That is not true.
> man rndc
```
-c config-file
Use config-file as the configuration file instead of the default, /etc/rndc.conf.
-k key-file
Use key-file as the key file instead of the default, /etc/rndc.key. The key in /etc/rndc.key will be used to authenticate commands sent to the server if the config-file does not exist.
```
In fact, running rndc with strace shows that it looks for these files at /etc/bind
```
futex(0x7ff0e34
stat("/
stat("/
openat(AT_FDCWD, "/etc/bind/
```
# Suggested resolution:
update the man page so it is not misleading.
Use case: on my configuration, Bind9 is configured to listen on 127.0.0.2 because I use another DNS server that handles most traffic at 127.0.0.1. But I could not get rndc to talk to correct ip address regardless of what I wrote at /etc/rndc.conf. Finally, strace revealed that the expected config file location is different from what man page tells. I've spent a considerable amount of time debugging what is wrong with my configuration
# System and version information:
Ubuntu 18.04
Package: bind9
Version: 1:9.11.
Changed in bind9 (Ubuntu Focal): | |
status: | New → Triaged |
Changed in bind9 (Ubuntu Bionic): | |
status: | New → Triaged |
Changed in bind9 (Ubuntu): | |
status: | New → Triaged |
Changed in bind9 (Ubuntu Focal): | |
importance: | Undecided → Medium |
Changed in bind9 (Ubuntu Bionic): | |
importance: | Undecided → Medium |
Changed in bind9 (Ubuntu): | |
importance: | Undecided → Medium |
Changed in bind9 (Ubuntu Groovy): | |
status: | New → Triaged |
status: | Triaged → Confirmed |
Changed in bind9 (Ubuntu Hirsute): | |
status: | New → Confirmed |
status: | Confirmed → Triaged |
Changed in bind9 (Ubuntu Groovy): | |
status: | Confirmed → Triaged |
importance: | Undecided → Medium |
Changed in bind9 (Ubuntu Hirsute): | |
importance: | Undecided → Medium |
Changed in bind9 (Debian): | |
status: | Unknown → New |
Changed in bind9 (Ubuntu Groovy): | |
status: | Triaged → Won't Fix |
Changed in bind9 (Debian): | |
status: | New → Fix Released |
Changed in bind9 (Ubuntu Bionic): | |
status: | Triaged → Won't Fix |
tags: | added: bitesize |
I submitted a patch to Debian through salsa [1], pinged the maintainer in BTS [2], and forwarded the patch upstream [3].
[1] https:/ /salsa. debian. org/dns- team/bind9/ -/merge_ requests/ 16 /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 606767 /gitlab. isc.org/ isc-projects/ bind9/- /issues/ 2717
[2] https:/
[3] https:/