By Mohamed Lrhazi @lrhazi
I am just curious how that would work, given the instructions say:
With your TinyPilot booted, you can now access the TinyPilot web interface from any device on your local network by visiting one of the following URLs:
https://tinypilot/
https://tinypilot.local/
https://tinypilot.localdomain/
There seems to be the expectation that such DNS names would resolve at the users computers? how?
Diego @diegoHello @lrhazi - Thank you for posting your question here!
At a high level, this is how it works:
- When the TinyPilot boots, it performs a DHCP request, which includes the hostname (
tinypilot). - Your router, acting as DHCP server, replies with a DHCP offer, that includes the IP address the TinyPilot will use.
- The TinyPilot accepts the DHCP offer, and configures its network interface to use the given IP address.
- Your router adds an entry for
tinypilotto its own DNS resolver, using the IP address it assigned to the TinyPilot via the DHCP offer. - When you type https://tinypilot in your browser, it is your router that is resolving
tinypilotto the corresponding IP address. - Depending on your router, you may have to type https://tinypilot.local or https://tinypilot.localdomain in your browser.
It's worth mentioning that this isn't anything specific to TinyPilot. The OS running the DHCP client needs to include the hostname in the DHCP request, that's all. Most systems do this when they do a DHCP request.
- When the TinyPilot boots, it performs a DHCP request, which includes the hostname (