EDNS processing correctly in 2.5.0.r ?

Sergei_Shablovsky

Hi dear pfSense Gurus!

After 1 Feb 2021 (The DNS Flag Day) the process of updating DNS servers software on all operators start, and almost 1 year and 14 days done...

Are anyone has some issues as a result of implementing EDNS on upstream ?

johnpoz

Where are you seeing info for flag day 2021?

the edns stuff was from 2019.. I am not seeing any info provided for flagday 2021?

Sergei_Shablovsky

@johnpoz Sorry my stupidness, I mean 2020-10-01 (October 1st 2020). :)

And main question was "are someone has any issue"?

johnpoz

Where you seeing any issues with this, there are not problems with this in 2.4.5p1 - why would you think it would regress in 2.5, when 2.5 is using newer version of unbound.

The default buffer size in unbound is

edns-buffer-size: 4096

The min for that is to set 1232 as a min.. Well over that, and the tcp.. Would be allowed outbound for resolving be default.. The only way anyone could have problems with this is they shot themselves in their own foot. And to be honest they would work hard at it - like forging the gun from ore they dug up, and then also making the bullets by hand after gathering the chemicals to make gun powder hard ;)

Run the test they provide..
https://dnsflagday.net/2020/#action-dns-resolver-operators

jimp

The changes for that were already in 2.4.5-p1

https://redmine.pfsense.org/issues/10293

johnpoz

Yup you can see them in the gui..

Like said you would really have to try hard to mess this up ;) Since it defaults to 4096..