WebThingsIO / registration_server

The registration server for WebThings Gateway.
Mozilla Public License 2.0
79 stars 34 forks source link

To make registration-server work without exposing port 53 to the internet #88

Closed viren-moradiya closed 4 years ago

viren-moradiya commented 4 years ago

Hi Team,

Can the registration and tunnelling process work without exposing the port 53 to the public internet? And if this is not possible, can we separate out DNS server from the registration server?

Thanks, Viren

mrstegeman commented 4 years ago

No, it cannot. The way PageKite is set up in the registration server requires the DNS server to be public. They could potentially be separated, but the registration server needs to communicate directly with the PowerDNS server, which is currently done via a Unix domain socket.

abhijitnathwani commented 4 years ago

Hi @mrstegeman ,

If we could potentially separate out PowerDNS and the registration server, will the PowerDNS server need port 53 exposed to public ?

mrstegeman commented 4 years ago

Yes, it would still have to be exposed to the public. The PowerDNS server serves as the authoritative nameserver for the entire domain.