You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One can add a <domain name='example.com' localOnly='yes'/> type stanza to a libvirt network configuration to have that network's dnsmasq answer DNS queries for that network as is blogged about here.
This would be very useful.
Barring actually implementing this, a similar option to #791 for networks would be a useful stop-gap.
The text was updated successfully, but these errors were encountered:
Actually I'd find that feature very handy as it would remove a requirement on using vagrant-hostmanager locally and make a container with vagrant/vagrant-libvirt easier to use.
I'll try to see what's required over the next week, but it's probably as easy as adding a domain option to the network config options and updating the associated template. Trickier might be restricting usage to additional networks (should not be allowed for the management one i'd say, as too easy to conflict with multiple setups), and catching attempting to redefine a network used by another set of vm's.
One can add a
<domain name='example.com' localOnly='yes'/>
type stanza to a libvirt network configuration to have that network's dnsmasq answer DNS queries for that network as is blogged about here.This would be very useful.
Barring actually implementing this, a similar option to #791 for networks would be a useful stop-gap.
The text was updated successfully, but these errors were encountered: