Hi,
Got my network team to allow me port 53 to another dns resolver1.opendns.com (
entered this into my resolv.conf ) and get similar results,
Nov 18 14:20:32 obeml1 postfix/smtp[21362]: [ID 197553 mail.info] AAC73239403:
to=postmas...@eurocommerce.ie, relay=none, delay=20,
Laurence Moughan:
obeml1# dig @resolver1.opendns.com eurocommerce.ie
; DiG 8.3 @resolver1.opendns.com eurocommerce.ie
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr rd ra; QUERY: 1, ANSWER: 1,
I do ( detailed in the same email ) - and i get timeouts when there is a typo
in the record - all correct records come back fine.
Wietse Venema wie...@porcupine.org 18/11/09 14:43:46
Laurence Moughan:
obeml1# dig @resolver1.opendns.com eurocommerce.ie
; DiG 8.3
Laurence Moughan:
I do ( detailed in the same email ) - and i get timeouts when there is a
typo in the record - all correct records come back fine.
You are doing one MX lookup that times out. Then, two A lookups
for the email domain name, and that is wrong.
Instead, you need to do one MX
Found problem,
Its not postfix nor os - thanks for all the help,
its my toplayer IDS !
Nov 18 14:16:31 [10.142.4.252.2.2] 10.142.4.252 IPS5500-150E: id=060002
pt=TLN-TS prot=UDP cip=208.67.222.222 cprt=53 sip=193.95.152.20 sprt=48020
atck=tln-101047 disp=mitigate ckt=1 src=extern
Thanks Wietse,
Thats the answer i was looking for - wil upgrade today.
Wietse Venema wie...@porcupine.org 17/11/09 00:18:48
Postfix versions 2.3 and later skip a DNS record with a bad name.
Unsupported Postfix versions pretend that the lookup failed when
the result is invalid.
Wietse
Ok ,
I upgraded to 2.6.5 - and still fails,
eg
Nov 17 10:42:21 obeml1 postfix/smtp[5444]: [ID 197553 mail.info] 6D12F239406:
to=postmas...@eurocommerce.ie, relay=none, delay=40, delays=0.26/0/40/0,
dsn=4.4.3, status=deferred (Host or domain name not found. Name service error
for
Laurence Moughan:
Ok ,
I upgraded to 2.6.5 - and still fails,
Works for me. I suspect that your LOCAL dns server is making trouble.
Wietse
Wietse Venema:
Laurence Moughan:
Ok ,
I upgraded to 2.6.5 - and still fails,
Works for me. I suspect that your LOCAL dns server is making trouble.
Logging:
Nov 17 06:34:54 spike postfix/qmgr[6861]: 509F61F3EA7:
from=wie...@porcupine.org, size=338, nrcpt=1 (queue active)
Nov 17
Hi all,
Someo of my mail destinations failing, due to unable to find mx,
However when i DIG i see the mx record, but has a typo ( the remote needs to
fix thier dns )
; DiG 9.3.2 @localhost eurocommerce.ie MX ; (2 servers found) ;;
global options: printcmd ;; Got answer: ;; -HEADER-
Quoting Laurence Moughan laurence.moug...@aerlingus.com:
Hi all,
Someo of my mail destinations failing, due to unable to find mx,
However when i DIG i see the mx record, but has a typo ( the remote
needs to fix thier dns )
My postfix fails to find an mx
(Host or domain name not found.
Thanks Eero,
But im concerned that more will fail in future - should my postfix be able to
resolve this ( the groupwise system can and both are pointing at same ns )
Thanks
Laurence
Eero Volotinen eero.voloti...@iki.fi 16/11/09 14:16:51
Quoting Laurence Moughan
Quoting Laurence Moughan laurence.moug...@aerlingus.com:
Thanks Eero,
But im concerned that more will fail in future - should my postfix
be able to resolve this ( the groupwise system can and both are
pointing at same ns )
No, ask dns admin to fix that dns zone.
--
Eero
On Monday 16 November 2009 14:27:19 Eero Volotinen wrote:
Quoting Laurence Moughan laurence.moug...@aerlingus.com:
Thanks Eero,
But im concerned that more will fail in future - should my postfix
be able to resolve this ( the groupwise system can and both are
pointing at same ns )
No,
Possibly make sense for DNS servers to reject such records? I have seen a
proliferation of same, most of which were cut and paste from Google's web
page.
Sounds like very poor dns management, maybe you can change dns service
provider?
--
Eero
On Monday 16 November 2009 15:08:08 Eero Volotinen wrote:
Possibly make sense for DNS servers to reject such records? I have seen a
proliferation of same, most of which were cut and paste from Google's web
page.
Sounds like very poor dns management, maybe you can change dns service
On Mon, Nov 16, 2009 at 01:55:46PM +, Laurence Moughan wrote:
eurocommerce.ie. 3151 IN MX 10 cluster8.eu.messagelabs.com.
eurocommerce.ie. 3151 IN MX 20 cluster8a.eu.messagelabs.com\032.
See the (\032) trailing commas on the line containing the mx also
seem to fail me.
The MX records
Postfix versions 2.3 and later skip a DNS record with a bad name.
Unsupported Postfix versions pretend that the lookup failed when
the result is invalid.
Wietse
18 matches
Mail list logo
