diff options
| author |  Yujia Qiao <code@rapiz.me>
| 2022-08-30 11:06:34 +0800 |
|---|---|---|
| committer |  GitHub <noreply@github.com>
| 2022-08-30 11:06:34 +0800 |
| commit | dcccbb487114fefb37081d4b425179e260b1faec (patch) | |
| tree | 750c3a47fd1bbbc252fb3afc93865aacf40db2ec | |
| parent | 881701d68fa93d93b888f45010473fb4cae1587d (diff) | |
| download | rathole-revert-185-patch-1.tar.gz rathole-revert-185-patch-1.tar.zst rathole-revert-185-patch-1.zip | |
Revert "Update out-of-scope.md"revert-185-patch-1
This reverts commit 881701d68fa93d93b888f45010473fb4cae1587d.
| -rw-r--r-- | docs/out-of-scope.md | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/docs/out-of-scope.md b/docs/out-of-scope.md index 12aecee..6314b13 100644 --- a/docs/out-of-scope.md +++ b/docs/out-of-scope.md @@ -17,7 +17,3 @@ But that doesn't mean it's not useful for other purposes. In the future, more co - *`frp`'s STCP or other setup that requires visitors' side configuration* If that kind of setup is possible, then there are a lot more tools available. You may want to consider secure tunnels like wireguard or zerotier. `rathole` primarily focuses on NAT traversal by forwarding, which doesn't require any setup for visitors. - -- *Caching `local_ip`'s DNS records* - - As responded in [issue #183](https://github.com/rapiz1/rathole/issues/183), `local_ip` cache is not feasible because we have no reliable way to detect ip change. Handle DNS TTL and so on should be done with a DNS server, not a client. Caching ip is generally dangerous for clients. If you care about the `local_ip` query you can set up a local DNS server and enable caching. Then the local lookup should be trivial. |