---
title: Hostname routing for Cloudflare Mesh
description: Route traffic to a Cloudflare Mesh node by hostname instead of IP.
image: https://edgetunnel-b2h.pages.dev/changelog-preview.png
---

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

[Skip to content](#%5Ftop) 

# Changelog

New updates and improvements at Cloudflare.

[ Subscribe to RSS ](https://edgetunnel-b2h.pages.dev/changelog/rss/index.xml) [ View RSS feeds ](https://edgetunnel-b2h.pages.dev/fundamentals/new-features/available-rss-feeds/) 

![hero image](https://edgetunnel-b2h.pages.dev/_astro/hero.CVYJHPAd_26AMqX.svg) 

[ ← Back to all posts ](https://edgetunnel-b2h.pages.dev/changelog/) 

## Hostname routing for Cloudflare Mesh

Jul 02, 2026 

[ Cloudflare Mesh ](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-mesh/)[ Cloudflare One ](https://edgetunnel-b2h.pages.dev/cloudflare-one/) 

You can now add [hostname routes](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-mesh/routes/#hostname-routes) to a Cloudflare Mesh node, in addition to CIDR routes.

1. [Client device](https://edgetunnel-b2h.pages.dev/cloudflare-one/team-and-resources/devices/cloudflare-one-client/)  
Requests `wiki.internal.local`
2. DNS query ↓
3. [Cloudflare Gateway](https://edgetunnel-b2h.pages.dev/cloudflare-one/traffic-policies/)  
Returns a token IP, then rewrites the destination to the real private IP.  
`100.80.0.0/16`
4. [Hostname route](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-mesh/routes/#hostname-routes) ↓
5. [Mesh node](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-mesh/)  
Forwards traffic to the host on the local network
6. ↓
7. Private host  
`wiki.internal.local` · `10.0.0.50`

Instead of managing IP ranges, you can attract traffic for a hostname to a Mesh node:

* **Private hostname** (for example, `wiki.internal.local`) — reach an internal application by name, which is useful when it has an unknown or ephemeral IP. On Mesh you do not need to run a DNS server; a local hosts-file entry on the node is enough, or you can use a Gateway resolver policy for split DNS.
* **Public hostname** (for example, `www.example.com`) — route that hostname's traffic through the node and egress via the node's public IP.
[ Go to **Mesh** ](https://dash.cloudflare.com/?to=/:account/mesh) 

For setup steps, prerequisites, and DNS options, refer to [Hostname routes](https://edgetunnel-b2h.pages.dev/cloudflare-one/networks/connectors/cloudflare-mesh/routes/#hostname-routes).

```json
{"@context":"https://schema.org","@type":"BlogPosting","@id":"https://edgetunnel-b2h.pages.dev/changelog/post/2026-07-02-mesh-hostname-routing/#page","headline":"Hostname routing for Cloudflare Mesh · Changelog","description":"Route traffic to a Cloudflare Mesh node by hostname instead of IP.","url":"https://edgetunnel-b2h.pages.dev/changelog/post/2026-07-02-mesh-hostname-routing/","inLanguage":"en","image":"https://edgetunnel-b2h.pages.dev/changelog-preview.png","dateModified":"2026-07-02","datePublished":"2026-07-02","publisher":{"@type":"Organization","name":"Cloudflare","url":"https://www.cloudflare.com/"},"isPartOf":{"@type":"WebSite","@id":"https://edgetunnel-b2h.pages.dev/#website","name":"Cloudflare Docs","url":"https://edgetunnel-b2h.pages.dev/"}}
```