Can not receive mails, MXTOOLBo says MX Record not publiched, dig mx muekno.de gives no result. DNS is ISPconfig controlled. here is my ISPconfig generated 7etc/bind/pri.muekno.de cat pri.muekno.de $TTL 3600 @ IN SOA mike.muekno.de. mk.muekno.de. ( 2026052701 ; serial, todays date + todays serial # 3600 ; refresh, seconds 1000 ; retry, seconds 1209600 ; expire, seconds 3600 ) ; minimum, seconds ; muekno.de. 3600 A 78.138.61.177 muekno.de. 3600 NS ns2.muekno.de. muekno.de. 3600 TXT "v=spf1 mx a ~all" ns2 3600 A 62.54.177.160 muekno.de. 3600 NS mike.muekno.de. mike 3600 A 78.138.61.177 muekno.de 3600 MX 10 mike.muekno.de. nextcloud 3600 A 78.138.61.177 muekno.de. 3600 CAA 0 issue "letsencrypt.org" mob 3600 A 62.54.177.160 gwweb 3600 A 62.54.177.160 gwmail 3600 A 62.54.177.160 rspamd 3600 A 78.138.61.177 pve 3600 A 62.54.177.160 pbs 3600 A 62.54.177.160 ha 3600 A 62.54.177.160 mail2 3600 A 62.54.177.160 rainer 3600 A 78.138.61.177 nsx 3600 A 62.54.177.160 need help
corrected that, but still get no mail. root@mike:/etc/bind# cat pri.muekno.de $TTL 3600 @ IN SOA mike.muekno.de. mk.muekno.de. ( 2026052702 ; serial, todays date + todays serial # 3600 ; refresh, seconds 1000 ; retry, seconds 1209600 ; expire, seconds 3600 ) ; minimum, seconds ; muekno.de. 3600 A 78.138.61.177 muekno.de. 3600 NS ns2.muekno.de. muekno.de. 3600 TXT "v=spf1 mx a ~all" ns2 3600 A 62.54.177.160 muekno.de. 3600 NS mike.muekno.de. mike 3600 A 78.138.61.177 muekno.de. 3600 MX 10 mike.muekno.de. nextcloud 3600 A 78.138.61.177 muekno.de. 3600 CAA 0 issue "letsencrypt.org" mob 3600 A 62.54.177.160 gwweb 3600 A 62.54.177.160 gwmail 3600 A 62.54.177.160 rspamd 3600 A 78.138.61.177 pve 3600 A 62.54.177.160 pbs 3600 A 62.54.177.160 ha 3600 A 62.54.177.160 mail2 3600 A 62.54.177.160 rainer 3600 A 78.138.61.177 nsx 3600 A 62.54.177.160
DNS seems to be correct now. Then you might want to check your mail.log file. Or you closed port 25 incoming in an external firewall.
Checked a lot of things. no firewall problem at all. port 25 is fine. It is still a DNS Problem. i.e. if I try a working mailserver fro a customer i get. ping: mail.fensterhaus.de: Temporärer Fehler bei der Namensauflösung When I try to send me a Mail from there with telnet i see the problem my Mailserver can not resolv the hostname 450 4.7.1 <mail.fensterhaus.de>: Helo command rejected: Host not found how to get information about the reason of "Temporärer Fehler bei der Namensauflösung"
Fürther information, the server is aproxmox pve debian 12.x Everyting worked fine till yesterday since nearly a year.
That's a different domain than the domain you mentioned above and where you fixed the issue. So this is a different error and not related to the initial post about the zone muekno.de. As the error message implies, you missed creating an A-Record for mail.fensterhaus.de here.
No the problem domain is still muekno. de . the Domain fensterhaus.de is from I Customer whom I support and I have full root access via ssh andwireguard VPN an I can Use for tests. MfG
The problem is not muekno.de, see here: Code: 450 4.7.1 <mail.fensterhaus.de>: Helo command rejected: Host not found how to get information about the reason of "Temporärer Fehler bei der Namensauflösung" The problem is that mail.fensterhaus.de does not exist in DNS as an A record. This is not related to muekno.de at all. Or our server is not able to resolve domain names at all, but this would also not be an issue about the zone muekno.de, but an issue with the base setup of your server.
The problem is a missing A-record for mail.fensterhaus.de in the DNS zone fensterhaus.de, if you manage the DNS for fensterhaus.de, then you must add it. if you don't manage this domain but you know its owner, then contact the owner and tell hom to add it on his DNS server.
It is not only with domain fensterhaus.de. Every hostnameI try to ping gives me temporary ... , but I can ping every IP address. Provider checked and says at his side everything is OK.
Then you have an issue with your resolving the name server configuration on your server. Providers configure them differently, and this is set up before you configure ISPConfig.
Also, have you checked that your local DNS server, in case you installed one, is running? Have you tried restarting it? Did you check the logs? Maybe you added your muekno.de zone as a primary and secondary zone on the same server, which would make BIND fail.
the primary DNS ist at78.138.61.1777 abd the secondary is at 62.54.177.160 Yes it is a genreal resolv propblem, but why was everything ok till yesterday evening. what can/should I check to find the problem. Server is Debian 12 uodated lst Sunday, ISPconfig is the latest Version 3.3 ISPconfig Monitor shows all green systemctl status named shows no problems and runnig.
