Donatas Abraitis

Don't know if this is the correct way to fix this, but it works.

**Describe the bug** Lots of such warnings: `Task was destroyed but it is pending!` I noticed that this mostly happens with the _slow_ nodes where the latency is 200-300ms. **Additional...

dns: Handle DNS short failures at startup

3

Not the first time we got DNS resolver error and Nebula failed to start. Let's handle this a bit more gracefuly. Signed-off-by: Donatas Abraitis

Add an ability to specify allow from list

1

Allow from `allow_from` instead of only static hosts. Also, 127.0.0.1 is the wrong source, because 127.0.0.0/8 MUST be allowed. It's a local range.