systemd-resolved[850]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.

I have looked at 10 different articles and there are no clear explanations for a. what causes this b. what dve-2018 is or how to actually solve it rather than ignore it.

It seems to bork with openvpn and it also happens at a very conspicuous moment.

I would enjoy hearing the lq communities thoughts. Also if anyone knows why I am blocked from posting in general.

Here is a suggestion how to solve it: https://askubuntu.com/questions/1058...ting-potential.

Another one (Japanese, but the commands are in Bash): https://www.chazine.com/archives/4094

Here is an explanation with workaround: https://github.com/dns-violations/dn...E-2018-0001.md

I wonder if the security advisory number is not a typo and should be CVE-2018-0001 instead, though the description of this CVE doesn't seem to match the error.

Posting where?

That first link is one of the most bizarre trouebleshooting forum responses I have ever seen, conflicting, absurd, "dont worry about it" answers, then this answer when you scroll down.
Summary:

NXDOMAIN error message means that a domain does not exist.
Some ISPs started DNS hijacking or DNS redirection for NXDOMAIN error messages. It is the practice of redirecting the resolution of Domain Name System (DNS) names to other DNS servers or web servers.
Commonly used for displaying advertisements or collecting statistics.
This practice violates the RFC standard for DNS (NXDOMAIN) responses.
Phishing: Cross-site scripting attacks can occur due to malicious hijacking.

*****Censorship: DNS service providers to block access to selected domains.*******

So germany has begun blocking vnp users! Stop the presses. I thought this was the free world!

Answer to second question:
I am unable to post in the General or Bug Report Forums. This since a few months ago, but I thought Id check back in and it hasnt changed.

Did I say something wrong? For what it is worth, I am also censored at mastadon via a "you need to confirm email address because you havent logged in in 2 weeks" that never sends the confirmation email. Then admins on two servers throw hands up in the air like it is not their fault.

Someone is breaking the internet on purpose and trying to make it look like an accident. Some users are more equal than others, and words are being treated like bugs.

Please, confince me I am worng.

I understood that linking /run/systemd/resolve/resolv.conf to /etc/resolv.conf might help with your NXDOMAIN problem.

Sorry, even though I recently acquired Guru status (wow!), I have no power over your acceptance at certain fora.

So LQ, no helpful responses to this.

Says all I need to know about what this forum really is.

Confirms what I thought already.

Sad.

"what? you are censored, did I do that?"

"what you have a bizarre security error? maybe you can just make it stop showing in logs and that will be the same as making it go away."

Guru yeah lol for realz

BYE

Sorry you feel that way. To form that opinion of a forum with more than 664,000 members based on two polite responses from one person who provided some troubleshooting ideas seems a bit over the top. Were they all not helpful?

That said: AFAIK the NXDOMAIN error message does mean that a domain does not exist in the name server the resolver is using. I would start troubleshooting by figuring out which name server that is. By default, the dig command will display the name server IP being used:
On this desktop, I've configured the resolver to use my router, which is in turn configured to use my ISP's name server.

As to the posting question: There is a Contact Us link at the bottom of every page that let you send a message directly to management to ask why you can't post in General, etc. Not sure why berndbausch telling you that they didn't know why offended you. I don't know why, either, even though I also recently reached Guru status (which is simply a label that means I've made more than 5000 posts)

I wish you luck in your future endeavors

1 members found this post helpful.

Wrong thread. Sorry.