Skip to content

Commit fbe70aa

Browse files
authored
Apply suggestions from code review
1 parent 1dfea82 commit fbe70aa

File tree

1 file changed

+2
-2
lines changed
  • src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic

1 file changed

+2
-2
lines changed

src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/local-domains.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -51,9 +51,9 @@ Local Domain Fallback configuration only impacts where DNS requests get resolved
5151

5252
The domain will no longer be excluded from Gateway DNS policies, effective immediately.
5353

54-
## Handling reverse DNS lookups for internal IPs.
54+
## Reverse DNS lookups for internal IPs
5555

56-
By default Warp will send reverse DNS querys (IP to hostname) to public DNS servers, in order to resolve internal reverse DNS lookups a local domain fallback entry needs to be added for in-addr.arpa that points to your internal DNS server IP. in-addr.arpa is the "domain" used for reverse DNS queries, so adding a local domain fallback entry for this will send reverse DNS queries to your local DNS server.
56+
By default, Warp sends [reverse DNS queries](https://www.cloudflare.com/learning/dns/glossary/reverse-dns/) to public DNS servers. To lookup the domain name associated with an internal IP address, [add a local domain fallback entry](#add-a-domain) for `in-addr.arpa` (IPv4) and/or `ip6.arpa` (IPv6) that points to your internal DNS server IP. `in-addr.arpa` and `ip6.arpa` are top-level domains [reserved](https://www.iana.org/domains/arpa) for reverse DNS queries. By adding a local domain fallback entry for these domains, all reverse DNS queries (such as `dig -x 1.1.1.1`) will now resolve through your local DNS server.
5757

5858
## Related resources
5959

0 commit comments

Comments
 (0)