On 12/19/2013 06:50 PM, Daniel P. Berrange wrote:
> On Mon, Dec 16, 2013 at 04:41:31PM +0200, Laine Stump wrote:
>> On 12/10/2013 04:45 PM, Daniel P. Berrange wrote:
>>> So considering your example XML config above we're debating the
>>> behaviour of the following 5 possible DNS requests
>>>
>>> -
On Mon, Dec 16, 2013 at 04:41:31PM +0200, Laine Stump wrote:
> On 12/10/2013 04:45 PM, Daniel P. Berrange wrote:
> > So considering your example XML config above we're debating the
> > behaviour of the following 5 possible DNS requests
> >
> > - myguest
> > - myguest.example.com
> > - notmyguest
On 12/10/2013 04:45 PM, Daniel P. Berrange wrote:
> So considering your example XML config above we're debating the
> behaviour of the following 5 possible DNS requests
>
> - myguest
> - myguest.example.com
> - notmyguest
> - notmyguest.example.com
> - google.com
>
> Originally
>
> - myguest
On Fri, Dec 06, 2013 at 04:19:01PM +0200, Laine Stump wrote:
> In commit f386825 we began adding the option "--local=/$mydomain/" to
> all dnsmasq commandlines (later changed to "local=/$mydomain/" when we
> moved the options from the commandline to a conf file) with the stated
> reason of preventi
In commit f386825 we began adding the option "--local=/$mydomain/" to
all dnsmasq commandlines (later changed to "local=/$mydomain/" when we
moved the options from the commandline to a conf file) with the stated
reason of preventing forwarding of DNS queries for names that weren't
fully qualified d
