Segnalazione #229
bind record ptr
0%
Description
root@server:~# host -l fuss.bzn
fuss.bzn name server ns.fuss.bzn.
ns.fuss.bzn has address 192.168.0.1
proxy.fuss.bzn has address 192.168.0.1
server.fuss.bzn has address 192.168.0.1
test1.fuss.bzn has address 192.168.0.11
test2.fuss.bzn has address 192.168.0.13
test3.fuss.bzn has address 192.168.0.15
test4.fuss.bzn has address 192.168.0.17
test5.fuss.bzn has address 192.168.0.19
root@server:~# nmap -sn --system-dns 192.168.0.0/24 | grep report
Nmap scan report for 192.168.0.11
Nmap scan report for 192.168.0.13
Nmap scan report for 192.168.0.15
Nmap scan report for 192.168.0.17
Nmap scan report for 192.168.0.19
Nmap scan report for server.fuss.bzn (192.168.0.1)
root@server:~# cat /var/cache/bind/db.local
$ORIGIN .
$TTL 604800 ; 1 week
fuss.bzn IN SOA ns.fuss.bzn. root.server.fuss.bzn. (
21 ; serial
604800 ; refresh (1 week)
86400 ; retry (1 day)
2419200 ; expire (4 weeks)
604800 ; minimum (1 week)
)
NS ns.fuss.bzn.
$ORIGIN fuss.bzn.
ns A 192.168.0.1
octofuss CNAME proxy
proxy A 192.168.0.1
server A 192.168.0.1
$TTL 300 ; 5 minutes
test1 A 192.168.0.11
TXT "00a34f2bcf49b05c5528c03b925bd46b22"
test2 A 192.168.0.13
TXT "00d6b33118cc2a86c063bbcafa63a77831"
test3 A 192.168.0.15
TXT "003aa85dc11b56b67f07e6d6a040771b48"
test4 A 192.168.0.17
TXT "0010b8c2ced2d4943f82905bef4dee813e"
test5 A 192.168.0.19
TXT "00a80692c36949d1ae6fc183fa4c30ffae"
$TTL 604800 ; 1 week
wpad CNAME proxy
root@server:~# cat /var/cache/bind/db.192.168.0.0
;
; BIND data file for reverse zone
;
$TTL 604800 IN SOA ns.fuss.bzn. root.server.fuss.bzn. (
IN NS ns.fuss.bzn.
1 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
;
;<rev-ip> IN PTR server.fuss.bzn.
1.0.168.192.in-addr.arpa. IN PTR server.fuss.bzn.
Related issues
Associated revisions
More correction for /etc/dhcp/dhcpd.conf (refs #229): for the reverse
zone we need the network name, not the address. Version bump to
8.0.10-2.
History
Updated by Christopher R. Gabriel about 7 years ago
- Assignee changed from TRUELITE to Simone Piccardi
Updated by Simone Piccardi about 7 years ago
- Status changed from Nuovo to In elaborazione
- Assignee changed from Simone Piccardi to Elena Grandi
The last commit (3b3b3d36) should solve the issue. I did a quick manual check, after rebuilding, installing the last fuss-server (8.0.10-2), a freshly started client was correctly put in the reverse zone:
# host guest-42.fuss.bzn guest-42.fuss.bzn has address 192.168.42.12
and:
# host 192.168.42.12 12.42.168.192.in-addr.arpa domain name pointer guest-42.fuss.bzn.
Installing the 8.0.10-2 version and re-executing fuss-server create
is enough to fix the issue.
Updated by Michael Guggenberg about 7 years ago
ddns-update-style standard;
https://deepthought.isc.org/article/AA-01091/0/ISC-DHCP-support-for-Standard-DDNS.html
Per far sì che record già esistenti vengono attualizati.
Updated by Elena Grandi about 7 years ago
- Assignee changed from Elena Grandi to Michael Guggenberg
I've uploaded a new version (8.0.10-2) of fuss-server to the repo, with the fixes from Simone, so that it can be tested and installed.
Simone suggests to open another ticket for the request in https://work.fuss.bz.it/issues/229#note-4 instead.
Updated by Michael Guggenberg about 7 years ago
- Related to Segnalazione #234: isc-dhcp-server ddns-update-style added
Remove an additional unneeded in-addr.arpa in the dhcpd.conf template
when defining the reverse zone for ddns updates; now the reverse zone
update (refs #229) should work. Version bump to 8.0.10.