DNS Auflösung Thema/Problem

Minga

Active Member
Oct 20, 2020
49
2
28
Servus zusammen,

ich habe auf eine Micro$oft Mail gewartet und fand folgenden Log:

Feb 26 11:33:04 cluster postfix/smtpd[1652207]: warning: hostname mail-centralusazon11011004.outbound.protection.outlook.com does not resolve to address 52.101.61.4

Die Mail wurde nicht angenommen, weil die PMG den Reverse DNS nicht richtig auflösen konnte. Seltsam... dig kann es:

root@cluster:~# dig -x 52.101.61.4

; <<>> DiG 9.16.48-Debian <<>> -x 52.101.61.4
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36321
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
; COOKIE: 1ac89fd6f21245c40100000065dc69fc56e54b6b226f88c0 (good)
;; QUESTION SECTION:
;4.61.101.52.in-addr.arpa. IN PTR

;; ANSWER SECTION:
4.61.101.52.in-addr.arpa. 10 IN PTR mail-centralusazon11011004.outbound.protection.outlook.com.

;; Query time: 12 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Feb 26 11:37:48 CET 2024
;; MSG SIZE rcvd: 153

Die PMG löst lokal auf über BIND und zwei Open DNS Server
 
Nur mit externer Auflösung fuktioniert die PMG normal...

Feb 26 12:03:26 cluster postfix/smtpd[2213]: connect from mail-centralusazon11010001.outbound.protection.outlook.com[52.101.61.1]
Feb 26 12:03:27 cluster postfix/smtpd[2213]: Anonymous TLS connection established from mail-centralusazon11010001.outbound.protection.outlook.com[52.101.61.1]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
Feb 26 12:03:27 cluster postfix/smtpd[2213]: NOQUEUE: client=mail-centralusazon11010001.outbound.protection.outlook.com[52.101.61.1]...
 
Feb 26 11:33:04 cluster postfix/smtpd[1652207]: warning: hostname mail-centralusazon11011004.outbound.protection.outlook.com does not resolve to address 52.101.61.4
Die Mail wurde nicht angenommen, weil die PMG den Reverse DNS nicht richtig auflösen konnte. Seltsam... dig kann es:
die fehlermeldung sagt aber das umgekehrte, domain -> 51.101... kann nicht aufgelöst werden, und das kann ich hier bestätigen:

Code:
# dig mail-centralusazon11011004.outbound.protection.outlook.com @8.8.8.8

; <<>> DiG 9.18.24-1-Debian <<>> mail-centralusazon11011004.outbound.protection.outlook.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30045
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;mail-centralusazon11011004.outbound.protection.outlook.com. IN A

;; ANSWER SECTION:
mail-centralusazon11011004.outbound.protection.outlook.com. 600 IN A 127.0.0.1

;; Query time: 104 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Mon Feb 26 15:14:10 CET 2024
;; MSG SIZE  rcvd: 103
es löst auf 127.0.0.1 auf

Nur mit externer Auflösung fuktioniert die PMG normal...

Feb 26 12:03:26 cluster postfix/smtpd[2213]: connect from mail-centralusazon11010001.outbound.protection.outlook.com[52.101.61.1]
Feb 26 12:03:27 cluster postfix/smtpd[2213]: Anonymous TLS connection established from mail-centralusazon11010001.outbound.protection.outlook.com[52.101.61.1]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
Feb 26 12:03:27 cluster postfix/smtpd[2213]: NOQUEUE: client=mail-centralusazon11010001.outbound.protection.outlook.com[52.101.61.1]...
achtung, andere domain 11010001 vs 11011004
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!