10:19 a.m.
Now my VMs are getting an internal DNS, instead of libvirt's...
(lago-he-basic-suite-4-1-storage.tlv.redhat.com) for example.
Y.
5:50 p.m.
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.
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.
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?
On Wed, Mar 22, 2017 at 9:19 AM, Yaniv Kaul <ykaul(a)redhat.com> wrote:
Now my VMs are getting an internal DNS, instead of libvirt's...
(lago-he-basic-suite-4-1-storage.tlv.redhat.com) for example.
Y.
8:36 p.m.
On Wed, Mar 22, 2017 at 5:50 PM, Ondrej Svoboda <osvoboda(a)redhat.com> wrote:
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.
Correct, it was a different o-s-t patch that broke it - a follow-up patch
fixed it (thanks to Simone!).
Y.
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.
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?
On Wed, Mar 22, 2017 at 9:19 AM, Yaniv Kaul <ykaul(a)redhat.com> wrote:
> Now my VMs are getting an internal DNS, instead of libvirt's...
> (lago-he-basic-suite-4-1-storage.tlv.redhat.com) for example.
>
> Y.
>
2802
days inactive
2802
days old
2 comments
2 participants
participants (2)
-
Ondrej Svoboda -
Yaniv Kaul