mirror of
https://github.com/fosrl/docs-v2.git
synced 2026-02-08 05:56:45 +00:00
Working
This commit is contained in:
@@ -2,3 +2,11 @@
|
||||
title: "Aliases"
|
||||
description: "Set a friendly alias hostname that resolves to a host"
|
||||
---
|
||||
|
||||
Aliases provide a secondary, user-friendly address for any of your Resources, allowing users to access the Resource using this alternate name in addition to the original address.
|
||||
|
||||
For instance, a router with the address `10.0.0.1` could be assigned the alias `router.internal`, and users could connect using either. Aliases are accessible to anyone who has access to the Resource, and they are exclusively accessible when connected with a Pangolin client, meaning they function without requiring any external DNS record setup. Furthermore, aliases are protocol agnostic, which means they will work with any network protocol, essentially acting as a pseudo-A record for an address that is only functional within the Pangolin environment.
|
||||
|
||||
# Disable Aliases
|
||||
|
||||
Aliases work
|
||||
@@ -2,3 +2,14 @@
|
||||
title: "Hosts"
|
||||
description: "Provide access to a specific host on the network"
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### What about overlaps?
|
||||
|
||||
Pangolin smooths away overlapping networks and arbitrarily chooses a single site to resolve the IP address or range to. This is because we want connection requests to any Resource to be as simple as possible for the end users: when they connect to a particular IP address or FQDN, Pangolin figures out which site to send it to and the end user never needs to figure this out.
|
||||
|
||||
It is recommended that you create overlapping resources only if absolutely required. If you do, use [Aliases](/manage/resources/private/alias) to explicitly defined which host should be used for a given FQDN or IP address and use the alias to connect.
|
||||
Reference in New Issue
Block a user