نمایش نتایج: از شماره 1 تا 1 از مجموع 1

موضوع: مشکل در Reverse شدن External IP برای ارسال ایمیل به سایر میل سرورها در exchange 2010

  
  1. #1


    عضو عادی
    تاریخ عضویت
    Dec 2006
    نوشته
    69
    سپاسگزاری شده
    31
    سپاسگزاری کرده
    10

    مشکل در Reverse شدن External IP برای ارسال ایمیل به سایر میل سرورها در exchange 2010

    سلام
    تنظیمات مربوط به دامین External ام رو برای مخابرات که IP Valid رو از اونجا گرفتم فرستادم تا تنظیمات مربوط به Reverse Ip رو انجام بده، ولی مخابرات می گه Error های زیر مانع از تعریف Reverse IP می شه.
    از دوستان و اساتید کسی می تونه به من در این مورد کمک کنه. ممنون



    -----Original Message-----


    From: RIPE Database Administration local
    Sent: Sunday, July 06, 2014 11:54 AM
    To: ripe@dci.ir
    Subject: FAILED: reverse

    > From: <ripe@dci.ir>
    > Subject: reverse
    > Date: Sun, 06 Jul 2014 10:23:05 +0200
    > Reply-To: Javidi <ripe@dci.ir>
    > Message-ID: <31A6126BEC514100A0821816A0C5161A@cdit.ir>

    SUMMARY OF UPDATE:

    Number of objects found: 1
    Number of objects processed successfully: 0
    Create: 0
    Modify: 0
    Delete: 0
    No Operation: 0
    Number of objects processed with errors: 1
    Create: 1
    Modify: 0
    Delete: 0

    DETAILED EXPLANATION:

    **Warning: Invalid keyword(s) found: reverse
    **Warning: All keywords were ignored

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~
    The following object(s) were found to have ERRORS:

    ---
    Create FAILED: [domain] 140.38.78.in-addr.arpa

    domain: 140.38.78.in-addr.arpa
    descr: Reverse Delegation for university IP range.
    admin-c: MT7308-RIPE
    tech-c: MT7308-RIPE
    zone-c: MT7308-RIPE
    nserver: ir5.XXXXX.org
    nserver: ir6.XXXXX.org
    mnt-by: AS12880-MNT
    notify: javadashoaei@yahoo.com
    changed: ripe@dci.ir 20140706
    source: RIPE

    **Error: Superfluous name server listed at parent: ir5.XXXXX.org

    A name server listed at the parent, but not at the child, was
    found. This is most likely an administrative error. You should
    update the parent to match the name servers at the child as soon
    as
    possible.

    **Error: Superfluous name server listed at parent: ir6.XXXXX.org

    A name server listed at the parent, but not at the child, was
    found. This is most likely an administrative error. You should
    update the parent to match the name servers at the child as soon
    as
    possible.

    **Error: Total parent/child glue mismatch.

    The parent lists name servers that the child doesn't know about;
    see details in advanced. This configuration could actually work
    but
    breaks very easily if one of these zones changes slightly.

    **Error: Too few IPv4 name servers (1).

    Only one IPv4 name server was found for the zone. You should
    always
    have at least two IPv4 name servers for a zone to be able to
    handle
    transient connectivity problems.

    **Error: Name server IRw2.pouyasazan.org (94.232.174.176) does not answer
    queries over TCP.

    The name server failed to answer queries sent over TCP. This is
    probably due to the name server not correctly set up or due to
    misconfgured filtering in a firewall. It is a rather common
    misconception that DNS does not need TCP unless they provide
    zone
    transfers - perhaps the name server administrator is not aware
    that
    TCP usually is a requirement.

    **Error: Name server ir5.XXXXX.org (94.232.174.176) does not answer
    queries over TCP.

    The name server failed to answer queries sent over TCP. This is
    probably due to the name server not correctly set up or due to
    misconfgured filtering in a firewall. It is a rather common
    misconception that DNS does not need TCP unless they provide
    zone
    transfers - perhaps the name server administrator is not aware
    that
    TCP usually is a requirement.

    **Error: Name server ir6.XXXXX.org (94.232.174.176) does not answer
    queries over TCP.

    The name server failed to answer queries sent over TCP. This is
    probably due to the name server not correctly set up or due to
    misconfgured filtering in a firewall. It is a rather common
    misconception that DNS does not need TCP unless they provide
    zone
    transfers - perhaps the name server administrator is not aware
    that
    TCP usually is a requirement



    موضوعات مشابه:
    ویرایش توسط javad0062 : 2014-07-10 در ساعت 10:19 AM

کلمات کلیدی در جستجوها:

ripe xxxxx.com

برچسب برای این موضوع

مجوز های ارسال و ویرایش

  • شما نمی توانید موضوع جدید ارسال کنید
  • شما نمی توانید به پست ها پاسخ دهید
  • شما نمی توانید فایل پیوست ضمیمه کنید
  • شما نمی توانید پست های خود را ویرایش کنید
  •