한메일이나 다른 큰 서비스 업체로 메일을 보내면 도착을 안합니다.
501.5.1.8 에러가 나고..
sender domain 어쩌구..-_-;
답변을 얻긴 했는데..
제가 dns는 잘 몰라서 도움이 필요하군요..
어떻게 해결해야 할지 도와주세요...ㅠ.ㅠ...
그럼..
-----------------------------------------------------------
"dalbong2" <webmaster at adfinder.co.kr> wrote:
>hi,all.
>I have a problem managing a mail server..
>1/3 of mails are keep returning with these messages..
>------------------------------
>501 5.1.8 ... while talking to mx2.hanmail.net.:
>>>> MAIL From:<root at zzang.adfinder.co.kr> SIZE=6365
><<< 501 5.1.8 <root at zzang.adfinder.co.kr>... Sender domain must exist
>501 sinkeeru at hanmail.net... Data format error
>I asked this question before and got an answer by 'Neil W Rickert'.
>He/she..:-) said..
>-------------
>>---------------
>That is a DNS problem. Fix your broken DNS nameservers.
>According to my lookup, the two official nameservers for this
>hostname are:
>;; AUTHORITY SECTION:
>adfinder.co.kr. 2H IN NS ns.netcubic.co.kr.
>adfinder.co.kr. 2H IN NS ns2.netcubic.co.kr.
>;; ADDITIONAL SECTION:
>ns.netcubic.co.kr. 2H IN A 211.36.0.22
>ns2.netcubic.co.kr. 2H IN A 211.36.0.23
>The first of these returns an address for zzang.adfinder.co.kr, while
>the second says that zzang.adfinder.co.kr does not exist.
> -NWR
>---------------
>Problems are..
>I changed DNS servers and still, the problems are keep bugging me..
>Can anyone give me some help..? :-(
You still have the same problem with DNS.
The DNS servers for KR. are listed as
;; AUTHORITY SECTION:
kr. 4D IN NS ns.krnic.net.
kr. 4D IN NS ns.kornet.ne.kr.
kr. 4D IN NS ns.kreonet.re.kr.
kr. 4D IN NS ns.kren.ne.kr.
kr. 4D IN NS ns2.internic.net.
kr. 4D IN NS ns.ripe.net.
Based on the SOA record, the first of these is the primary
server for KR.
It is listing your dns servers as
adfinder.co.kr. 2H IN NS ns.netcubic.co.kr.
adfinder.co.kr. 2H IN NS ns2.netcubic.co.kr.
adfinder.co.kr. 2H IN NS ns1.jdns.net.
adfinder.co.kr. 2H IN NS ns2.jdns.net.
However, other DNS servers for KR. disagree about this.
The current SOA serial number for the KR. zone is
1999122915
That looks suspiciously like a date in 1999. I can't be sure of
that. But that, together with the inconsistency of data, suggests
that the KR nameservers are not well managed.
I don't know how to solve that problem. That is a problem you have
to work out how to solve.
-NWR