Zitat von Craig Hurley <[email protected]>:
Hello,
I have the following config in unbound.conf:
# Company DNS
forward-zone:
name: "company.lan"
forward-addr: 192.168.0.1
# OpenDNS via dnscrypt-proxy
forward-zone:
name: "."
forward-addr: 127.0.0.1@40
... and this works great most of the time, the problem is I often receive
emails with links to servers on the company lan such as "http://host1/";
rather than "http://host1.company.lan/";.
I'd prefer not to hardcode the unqualified hostname "host1" to its
*current* IP address as it may be subject to change.
Is there a way to force the unqualified hostname "host1" to be resolved by
the companies internal DNS server on 192.168.0.1?
That's what the search domain on the *client* side is used for. DNS is
never unqualified so it would be wrong if the caching-resolver should
try to care about IMHO.
Regards
Andreas
_______________________________________________
Unbound-users mailing list
[email protected]
http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
