diff options
| author |  fernvenue <git@fernvenue.com>
| 2022-08-30 10:11:27 +0800 |
|---|---|---|
| committer |  Yujia Qiao <code@rapiz.me>
| 2022-08-30 11:06:19 +0800 |
| commit | 881701d68fa93d93b888f45010473fb4cae1587d (patch) | |
| tree | 1cdaf4f4e2570a7dd1d9667eee79f3c5775fc0a1 | |
| parent | 2e9e7374bc046ecda23ebd0aefeb45a560498585 (diff) | |
| download | rathole-881701d68fa93d93b888f45010473fb4cae1587d.tar.gz rathole-881701d68fa93d93b888f45010473fb4cae1587d.tar.zst rathole-881701d68fa93d93b888f45010473fb4cae1587d.zip | |
Update out-of-scope.md
| -rw-r--r-- | docs/out-of-scope.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/out-of-scope.md b/docs/out-of-scope.md index 6314b13..12aecee 100644 --- a/docs/out-of-scope.md +++ b/docs/out-of-scope.md @@ -17,3 +17,7 @@ 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. |