Comment 21 for bug 1784879

I can confirm that removing the check from #20 works for my use case (which is similar to the one brought up in #17), and would suggest that an additional attribute on the Network object (e.g. "dns_force_entries", default=False) be created, so that users wishing to use automated DNS publishing are able to do so while keeping the "old" behavior as default for backwards compatibility.