From 13678d5350e006ac31fb64bc47d6432ecc03dec2 Mon Sep 17 00:00:00 2001
From: mzz2017 <2017@duck.com>
Date: Thu, 16 Mar 2023 23:15:12 +0800
Subject: [PATCH] docs(README): add a note

---
 README.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 3e1fe4f..c5c2d97 100644
--- a/README.md
+++ b/README.md
@@ -22,9 +22,10 @@ As a successor of [v2rayA](https://github.com/v2rayA/v2rayA), dae abandoned v2ra
 
 Please refer to [Quick Start Guide](./docs/getting-started) to start using `dae` right away!
 
-## Known Issues
+## Notes
 
 1. If you setup dae and also a shadowsocks server (or any UDP servers) on the same machine in public network, such as a VPS, don't forget to add `l4proto(udp) && sport(your server ports) -> must_direct` rule for your UDP server port. Because states of UDP are hard to maintain, all outgoing UDP packets will potentially be proxied (depends on your routing), including traffic to your client. This behaviour is not what we want to see. `must_direct` makes all traffic from this port including DNS traffic direct.
+1. If users in mainland China find that the first screen time is very long when they visit some domestic websites for the first time, please check whether you use foreign DNS to handle some domestic domain in DNS routing. Sometimes this is hard to spot. For example, `ocsp.digicert.cn` is included in `geosite:geolocation-!cn` unexpectedly, which will cause some tls handshakes to take a long time. Be careful to use such domain sets in DNS routing.
 
 ## TODO