diff --git a/public/docs-static/img/manage/dns/service-discovery/add-resource.png b/public/docs-static/img/manage/dns/dns-aliases/add-resource.png similarity index 100% rename from public/docs-static/img/manage/dns/service-discovery/add-resource.png rename to public/docs-static/img/manage/dns/dns-aliases/add-resource.png diff --git a/public/docs-static/img/manage/dns/service-discovery/add-routing-peer.png b/public/docs-static/img/manage/dns/dns-aliases/add-routing-peer.png similarity index 100% rename from public/docs-static/img/manage/dns/service-discovery/add-routing-peer.png rename to public/docs-static/img/manage/dns/dns-aliases/add-routing-peer.png diff --git a/public/docs-static/img/manage/dns/service-discovery/create-network.png b/public/docs-static/img/manage/dns/dns-aliases/create-network.png similarity index 100% rename from public/docs-static/img/manage/dns/service-discovery/create-network.png rename to public/docs-static/img/manage/dns/dns-aliases/create-network.png diff --git a/public/docs-static/img/manage/dns/service-discovery/create-policy.png b/public/docs-static/img/manage/dns/dns-aliases/create-policy.png similarity index 100% rename from public/docs-static/img/manage/dns/service-discovery/create-policy.png rename to public/docs-static/img/manage/dns/dns-aliases/create-policy.png diff --git a/public/docs-static/img/manage/dns/service-discovery/network-overview.png b/public/docs-static/img/manage/dns/dns-aliases/network-overview.png similarity index 100% rename from public/docs-static/img/manage/dns/service-discovery/network-overview.png rename to public/docs-static/img/manage/dns/dns-aliases/network-overview.png diff --git a/public/docs-static/img/manage/dns/service-discovery/records-created.png b/public/docs-static/img/manage/dns/dns-aliases/records-created.png similarity index 100% rename from public/docs-static/img/manage/dns/service-discovery/records-created.png rename to public/docs-static/img/manage/dns/dns-aliases/records-created.png diff --git a/public/docs-static/img/manage/dns/service-discovery/zone-config.png b/public/docs-static/img/manage/dns/dns-aliases/zone-config.png similarity index 100% rename from public/docs-static/img/manage/dns/service-discovery/zone-config.png rename to public/docs-static/img/manage/dns/dns-aliases/zone-config.png diff --git a/src/components/NavigationDocs.jsx b/src/components/NavigationDocs.jsx index f38a5da1..602de690 100644 --- a/src/components/NavigationDocs.jsx +++ b/src/components/NavigationDocs.jsx @@ -165,6 +165,7 @@ export const docsNavigation = [ { title: 'Configuring Nameservers', href: '/manage/dns/nameserver-groups' }, { title: 'DNS Settings', href: '/manage/dns/dns-settings' }, { title: 'Custom Zones', href: '/manage/dns/custom-zones' }, + { title: 'DNS Aliases for Routed Networks', href: '/manage/dns/dns-aliases-for-routed-networks' }, { title: 'DNS Troubleshooting', href: '/manage/dns/troubleshooting' }, ] }, diff --git a/src/pages/manage/dns/custom-zones.mdx b/src/pages/manage/dns/custom-zones.mdx index 40bb49bf..18bcb074 100644 --- a/src/pages/manage/dns/custom-zones.mdx +++ b/src/pages/manage/dns/custom-zones.mdx @@ -111,4 +111,4 @@ Custom DNS Zones have the following limitations: ## Use Cases -- [Service Discovery for Routed Networks](/manage/dns/service-discovery-for-routed-networks) \ No newline at end of file +- [DNS Aliases for Routed Networks](/manage/dns/dns-aliases-for-routed-networks) \ No newline at end of file diff --git a/src/pages/manage/dns/service-discovery-for-routed-networks.mdx b/src/pages/manage/dns/dns-aliases-for-routed-networks.mdx similarity index 85% rename from src/pages/manage/dns/service-discovery-for-routed-networks.mdx rename to src/pages/manage/dns/dns-aliases-for-routed-networks.mdx index b1964910..bc716ce2 100644 --- a/src/pages/manage/dns/service-discovery-for-routed-networks.mdx +++ b/src/pages/manage/dns/dns-aliases-for-routed-networks.mdx @@ -1,4 +1,4 @@ -# Service Discovery for Routed Networks +# DNS Aliases for Routed Networks This guide explains how to use Custom DNS Zones with NetBird's Networks to provide easy-to-remember DNS names for resources in private networks. @@ -23,11 +23,11 @@ This works, but it's problematic: ### The Solution -Service Discovery with Custom DNS Zones solves this by giving your private network resources friendly, memorable DNS names. Instead of `192.168.0.68`, your developers connect to `postgres.netbird.internal` or simply `postgres`. +DNS Aliases with Custom DNS Zones solve this by giving your private network resources friendly, memorable DNS names. Instead of `192.168.0.68`, your developers connect to `postgres.netbird.internal` or simply `postgres`. ### How the DNS Resolution Works -Here's what happens when you set up service discovery and a developer tries to connect to `postgres.netbird.internal`: +Here's what happens when you set up a DNS Alias and a developer tries to connect to `postgres.netbird.internal`: **Setup (One-Time):** @@ -68,7 +68,7 @@ First, create a Custom DNS Zone to manage the DNS records for your private servi - **Enable Search Domain**: Keep this enabled to allow using short names (e.g., `postgres` instead of `postgres.netbird.internal`). 4. Click **Add Zone**. -Delete DNS Zone +Delete DNS Zone ### Step 2: Add DNS Records @@ -87,7 +87,7 @@ Next, add DNS records for each of your services. - **Type**: `A` - **Value**: `192.168.0.78` -DNS Records Created +DNS Records Created ### Step 3: Configure Network Routing @@ -102,7 +102,7 @@ To enable access to your private resources, you need to set up a network with ro - **Description**: `Provides access to internal service resources` 4. Click **Add Network**. -Create Network +Create Network #### Add Network Resources @@ -114,7 +114,7 @@ Add a wildcard resource that will match all services in your DNS zone. - **Groups**: Assign to a resource group (e.g., `internal-services`) 2. Click **Add Resource**. -Add Network Resource +Add Network Resource Repeat the same steps to add the **Internal Postgres** resource with the address `postgres.netbird.internal`. @@ -132,7 +132,7 @@ Create a policy to allow your developers to access these resources. - **Ports**: `All` 2. Click **Continue** twice, then click **Add Policy**. -Create Access Control Policy +Create Access Control Policy #### Add a Routing Peer @@ -142,13 +142,13 @@ Next, add a routing peer that has access to your private network. 1. Click **Add Routing Peer** and select the peer that is running in your data center or VPC. 2. Click **Continue** and then **Add Routing Peer** to confirm. -Add Routing Peer +Add Routing Peer After completing the wizard, your network routing is configured, and the DNS names you created will now work seamlessly with the network routes. You can view your fully configured network in the Networks dashboard: -Fully Configured Network +Fully Configured Network ### Step 4: Verify the Setup