Would love to give this a try, but being able to assign names to devices in my network with one click (not by manually creating DNS records) is important to me. This is because my users have existing configurations and I don't want to interrupt their workflow.
If using Tailscale (or similar), you can access a device named "example-device" by running ping example-device or ssh user@example-device.
Does this functionality exist? e.g., from the dashboard, can I assign a name to any device, and have all other devices recognize it by that name?
Originally created by @NovaCyntax on GitHub (Jan 7, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/8
Would love to give this a try, but being able to assign names to devices in my network with one click (not by manually creating DNS records) is important to me. This is because my users have existing configurations and I don't want to interrupt their workflow.
If using Tailscale (or similar), you can access a device named "example-device" by running `ping example-device` or `ssh user@example-device`.
Does this functionality exist? e.g., from the dashboard, can I assign a name to any device, and have all other devices recognize it by that name?
@oschwartz10612 commented on GitHub (Jan 7, 2025):
Hi!
I am not super familiar with how TailScale's MagicDNS works but I will try to answer this best I can.
If I understand your question correctly I think you are concerned with managing DNS records. You will have to create at least one DNS record with your DNS provider but you only need one and it can be a wildcard pointing at your VPS. See here about how to set up DNS.
Once you have this one record you can create any number of named resources in Pangolin and they will just work because they are all subdomains of this wildcard pointing at the VPS and you will not have to keep creating DNS records.
Does that answer the question correctly?
<!-- gh-comment-id:2575681299 -->
@oschwartz10612 commented on GitHub (Jan 7, 2025):
Hi!
I am not super familiar with how TailScale's MagicDNS works but I will try to answer this best I can.
If I understand your question correctly I think you are concerned with managing DNS records. You will have to create at least one DNS record with your DNS provider but you only need one and it can be a wildcard pointing at your VPS. See [here about how to set up DNS](https://docs.fossorial.io/Getting%20Started/dns-networking#dns).
Once you have this one record you can create any number of named resources in Pangolin and they will just work because they are all subdomains of this wildcard pointing at the VPS and you will not have to keep creating DNS records.
Does that answer the question correctly?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @NovaCyntax on GitHub (Jan 7, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/8
Would love to give this a try, but being able to assign names to devices in my network with one click (not by manually creating DNS records) is important to me. This is because my users have existing configurations and I don't want to interrupt their workflow.
If using Tailscale (or similar), you can access a device named "example-device" by running
ping example-deviceorssh user@example-device.Does this functionality exist? e.g., from the dashboard, can I assign a name to any device, and have all other devices recognize it by that name?
@oschwartz10612 commented on GitHub (Jan 7, 2025):
Hi!
I am not super familiar with how TailScale's MagicDNS works but I will try to answer this best I can.
If I understand your question correctly I think you are concerned with managing DNS records. You will have to create at least one DNS record with your DNS provider but you only need one and it can be a wildcard pointing at your VPS. See here about how to set up DNS.
Once you have this one record you can create any number of named resources in Pangolin and they will just work because they are all subdomains of this wildcard pointing at the VPS and you will not have to keep creating DNS records.
Does that answer the question correctly?
@NovaCyntax commented on GitHub (Jan 7, 2025):
Yes sir, thank you for the clarification!