Cannot resolve maps.rspamd.com

Support
, ,
1

I have the same error in my rspamd log (every few seconds):

Feb 12 21:17:20 server rspamd[2284]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out

When i check dig @127.0.0.1 -p 10053 maps.rspamd.com i got:

[root@server ~]# dig @127.0.0.1 -p 10053 maps.rspamd.com

; <<>> DiG 9.11.4-P2-RedHat-9.11.4-9.P2.el7 <<>> @127.0.0.1 -p 10053 maps.rspamd.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

Is it a firewall problem? or what can i do?

thanks

strauch

2

if your server is connected to internet, you can take a beer

From time to time, maps.rspamd.com is not accessible, perhaps rspamd is a victim of its success

You can make a donation to rspamd also

3

I have the same problem on other server, but on port 53 (and not 10053) it is resolved fine.

I think there are some problems with unbound service…

2 Likes
4

workable on the two ports here

5

We solved by adding a second resolve address in rspamd.conf… but I think the problem is not in rspamd, because also dig @127.0.0.1 -p 10053 google.com is not resolved fine.

1 Like
6 
root@prometheus ~]# dig @127.0.0.1 -p 10053 google.com

; <<>> DiG 9.11.4-P2-RedHat-9.11.4-9.P2.el7 <<>> @127.0.0.1 -p 10053 google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25331
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google.com.			IN	A

;; ANSWER SECTION:
google.com.		300	IN	A	172.217.19.238

;; Query time: 8 msec
;; SERVER: 127.0.0.1#10053(127.0.0.1)
;; WHEN: Wed Feb 12 22:16:56 CET 2020
;; MSG SIZE  rcvd: 55
7

We have the same problem with servers on satellite connections. The dig to port 53 on google.com works but 10053 fails every time. Is there a way to get around this?

Feb 25 16:54:50 srv rspamd[3264]: <7n3qic>; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:54:51 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:54:51 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:54:51 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:54:51 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:54:52 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:54:53 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:54:54 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:01 srv rspamd[3264]: <7n3qic>; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:02 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:02 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:02 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:02 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:03 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:04 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:05 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:12 srv rspamd[3264]: <7n3qic>; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:13 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:13 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:13 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:13 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:14 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:15 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:16 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:23 srv rspamd[3264]: <7n3qic>; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:24 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:24 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:24 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:24 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:25 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:26 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:27 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:34 srv rspamd[3264]: <7n3qic>; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:35 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:35 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:35 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:35 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:36 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:37 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:38 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: query timed out
Feb 25 16:55:43 srv rspamd[3264]: <7n3qic>; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: server fail
Feb 25 16:55:43 srv rspamd[3264]: ; map; rspamd_map_dns_callback: cannot resolve maps.rspamd.com: server fail

8

I solved: the ISP router was blocking dns queries.

2 Likes
9

Hello,

the only solution i find was to change the dns port from 10053 to 53. Why is port 10053 in use? I didnt use nethserver as dns server, so the nethserver asked my ubiquiti usg. maybe this is the problem?
i changed the config file /etc/rspamd/rspamd.conf

dns {
    timeout = 1s;
    sockets = 16;
    retransmits = 5;
    nameserver = ["127.0.0.1:10053:1"];
}

to:

dns {
    timeout = 1s;
    sockets = 16;
    retransmits = 5;
    nameserver = ["127.0.0.1:53:1"];
}
10

is used by unbound

11

Am I wrong or unbound is not used by NethServer?

12 
[root@prometheus ~]# systemctl status unbound
â—Ź unbound.service - Unbound recursive Domain Name Server
   Loaded: loaded (/usr/lib/systemd/system/unbound.service; enabled; vendor preset: disabled)
   Active: active (running) since Sat 2020-05-23 15:59:07 CEST; 3 days ago
 Main PID: 451 (unbound)
   CGroup: /system.slice/unbound.service
           └─451 /usr/sbin/unbound -d

May 23 15:59:06 prometheus.de-labrusse.fr systemd[1]: Starting Unbound recursive Domain Name Server...
May 23 15:59:06 prometheus.de-labrusse.fr unbound-checkconf[434]: unbound-checkconf: no errors in /etc/unbound/unbound.conf
May 23 15:59:07 prometheus.de-labrusse.fr systemd[1]: Started Unbound recursive Domain Name Server.
May 23 15:59:07 prometheus.de-labrusse.fr unbound[451]: [451:0] notice: init module 0: subnet
May 23 15:59:07 prometheus.de-labrusse.fr unbound[451]: [451:0] notice: init module 1: validator
May 23 15:59:07 prometheus.de-labrusse.fr unbound[451]: [451:0] notice: init module 2: iterator
May 23 15:59:07 prometheus.de-labrusse.fr unbound[451]: [451:0] info: start of service (unbound 1.6.6).

yes running on 10053 for rspamd

13

So NethServer installs dnsmasq (as default), bind (as option), and unbound (as dependency of rspamd).
DNS overhauling?

14

Unbound is there for caching dns request, in fact rspamd does a lot

15

Hi all,

I have same problem with a friend NethServer in France. He cannot send nor receive mails.

I changed the file as above.

Now he can receive mail but cannot send.

Do I have to make a custom template of
/etc/e-smith/templates/etc/rspamd/rspamd.conf/20Options
to make the change permanent ?

What about the sending mail problem, they are stucked in the queue?

Michel-André

16

Hi all,

I did a custom template, expand it and restart rspamd.

Emails are received OK but sending are still stucked in the mail queue.

Michel-André

17

What kind of router have you got?

Check if there are secure dns or similar enabled.

18

Good morning all,
I am the person who has trouble sending and receiving emails. (Big thanks to Michel, for your help,
I’m not very good with Linux)
About 15 days ago I moved the server and changed the IP, of course I did the
Modification at my registar, everything was working fine, and a few days ago nothing
I have a very classic Free Box.
If you have an idea , thank you
Frederic

19

hum, I cannot understand why rspamd could block the email, I would bet that the solution is in maillog, find why the email has been rejected.

1 Like
20

same, maillog is the key

I am not sure that to use this thread will help to get a solution. One problem, one thread