Y z wrote:
I'm sure (well, almost sure) that bind got hosed *somehow*. Postfix
really doesn't have more than a bit part in this drama. I just want to
figure out why Postfix gets different answers than dig at the command
prompt.
Relax.
I am sure you did
dig that.other.mail.org MX.
Then the
Y z put forth on 4/28/2010 2:08 AM:
>
>
>> Date: Wed, 28 Apr 2010 01:56:55 -0500
>> From: s...@hardwarefreak.com
>> To: postfix-users@postfix.org
>> Subject: Re: 'Domain not found' errors after Ubuntu upgrade
>>
> Date: Wed, 28 Apr 2010 15:20:08 +0800
> From: udip...@uniten.edu.my
> To: yan...@hotmail.com
> CC: s...@hardwarefreak.com; postfix-users@postfix.org
> Subject: Re: 'Domain not found' errors after Ubuntu upgrade
>
>
>&
Start by making sure that these match:
/etc/resolv.conf
/var/spool/postfix/etc/resolv.conf
Yup. Postfix start warns me if they differ.
I tried putting in nameservers there, but that makes it worse: then postfix
(it's supposed to relay) accepts the messages, then can't find te relay d
> Date: Wed, 28 Apr 2010 01:56:55 -0500
> From: s...@hardwarefreak.com
> To: postfix-users@postfix.org
> Subject: Re: 'Domain not found' errors after Ubuntu upgrade
>
> Stan Hoeppner put forth on 4/28/2010 1:50 AM:
>>
Stan Hoeppner put forth on 4/28/2010 1:50 AM:
> Y z put forth on 4/28/2010 1:36 AM:
>
>> Where do I start troubleshooting?
>
> Start by making sure that these match:
>
> /etc/resolv.conf
> /var/spool/postfix/etc/resolv.conf
>
> When cli dns tools work, that usually means the first file above is
Y z put forth on 4/28/2010 1:36 AM:
> Where do I start troubleshooting?
Start by making sure that these match:
/etc/resolv.conf
/var/spool/postfix/etc/resolv.conf
When cli dns tools work, that usually means the first file above is correct,
fsvo "correct". When postfix can't resolve dns, it usu
