Default domain for home network

Petr Menšík pemensik at
Mon Feb 8 12:53:02 UTC 2021

It seems Android wants you to use full names instead. Which might be
good idea anyway. What are applications on android where you would like
to use those names? Maybe aliases would be simpler there.

Search/domain algorithm are client side. If client=Android does not use
it, there is no other way than to create those names in root. They would
break on any DNSSEC validating client however.

I don't think there is better method than using DHCP hook to create
"cookie. IN CNAME cookie.sesame.street.". It seems FQDN is preferred way
on Android. Which might not be bad thing if it does not support
multicast DNS.


On 2/7/21 4:25 PM, Koos Pol via Unbound-users wrote:
> Background: I have Unbound running on OPNSense as my home network DNS
> server.
> Question: Is there a setting to have Unbound resolve plain host names
> (*cookie*) against my default LAN domain (*sesame.street*)?
> At home, my laptops use /etc/resolv.conf, so everything without a domain
> name (*cookie*), automatically gets the local LAN domain for free
> (*sesame.street*). Now everything resolves just fine:
> *cookie.sesame.street.**
> *
> But I'm running into this issue with the Android phones, which seem to
> strictly query host names (without the local domain name). (Ofcourse,
> they are on DHCP so to do have the local domain name.) As a result,
> Unbound doesn't resolve those queries, but forwards *cookie* to the root
> servers. Which is kinda silly.
> Thanks!
> Koos

Petr Menšík
Software Engineer
Red Hat,
email: pemensik at
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 495 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the Unbound-users mailing list