|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: name service error
Subject: Re: name service error
From: Andrew McNamara (andrewm
connect.com.au)
Date: Wed Jan 26 2000 - 06:49:10 CST
- Next message: Miguel A.L. Paraz: "Bouncing old mail for backup MX"
- Previous message: Leif Nixon: "Re: qmgr logging breaks"
- In reply to: Hal Snyder: "Re: name service error"
- Reply: Andrew McNamara: "Re: name service error"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
>Thanks to both respondents for replies. Turns out the name given in
>the relay host entry of main.cf is a CNAME and not an A record entry
>in DNS. For some reason mailers frown on this. Even changing the CNAME
>to A didn't help (reverse DNS checked?) - I had to use the bona fide A
>NAME record in the host.
>
>I don't know what changed on our network when. Problem is worked
>around. My only request to the postfix author would be to make the DNS
>error message a little more explicit - if CNAME or reverse are being
>checked, report those errors as such - much easier to track than the
>general message, "Name service error".
I think surounding the relayhost name with square brackets disables the
normal behaviour of looking up MX records for the host in question and
forces it to treat it as a regular host name (which would accept a
CNAME)
I.e.,
relayhost = [smtp.internal]
---
Andrew McNamara (System Architect)
connect.com.au Pty Ltd
Lvl 3, 213 Miller St, North Sydney, NSW 2060, Australia
Phone: +61 2 9409 2117, Fax: +61 2 9409 2111
- Next message: Miguel A.L. Paraz: "Bouncing old mail for backup MX"
- Previous message: Leif Nixon: "Re: qmgr logging breaks"
- In reply to: Hal Snyder: "Re: name service error"
- Reply: Andrew McNamara: "Re: name service error"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
This archive was generated by hypermail 2b27 : Wed Jan 26 2000 - 06:51:06 CST