purgatory/Xray-docs-next
1
0
Fork 0
mirror of https://github.com/XTLS/Xray-docs-next.git synced 2025-04-02 21:06:15 +03:00
Code Issues Projects Releases Packages Wiki Activity

Update log.md

Browse source
This commit is contained in:
风扇滑翔翼 2024-12-25 02:38:55 +08:00 • committed by GitHub
parent c5cf359802
commit 117bb3602b
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 6 additions and 37 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

43
docs/en/config/log.md
View file

@ -50,45 +50,14 @@ The log level for error logs, indicating the information that needs to be record
Log DNS queries made by built-in [DNS clients](./dns.md) to the access log. Example log record: `DOH//doh.server got answer: domain.com -> [ip1, ip2] 2.333ms`.
::: tip TIP 1
Xray doesn't perform all DNS queries via its built-in clients. Therefore, enabling this option doesn't mean that all DNS queries performed by Xray will be logged.
::: tip
1. Xray doesn't perform all DNS queries via its built-in clients. Therefore, enabling this option doesn't mean that all DNS queries performed by Xray will be logged.
2. DNS queries made by built-in [DNS clients](./dns.md) are also logged to the error log (with "Info" level) even if this option is disabled.
3.
4. FakeDNS client queries are never logged to the access log.
:::
::: tip TIP 2
DNS queries made by built-in [DNS clients](./dns.md) are also logged to the error log (with "Info" level) even if this option is disabled.
:::
::: tip TIP 3
FakeDNS client queries are never logged to the access log.
:::
Below is a client config example that allows you to see DNS logs. No server needed.
```json
{
"log": {
"dnsLog": true
},
"dns": {
"servers": ["https://1.1.1.1/dns-query"]
},
"inbounds": [
{
"listen": "0.0.0.0",
"port": 1984,
"protocol": "socks"
}
],
"outbounds": [
{
"protocol": "freedom",
"settings": {
"domainStrategy": "UseIPv4"
}
}
]
}
```
> `maskAddress`: "quarter" | "half" | "full"