In cases where you boot up really quickly (like in the VM test on a non-busy host), tinydns might want to bind before the loopback interface is fully up. Order tinydns after network.target to fix that.
(not strictly required to start the service)
with improvements suggested by Jörg Thalheim <joerg@thalheim.io>
