On 2014-10-27 16:55, Ahmad Ardiansyah wrote: > Mon 2014-10-27 16:26:08: [948618] Performing PTR lookup > (147.132.170.134.IN-ADDR.ARPA) > Mon 2014-10-27 16:26:48: [948618] * DNS: 40 second wait for DNS > response exceeded (DNS Server: 209.244.0.3) > Mon 2014-10-27 16:27:28: [948618] * DNS: 40 second wait for DNS > response exceeded (DNS Server: 209.244.0.4) > Mon 2014-10-27 16:27:28: [948618] * No PTR records found
Harusnya ada PTR recordnya, hanya tidak match dengan SMTP banner (FQDN host), tetapi mestinya tidak menjadi masalah di versi MDaemon yang Anda pakai sekarang karena PTR record itu forward-confirm Reverse DNS. http://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS $ host 134.170.132.147 209.244.0.3 Using domain server: Name: 209.244.0.3 Address: 209.244.0.3#53 Aliases: 147.132.170.134.in-addr.arpa domain name pointer mail-sg1on0147.outbound.protection.outlook.com. $ host mail-sg1on0147.outbound.protection.outlook.com 209.244.0.4 Using domain server: Name: 209.244.0.4 Address: 209.244.0.4#53 Aliases: mail-sg1on0147.outbound.protection.outlook.com has address 134.170.132.147 sementara FQDN hostnya terdaftar di internet. $ host APAC01-HK1-obe.outbound.protection.outlook.com APAC01-HK1-obe.outbound.protection.outlook.com has address 207.46.51.123 APAC01-HK1-obe.outbound.protection.outlook.com has address 207.46.51.124 APAC01-HK1-obe.outbound.protection.outlook.com has address 207.46.51.125 APAC01-HK1-obe.outbound.protection.outlook.com has address 207.46.51.126 APAC01-HK1-obe.outbound.protection.outlook.com has address 207.46.51.117 APAC01-HK1-obe.outbound.protection.outlook.com has address 207.46.51.118 APAC01-HK1-obe.outbound.protection.outlook.com has address 207.46.51.119 APAC01-HK1-obe.outbound.protection.outlook.com has address 207.46.51.120 APAC01-HK1-obe.outbound.protection.outlook.com has address 207.46.51.121 APAC01-HK1-obe.outbound.protection.outlook.com has address 207.46.51.122 > apakah ada solusi agar error ini tidak muncul kembali ? Mungkin karena koneksi internet Anda sibuk sehingga akses ke public DNS jadi gagal Coba naikkan idle time out DNS lookup sampai nilai maksimum http://mdaemon.dutaint.co.id/14.5/index.html?default-domain-and-servers_timouts.htm Wait 60 seconds for MX DNS server responses Wait 60 seconds for A-Record DNS server responses Kalau masih terkadang gagal, lakukan DNS benchmark http://www.mail-archive.com/mdaemon-l%40dutaint.com/msg22546.html lihat cara pakai/test nya disini https://www.grc.com/dns/operation.htm Yang dimasukkan dalam test adalah : 209.244.0.3 209.244.0.4 8.8.8.8 8.8.4.4 202.146.0.8 202.146.0.5 Boleh saja ditambahkan public DNS lain yang ada didaftar http://pcsupport.about.com/od/tipstricks/a/free-public-dns-servers.htm 4 DNS hasil rekomendasi terbaik dari test itu digunakan di MDaemon DNS resolver. Jika masih sering gagal juga, maka Anda perlu install DNS resolver sendiri di MDaemon server sebagai primary DNS resolver. Saya pakai simpleDNS (http://www.simpleDNS.com) di semua server kami, baik untuk authoritative DNS dan atau DNS resolver untuk MDaemon maupun local DNS di LAN sejak beberapa tahun yl, selama ini ok hasilnya. -- syafril ------- Syafril Hermansyah MDaemon-L Moderators, running MDaemon 14.5-64, SP 4.5-64 Harap tidak cc: atau kirim ke private mail untuk masalah MDaemon. If your actions inspire others to dream more, learn more, do more and become more, you are a leader. --- John Quincy Adams -- --[MDaemon-L]------------------------------------------------ Milis ini untuk Diskusi antar pengguna MDaemon Mail Server. Netiket: http://www.netmeister.org/news/learn2quote Arsip: http://mdaemon-l.dutaint.com Dokumentasi : http://mdaemon.dutaint.co.id Henti Langgan: Kirim mail ke MDaemon-L-unsubscribe [at] dutaint.com Berlangganan: kirim mail ke MDaemon-L-subscribe [at] dutaint.com Versi terakhir MD 14.5, SP 4.5, BES 2.0.2, OC 3.0, SG 3.0.2
