TrueCloudLab/coredns
16
0
Fork 2
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

plugin/bufsize: add usecase description (#3437)

Browse source 
* add usecase

Signed-off-by: yukihira <yukihira.lab@gmail.com>

* fix some comments

Signed-off-by: ykhr53 <yukihira.lab@gmail.com>
This commit is contained in:
Kohei Yoshida 2019-11-14 07:37:45 +00:00 • committed by Miek Gieben
parent 1743ca3f02
commit 8cc034eece
1 changed files with 11 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
plugin/bufsize/README.md
View file

@ -16,6 +16,7 @@ The default value is 512, and the value must be within 512 - 4096.
Only one argument is acceptable, and it covers both IPv4 and IPv6.
## Examples
Enable limiting the buffer size of outgoing query to the resolver (172.31.0.10):
```corefile
. {
bufsize 512
@ -24,7 +25,15 @@ Only one argument is acceptable, and it covers both IPv4 and IPv6.
}
```
If you run a resolver on 172.31.0.10, the buffer size of incoming query on the resolver will be set to 512 bytes.
Enable limiting the buffer size as an authoritative nameserver:
```corefile
. {
bufsize 512
file db.example.org
log
}
```
## Considerations
For now, if a client does not use EDNS, this plugin adds OPT RR.
- Setting 1232 bytes to bufsize may avoid fragmentation on the majority of networks in use today, but it depends on the MTU of the physical network links.
- For now, if a client does not use EDNS, this plugin adds OPT RR.