Dan Winship 50bafeaf2e dns-manager: fix the rules for public suffixes and search domains (rh #851521) ... dfe194ee made it so that we don't use "public suffixes" as resolv.conf search domains (eg, we don't add "search com" if the hostname is "example.com"). However, if this results in us writing a resolv.conf with no "search" line at all, then the resolver will fall back to using the parent domain of the hostname as a search domain anyway, thwarting us. To fix that, use the domain itself as a search domain in this case, since that's likely to be the expected behavior anyway. (And even if it's not, there doesn't appear to be any way to block the resolver from using the hostname's parent domain as a search domain unless we specify at least one search domain ourselves.) https://bugzilla.gnome.org/show_bug.cgi?id=729137		2014-04-29 14:47:25 -04:00
..
nm-dns-dnsmasq.c	build: add --with-dnsmasq, to specify dnsmasq path	2014-01-03 14:51:16 -05:00
nm-dns-dnsmasq.h	dns-manager: minor cleanups	2013-04-03 10:23:49 -04:00
nm-dns-manager.c	dns-manager: fix the rules for public suffixes and search domains (rh #851521)	2014-04-29 14:47:25 -04:00
nm-dns-manager.h	dns-manager: initialize hostname	2013-12-20 09:31:04 -05:00
nm-dns-plugin.c	core: track which interface an IP config came from	2013-02-07 15:31:00 -06:00
nm-dns-plugin.h	dns-manager: minor cleanups	2013-04-03 10:23:49 -04:00
nm-dns-utils.c	coverity: fix various warnings detected with Coverity	2013-11-13 15:29:24 +01:00
nm-dns-utils.h	dns: direct IPv4 reverse DNS queries to split DNS servers	2010-12-16 17:49:22 -06:00