On 02.12.2015 14:03, Neal Becker wrote: > Neal Becker wrote: > >> P J P wrote: >> >>> Hello Neal, >>> >>>> On Wednesday, 2 December 2015 1:03 AM, Neal Becker wrote: >>>> For example, when I'm at work, I can access hostA.work.com >>>> where resolving hostA only works by talking to dnsserverA.work.com, >>>> which was setup by the usual dhcp and then when I'm at home >>>> >>>> google.com is resolved as normal, using my ISP's dhcp to configure dns. >>>> And this must work without the user ever editing some unbound config >>>> file. >>> >>> >>> Yes, it does work that way. The proposed solution(tools) is available >>> in >>> current Fedora repositories and is easy to set-up and test. >>> >>> >>> -> >>> >> > https://fedoraproject.org/wiki/Changes/Default_Local_DNS_Resolver#How_To_Test >>> >>> >>> Please let us know if you face any difficulties. Thank you. >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1287607 >> >> > So remaining difficulties are: > > * howto prevent dnsmasq from starting (right now I'm just manually killing > it for testing)
This is needed only if you intentionally started dnsmasq. You don't need to kill all dnsamsq instances in the system (e.g. the ones started by libvirt). I'll review the change wiki in this regard. > * howto get domainname set automatically from dhcp As discussed in the Bug, this is not going to work and it is expected not to. Setting search domains from DHCP is a security issue. Tomas > -- > devel mailing list > devel@lists.fedoraproject.org > http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org > -- Tomas Hozza Software Engineer - EMEA ENG Developer Experience PGP: 1D9F3C2D UTC+1 (CET) Red Hat Inc. http://cz.redhat.com -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
