mdns-lookup yes creates mdns group
Author: bcookatpcsdCreated Sep 12, 2026Updated Sep 15, 2026
I did look for another report of this, but could not confirm if it exists or not..
[smartdns] | [2026-09-12 14:17:06,206][ INFO][ dns_client.c:537 ] request: 121.188.168.192.in-addr.arpa, qtype: 12, id: 12295, group: mdns
[smartdns] | [2026-09-12 14:17:06,388][ INFO][ context.c:1136] result: 121.188.168.192.in-addr.arpa, client: 192.168.188.112, qtype: 12, id: 29236, group: mdns, time: 183ms
[smartdns] | [2026-09-12 14:17:02,120][ INFO][ dns_client.c:537 ] request: 134.188.168.192.in-addr.arpa, qtype: 12, id: 31942, group: mdns
[smartdns] | [2026-09-12 14:17:03,884][ INFO][ context.c:1136] result: 134.188.168.192.in-addr.arpa, client: 192.168.188.112, qtype: 12, id: 45107, group: mdns, time: 1764ms# grep local53 smartdns.conf
server 192.168.188.1:53 -group local53 -exclude-default-group
nameserver /clean.internal/local53
nameserver /188.168.192.in-addr.arpa/local53
# mdns-lookup yeswithout mdns-lookup defined the local53 nameserver routing works correctly, with mdns-lookup enabled any PTR is returned with .local but only if it exists in mdns.
Was trying to replace/simplify avahi2dns
podman container, host mode networking,
smartdns 1.2026.08.05-1210
Thank you in advance.
Source: pymumu/smartdns