Server: Option to specify which interfaces to use

[mageddo]

Summary & Motivation

As requested at #544, it can be useful to bind DPS to one o more but specific network interfaces, by default DPS binds to all interfaces to make it easier to use, at the same time it can become unwanted or insecure when in more production like usecases.

Description

Create configs to decide which interfaces will be used to bind to the tcp/udp dns and web server

{
  "serverNetworkBindInterface": "en6" ,
  "dnsServerNetworkBindInterface": "en6",
  "webServerNetworkBindInterface": "en6" 
}

Where networkBindInterfacecan be a name ex en6 or a mac address, ex: acde48001122, ACDE48001122, ac:de:48:00:11:22, AC:DE:48:00:11:22

• All configs will be default to null, which means all interfaces will be binded (0.0.0.0)
• serverNetworkBindInterface will apply to both DNS and Web server
• dnsServerNetworkBindInterface and webServerNetworkBindInterface will override the serverNetworkBindInterface config

Alternatives

Run DPS inside a docker container to prevent DPS to bind to unwanted interfaces at the host.

[ak2766]

DPS has matured into a versatile tool. I think it is time it was included in DNS comparison table!

[mageddo]

See #609

[mageddo]

Consider to have the same configuration to choose the IP instead of the interface name