Difference between revisions of "Journalctl -u dnsmasq"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | + | journalctl -u dnsmasq | |
May 08 22:33:27 SERVER dnsmasq[18982]: Maximum number of concurrent DNS queries reached (max: 150) | May 08 22:33:27 SERVER dnsmasq[18982]: Maximum number of concurrent DNS queries reached (max: 150) | ||
Revision as of 08:55, 20 October 2020
journalctl -u dnsmasq
May 08 22:33:27 SERVER dnsmasq[18982]: Maximum number of concurrent DNS queries reached (max: 150)
From man page: https://linux.die.net/man/8/dnsmasq
-0, --dns-forward-max=<queries> Set the maximum number of concurrent DNS queries. The default value is 150, which should be fine for most setups. The only known situation where this needs to be increased is when using web-server log file resolvers, which can generate large numbers of concurrent queries.
Aug 18 12:08:52 SERVER systemd-resolved[754]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP
See also
- dnsmasq, /
etc/dnsmasq.conf,journalctl -u dnsmasq - DNS: Linux DNS, IP,
systemd-resolve,/etc/hosts,whois, Domain registrar,dig,host,nslookup,scutil --dnsdnsmasq,bind,delv,.local,.internal, .onion, FQDN, TTL,/etc/resolv.conf,/etc/systemd/resolved.conf,dscacheutil(macOS),hostname, hostnamectl,bind,resolvectl status, DNS sinkhole, Domain name server, LLMNR, Resource records:MX, TXT, NS, CAA, SSHFP, Apex, CNAME, Wildcard DNS records, Subdomain, /etc/nsswitch.conf,1.1.1.1,8.8.8.8, CoreDNS, dnsPolicy:, Google Public DNS, DNS caches, Kubernetes ExternalDNS, DNS forwarding, IDNA2008, DNS-1035, Domain name registrars, Split-view DNS, Pi-hole, NextDNS
Advertising:
