bughz/3proxy
1
0
Fork 0
mirror of https://github.com/3proxy/3proxy.git synced 2026-09-02 21:05:49 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update HTML documentation from man pages

Browse Source
This commit is contained in:
github-actions[bot] 2026-08-26 06:15:13 +00:00
parent facc35e287
commit 527f0704a4
1 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/html/man5/3proxy.cfg.5.html
View File

@ -500,9 +500,13 @@ cache size should usually be large enough (for example,
<p style="margin-left:9%; margin-top: 1em"><b>nsrecord</b> <p style="margin-left:9%; margin-top: 1em"><b>nsrecord</b>
<i>&lt;hostname&gt; &lt;hostaddr&gt;</i> <br> <i>&lt;hostname&gt; &lt;hostaddr&gt;</i> <br>
Adds static record to nscache. <b>nscache</b> must be Adds static record to nscache. <b>nscache</b> must be
enabled. If 0.0.0.0 is used as a hostaddr host will never enabled and must come first, because the record is placed in
resolve, it can be used to blacklist something or together the table it allocates, and <b>nserver</b> must be set as
with <b>dialer</b> command to set up UDL for dialing.</p> well: without it the system resolver is used and static
records are never consulted. If 0.0.0.0 is used as a
hostaddr host will never resolve, it can be used to
blacklist something or together with <b>dialer</b> command
to set up UDL for dialing.</p>
<p style="margin-left:9%; margin-top: 1em"><b>fakeresolve</b> <p style="margin-left:9%; margin-top: 1em"><b>fakeresolve</b>