----------------------------------------
> 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 
>> domain, so it bounces them. Ouch.
>>
>>> ~$ /etc/init.d/postfix restart
>>>
>>
>>
>> Yup. Been starting and stopping for a while now. :-(
>>
>
> I had something similar a few days back, when - duh - all my incoming
> mail got stuck for the same reason. I knew about the two resolv.conf,
> but nothing helped.
> Then I tried some dig another.domain.com MX, and it timed out, while dig
> another.domain.com didn't. Once name resolution of MX was back, postfix
> was back after a restart. I dunno, if it was a bad coincidence, though I
> didn't like it all too much.
>
> Good luck,
>
> Uwe

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. Lack of sleep 
doesn't help. :-)


                                          
_________________________________________________________________
The New Busy is not the old busy. Search, chat and e-mail from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3

Reply via email to