contrib/job_manager: config servers' UDP size limit

The limits are going to change around Flag Day 2020, which could lead to differences in TC returned to respdiff, so let's hardcode the limit towards clients to 4096 (higher so we don't compare empty answers). That will also keep it up for forwarding (for simplicity), which is OK, I think.

The separation for kresd is recent master: knot-resolver!1026 (merged)

Docs:

• https://bind9.readthedocs.io/en/v9_16_6/reference.html?highlight=max-udp-size#tuning
• https://nlnetlabs.nl/documentation/unbound/unbound.conf/#max-udp-size

I'm not so sure about the meaning in Unbound; in both BIND and Unbound the default hasn't been lowered yet, so currently it's a no-op there and the point is to keep the client side this way for later releases.

(I've done no real testing.)

mentioned in merge request knot-resolver!920 (merged)

assigned to @tkrizek

BIND documentation: https://bind9.readthedocs.io/en/v9_16_6/reference.html?highlight=max-udp-size#tuning

added 1 commit

• 61ac5a34 - contrib/job_manager: config servers' UDP size limit

Compare with previous version

changed the description

Depends on !88 (merged), older unbound doesn't have the max-udp-size option.

Or we could split the MR, as even currently released Unbound and BIND don't need those options.

added 6 commits

• 61ac5a34...2cb6b082 - 5 commits from branch master
• 42a0bde7 - contrib/job_manager: config servers' UDP size limit

Compare with previous version

added 1 commit

• 72aede82 - contrib/job_manager: config servers' UDP size limit

Compare with previous version

resolved all threads

added 1 commit

• 323fcb9d - contrib/job_manager: config servers' UDP size limit

Compare with previous version

The new reference after !88 (merged) hasn't fully stabilized, but my testing seems to confirm this is indeed a no-op change from our current situation.

approved this merge request

merged

mentioned in commit 6bbe3485

This has not been deployed to the CI farm yet, right?

resolved all threads