Because a PTR record cannot exist for multiple hosts. Unbound was dashing this out anyway but it caused problems for clients.
> sudo unbound-control -c /var/unbound/unbound.conf list_local_data | grep PTR1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa. 10800 IN PTR localhost.b.l.a.h.b.l.a.h.f.f.9.b.d.0.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. 3600 IN PTR rtr00.lan.1.0.0.127.in-addr.arpa. 10800 IN PTR localhost.15.1.168.192.in-addr.arpa. 3600 IN PTR rtr00.lan.
if (($alias === $tmp_aliases[0] || $tmp_aliases[0]['hostname'] === '*') && !in_array($host->server, $ptr_records, true)) { /* Only generate a PTR record for the non-alias override and only if the IP is not already associated with a PTR. * The exception to this is an alias whose parent uses a wildcard and as such does not specify a PTR record. */
sudo vi /usr/local/etc/inc/plugins.inc.d/unbound.inc
573 if (!($alias...
In case anyone else wants to try:Code: [Select]sudo vi /usr/local/etc/inc/plugins.inc.d/unbound.incGo to line 573, add "!" between first two parenthesesCode: [Select]573 if (!($alias...I ran the unbound-control I mention above, both before and after, diffing the two results and saw all the PTR records for host entries as I expected, and none for the aliases.