<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 22, 2017 at 5:50 PM, Ondrej Svoboda <span dir="ltr"><<a href="mailto:osvoboda@redhat.com" target="_blank">osvoboda@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>I don't think the patch is to blame, the only change it introduced is addition of the enable="yes" parameter to all libvirt <net/> XML definitions, which just confirms the default value in explicit terms.<br></div></div></div></div></blockquote><div><br></div><div>Correct, it was a different o-s-t patch that broke it - a follow-up patch fixed it (thanks to Simone!).</div><div>Y.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><br></div>What do you mean by "internal DNS"? Is libvirt's dnsmasq no longer started? That would be very weird because we still use NAT networks.<br><br></div>At this moment (I have just logged into VPN) I cannot resolve the host (you refer to) by name (I have two nameservers: 10.38.5.26 and 10.35.255.14, both supplied by vpnc). Can you share its address?<br></div><div><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 22, 2017 at 9:19 AM, Yaniv Kaul <span dir="ltr"><<a href="mailto:ykaul@redhat.com" target="_blank">ykaul@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Now my VMs are getting an internal DNS, instead of libvirt's...<div> (<a href="http://lago-he-basic-suite-4-1-storage.tlv.redhat.com" target="_blank">lago-he-basic-suite-4-1-stor<wbr>age.tlv.redhat.com</a>) for example.</div><span class="m_4776300703200888098HOEnZb"><font color="#888888"><div><br></div><div>Y.</div></font></span></div>
</blockquote></div><br></div></div></div></div>
</blockquote></div><br></div></div>