Version 6 uses TinyDNS not Bind and my guess is that they behave slightly differently (or SME handles them differently)
Correct.
- you may need to add the MAC address for the client NIC to the matching hostname entry in order to get it to work.
As this is an upgrade try deleting an entry and recreating it as a native SME6 entry and see if it behaves differently!
No, none of those will help.
This code in the /var/service/tinydns/root/data/00_functions template is key:
sub get_reverse_lookup_choices
{
my %reverse_lookups = ();
foreach my $host ($hosts->hosts())
{
# A remote host must be a DNS alias.
next if $host->prop('HostType') eq 'Remote';
my $alias = $host->prop('ReverseDNS') || "no";
if ($alias eq "yes")
{
# This host is not a DNS alias, so we should make note of it
# for reverse DNS lookup purposes.
my $ip = host2ip($host);
$reverse_lookups{$ip} = $host->{key};
# Note: Here we clobber any existing key/value pair, so if
# there is more than one host with the same ip flagged as
# being the reversedns host, the last one entered in this hash
# will win. Don't do that. ;-)
}
}
return %reverse_lookups;
}
Looks to me as though creating a "ReverseDNS" property with value of "yes" for each hostname you want to show up in reverse DNS will do what you want:
/sbin/e-smith/config hosts setprop xxxx.your.domain ReverseDNS yes
/sbin/e-smith/signal-event host-modify xxx.your.domain
Either that or change the default from '|| "no"' to '|| "yes"' in the template. Try that in a custom template. If you're happy with the result, pass on the problem and solution to the bugs forum.
Charlie
4 Replies
1067 Views