Otto Rodusek wrote:

Joachim Schrod wrote:

...

Otto Rodusek wrote:

...

# hosts: files mdns4_minimal [NOTFOUND=return] dns

There are two possible remedies:

1) If you don't know what Zeroconf is and have no Apple system, remove the string "mdns4_minimal [NOTFOUND=return] " from the line above. I.e., leave only files and dns.

2) Otherwise, check that avahi is running.

Hi, Thanks for all the helpful hints - tried all of them but postfix/sendmail still can't send out any mail!! I'm a bit confused with this dns issue - mainly if I open firefox or konquer, I have no problems surfing the net - even zyppr does all the updates without complaint - seems that ONLY postfix is giving an issue. As Joachim mentioned I tried the host command with the following results:

bunyip:/etc # host gmail.com gmail.com has address 209.85.225.83 gmail.com has address 74.125.79.83 gmail.com has address 74.125.127.83 ;; connection timed out; no servers could be reached bunyip:/etc # host -t mx gmail.com ;; connection timed out; no servers could be reached bunyip:/etc #

This tells that name resolution works, but not mx lookups. Actually, since the first command also outputs a time-out message, this probably also gets no answer from the DNS server. This is not good as the dig command yesterday worked. Before we make postfix work, dig and host must return results. Without them working, postfix won't work at all. Step 1) dig @202.156.1.58 gmail.com mx does that output a result? => This is the most basic way to check of you can access your DNS server. Step 2) host -v -t mx gmail.com 202.156.1.58 how about this? => This is a weeny bit more high-level, but the server is still accessed directly, without system configuation. Step 3) Make a backup copy of nsswitch.conf. Edit it: only "files dns" shall remain on the hosts line. host -v -t mx gmail.com what's the result now? => This uses the system configuration. If step 3 didn't return a result, stop now and come back. Step 4) What is the output of rcnscd status It may tell "command not found", that's OK, too. If it tells "running", call "rcnscd restart". Step 5) Restart postfix; otherwise the changed nsswitch.conf will not be activated: rcpostfix restart Hopefully these steps give more information to locate the problem at your system. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org