Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
viren-moradiya opened this issue Mar 11, 2020 · 3 comments

Comments

@viren-moradiya
Copy link

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
Copy link
Contributor

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
Copy link

Hi @mrstegeman ,

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

@mrstegeman
Copy link
Contributor

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

@mrstegeman mrstegeman added this to Inbox in WebThings Gateway Mar 12, 2020
WebThings Gateway automation moved this from Inbox to Done Mar 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

3 participants