<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/3-vnet-use-cases-to-simplify-internal-access-without-vpns--bhlp6s5d1" -->

---
title: 3 VNet Use Cases to Simplify Internal Access (Without VPNs)
description: Teleport VNet is presented as a VPN alternative that routes traffic through a virtual IP network with DNS routing, letting engineers reach internal APIs, dev...
canonical: https://daily.dev/posts/3-vnet-use-cases-to-simplify-internal-access-without-vpns--bhlp6s5d1
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: 3 VNet Use Cases to Simplify Internal Access (Without VPNs) | daily.dev
og:description: Teleport VNet is presented as a VPN alternative that routes traffic through a virtual IP network with DNS routing, letting engineers reach internal APIs, dev...
og:url: https://daily.dev/posts/3-vnet-use-cases-to-simplify-internal-access-without-vpns--bhlp6s5d1
og:image: https://api.daily.dev/og/posts/BhLp6s5D1.png
og:image:alt: 3 VNet Use Cases to Simplify Internal Access (Without VPNs)
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# 3 VNet Use Cases to Simplify Internal Access (Without VPNs)

**[Teleport](https://daily.dev/sources/teleport)** · 6 min read · 0 upvotes · 0 comments

## Summary

Teleport VNet is presented as a VPN alternative that routes traffic through a virtual IP network with DNS routing, letting engineers reach internal APIs, dev tools, and private container registries directly through familiar CLI tools. Three use cases are covered: direct CLI access to internal APIs (replacing SSH tunnels), pushing/pulling from private container registries without VPN steps, and migrating off legacy VPNs using custom DNS zones that preserve existing internal domain names and TLS certificates. Access is enforced through Teleport's identity-based RBAC and logged for audits.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://goteleport.com/blog/3-vnet-use-cases-to-simplify-internal-access-without-vpns>

## Questions this post answers

### How can I access an internal container registry without connecting to a VPN?

Teleport VNet lets engineers log in to and push or pull from private container registries as if they were publicly available, without a VPN connection. It sets up a local virtual IP subnet with DNS routing, proxies the connection through Teleport using the user's authenticated identity, and logs all access for auditing, while the registry stays fully unexposed.

_Developers comparing VPN alternatives for private registry access can track tools like this on daily.dev._

### How do I migrate off a legacy VPN without breaking hardcoded internal domain names like gitlab.internal.company.com?

Teleport VNet supports custom DNS zones that map existing internal domain names to virtual IPs locally, so a service like gitlab.internal.company.com keeps working after moving off the VPN. Because the domain name stays unchanged, existing TLS certificates continue to validate, avoiding certificate warnings, Git authentication failures, or broken automation scripts.

_Teams planning a VPN migration can follow discussions on tools like this via daily.dev._

## Similar posts on daily.dev

- [I reach every service on my home server from anywhere without opening a single port](https://daily.dev/posts/i-reach-every-service-on-my-home-server-from-anywhere-without-opening-a-single-port-qgiwzdz5k) · XDA Developers · 0 upvotes · 0 comments
- [I self-host anything I want behind CGNAT, and here's how you can too](https://daily.dev/posts/i-self-host-anything-i-want-behind-cgnat-and-here-s-how-you-can-too-vyjujrni5) · XDA Developers · 0 upvotes · 0 comments

---

Tags: [#security](https://daily.dev/tags/security), [#devops](https://daily.dev/tags/devops), [#vpn](https://daily.dev/tags/vpn)

[View this post on daily.dev](https://daily.dev/posts/3-vnet-use-cases-to-simplify-internal-access-without-vpns--bhlp6s5d1)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"3 VNet Use Cases to Simplify Internal Access (Without VPNs)","url":"https://daily.dev/posts/3-vnet-use-cases-to-simplify-internal-access-without-vpns--bhlp6s5d1","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/3-vnet-use-cases-to-simplify-internal-access-without-vpns--bhlp6s5d1"},"datePublished":"2026-08-23T12:19:32.067Z","dateModified":"2026-08-23T12:31:52.748Z","description":"Teleport VNet is presented as a VPN alternative that routes traffic through a virtual IP network with DNS routing, letting engineers reach internal APIs, dev...","image":"https://media.daily.dev/image/upload/s--qPvKM23u--/f_auto/v1722860399/public/Placeholder%2009","thumbnailUrl":"https://media.daily.dev/image/upload/s--qPvKM23u--/f_auto/v1722860399/public/Placeholder%2009","isAccessibleForFree":true,"articleSection":"Teleport","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Teleport","logo":"https://media.daily.dev/image/upload/s--Dw-Bbw6O--/c_limit,w_256/f_auto,q_auto/v1787487494/logos/teleport?_a=BAMAMicg0","url":"https://daily.dev/sources/teleport"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/3-vnet-use-cases-to-simplify-internal-access-without-vpns--bhlp6s5d1","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,devops,vpn","timeRequired":"PT6M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Teleport","item":"https://daily.dev/sources/teleport"},{"@type":"ListItem","position":3,"name":"3 VNet Use Cases to Simplify Internal Access (Without VPNs)"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/3-vnet-use-cases-to-simplify-internal-access-without-vpns--bhlp6s5d1#faq","mainEntity":[{"@type":"Question","name":"How can I access an internal container registry without connecting to a VPN?","acceptedAnswer":{"@type":"Answer","text":"Teleport VNet lets engineers log in to and push or pull from private container registries as if they were publicly available, without a VPN connection. It sets up a local virtual IP subnet with DNS routing, proxies the connection through Teleport using the user's authenticated identity, and logs all access for auditing, while the registry stays fully unexposed. Developers comparing VPN alternatives for private registry access can track tools like this on daily.dev."}},{"@type":"Question","name":"How do I migrate off a legacy VPN without breaking hardcoded internal domain names like gitlab.internal.company.com?","acceptedAnswer":{"@type":"Answer","text":"Teleport VNet supports custom DNS zones that map existing internal domain names to virtual IPs locally, so a service like gitlab.internal.company.com keeps working after moving off the VPN. Because the domain name stays unchanged, existing TLS certificates continue to validate, avoiding certificate warnings, Git authentication failures, or broken automation scripts. Teams planning a VPN migration can follow discussions on tools like this via daily.dev."}}]}
```

