104

I just installed a new Ubuntu Server 18.04. I set my hostname hostnamectl set-hostname ****.openbayou.biz and I set /etc/hosts:

127.0.0.1 localhost
[ip address] ****.openbayou.biz hostname
# The following lines are desirable for IPv6 capable hosts
[ip6 address] *****.openbayou.biz hostname
::1     localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

I also installed OSSEC to monitor for new files, errors and changes to my server and I'm now getting these alerts:

Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018- 
0001, retrying transaction with reduced feature level UDP.`

It's now repeating itself:

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

I've looked online for a solution and nobody is reporting this issue.

200_success
  • 1,259
  • 12
  • 22
Gregory Schultz
  • 1,309

11 Answers11

81

This warning is logged by systemd-resolved, whenever a name can not be resolved by the DNS system (e.g. nslookup www.kjfoiqaefah34876asdf.com). This can be tolerated and is no reason to be alarmed. This is no error and nothing needs to be fixed.

Redirecting /etc/resolv.conf to /run/systemd/resolve/resolv.conf is wrong, because this way systemd-resolved is skipped and the application with the faulty DNS request talks directly to the name server and not to the systemd-resolved stub anymore. This way systemd-resolved does not notice the NXDOMAIN events any more and therefore cannot log it any more.

The NXDOMAIN events are caused by packages, which try to access non-existing servers during system startup.

Zanna
  • 72,312
Hermann Klein
  • 926
55

IMPORTANT: The solution posted here hides the problematic message by bypassing an important part of your system (the DNS resolver daemon). It may cause DNS malfunction in the future (example). For a proper way to handle the error message please refer to this answer.

Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018- 
0001, retrying transaction with reduced feature level UDP.

The same error happened to my desktop machine, I don't know if it applies to server too.

It seems that my system had the old config in the place, resulting in a conflict between two services: resolvconf and systemd-resolved.

The symlink /etc/resolv.conf pointed to ../run/resolvconf/resolv.conf

Changing it to point to /run/systemd/resolve/resolv.conf which is managed by systemd, fixed it for me.

Read more here on Ubuntu Forums

Hope that helped.

Zanna
  • 72,312
Panagiotis Tabakis
  • 2,131
15

I asked on the OSSEC GitHub about this error and they recommended writing a rule to ignore NXDOMAIN errors. Add to /var/ossec/rules/local_rules.xml

<rule id="234567" level="0">
 <program_name>systemd-resolved</program_name>
 <match>Server returned error NXDOMAIN</match>
 <description>Usless systemd-resolvd log message</description>
</rule>
Chai T. Rex
  • 5,323
Gregory Schultz
  • 1,309
14

Problem

Although there might be other circumstances where this error will occur, I can definitely say that I've seen it puked in the output of:

systemctl status systemd-resolved

...when systemd-resolved is not configured.

And an Azure Ubuntu 18.04 VM does not have systemd-resolved configured out-of-the-box (as of today, 20191008).

Solution:

Configure systemd-resolved.

Mini systemd-resolved Config HowTo:

NOTE: Following instructions were prepared using Ubuntu 18.04

Edit hosts directive in /etc/nsswitch.conf by prepending resolve which sets systemd-resolved as first source of DNS resolution that will be consulted:

hosts:          resolve files dns

Edit /etc/systemd/resolved.conf. Some suggested settings:

[Resolve]
DNS=8.8.8.8 8.8.4.4
#FallbackDNS=
#Domains=
#LLMNR=no
#MulticastDNS=no
#DNSSEC=no
Cache=yes
DNSStubListener=yes

Restart systemd-resolved:

sudo systemctl restart systemd-resolved

When you next check systemd-resolved's status, the error should now be cleared:

systemctl status systemd-resolved

And DNS resolution should now behave in the expected way.

F1Linux
  • 1,256
12

I noticed the same thing on an Ubuntu 18.04 server which was recently updated to 18.04.1.

It would appear that systemd-resolve logs that message whenever it gets any NXDOMAIN response. In my case I have postfix running. So I get a lot of NXDOMAINS when random servers connect that don't have PTR record set.

You can test it with

systemd-resolve securelogin.example.com

Then you should see the log message appear.

With this in mind it would appear to be a relatively innocuous error and you can ignore it.

abu_bua
  • 11,313
Rwky
  • 286
9

My understanding after having read the previous answers and other web pages such as Ubuntu 18.04 systemd-resolved error NXDOMAIN is that this is more a warning than an error and there is nothing I can do on my side about it.

Therefore, I agree with those who say that we should not try to do something on our side so that these messages are not produced anymore. If we succeed, it is likely that we have altered the normal way the system resolve DNS requests.

However, since I have thousands of them (I am also in a desktop - it's not a server), I don't want them in my syslog file. Therefore, following https://www.rsyslog.com/doc/v8-stable/configuration/filters.html and Number pair prefix to config files, I added a file named 10-resolv.conf with a single line :msg, contains, "Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP" ~ in the directory /etc/rsyslog.d .

The name 10-resolv.conf is not important, but it must precede all other file names in the directory in alphabetic order. The command :msg, contains, <message-part> ~ says that all messages that contains <message-part> must be ignored: the tilde ~ in the command says to drop the message.

Note added: Since I wrote this answer, I installed some packages (for other reasons) and the error message is not produced anymore as checked with journalctl -u systemd-resolved -f. One installed package that might explain the disappearance of this message is libnss-resolve.

Dominic108
  • 1,407
2

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.

Shown up here: https://www.dnsknowledge.com/whatis/nxdomain-non-existent-domain-2/

NIMISHAN
  • 1,625
  • 4
  • 20
  • 28
Guest
  • 29
2

Apparently it doesn't link to 127.0.0.53 anymore, but I had no issues with it since re-linking.

I think there is a bug report out on this one. Anyway, it worked very well after re-linking.

Steps:

# systemctl status systemd-resolved

unlink /etc/resolv.conf


ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf


systemctl restart systemd-resolved


systemctl status systemd-resolved
intosomethin
  • 479
0

I was able to get rid of the message, and by the way I was also able to finally connect to my samba server, by changing the server name to server.domain instead of only server.

rosch
  • 8,168
0

In my case Google Cloud dislikes CloudFlare DNS. After running the following command from bain above

sudo tcpdump -vv port 53 | grep NXDomain

When I open my domain in a browser I get:

dns.google.domain > ....: [udp sum ok] .... NXDomain q: PTR? ... ns: .... SOA ....cloudflare.com. dns.cloudflare.com. ....

Might be the case with other VPS-CDN providers as well.

Moving DNS to your VPS/Cloud provider can help.

Szektor
  • 1
-1

This appears related to EDNS. The difference between using stub-resolv.conf and resolv.conf is options edns0.

Extension mechanisms for DNS (EDNS) is a specification for expanding the size of several parameters of the Domain Name System (DNS) protocol which had size restrictions that the Internet engineering community deemed too limited for increasing functionality of the protocol.

https://en.wikipedia.org/wiki/Extension_mechanisms_for_DNS

More details under this issue: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969

It sounds like, you can simply turn off that "option".

Carson Reinke
  • 159