Messaging Gateway

  • Private Community
 View Only

  • 1.  DNS lookup problem

    Posted Apr 02, 2012 12:56 PM

    Hi

    I have two machines, one running as control center/scanner and the other only scanner.

    After my 9.5.3.3 update I have noticed dns problem with control center server.

    When I run a MX lookup using web or CLI I receive a uncompleted result:

    nslookup -querytype=mx enkoping.se
    Server:         127.0.0.1
    Address:        127.0.0.1#53

    Non-authoritative answer:
    enkoping.se     mail exchanger = 20 inkorg2.enkoping.se.
    enkoping.se     mail exchanger = 10 inkorg1.enkoping.se.

    Authoritative answers can be found from:

    If I check from my scanner I receive a correct result.

    I can ping dns server from control center server.
    I have checked all DNS settings and I have flushed dns too.

    Edit: i notice this problem also on scanner server too now.

    //Peter



  • 2.  RE: DNS lookup problem

    Broadcom Employee
    Posted Apr 02, 2012 04:07 PM

    Can you please explain how this is an incomplete result? I do not understand how this is an issue. What problem does it cause?



  • 3.  RE: DNS lookup problem

    Posted Apr 03, 2012 02:35 AM

    I receive "MX-servers not found" errors on mail.

    If I run this on the scanner server I receive a more complete result:

    nslookup -querytype=mx enkoping.se

     

    Server:         127.0.0.1
    Address:        127.0.0.1#53
     
    Non-authoritative answer:
    enkoping.se     mail exchanger = 20 inkorg2.enkoping.se.
    enkoping.se     mail exchanger = 10 inkorg1.enkoping.se.
     
    Authoritative answers can be found from:
    enkoping.se     nameserver = dns1.enkoping.se.
    enkoping.se     nameserver = enkkomdns.lidnet.net.
    inkorg1.enkoping.se     internet address = 89.243.99.210
    inkorg2.enkoping.se     internet address = 219.99.56.2
    dns1.enkoping.se        internet address = 89.243.99.194
    enkkomdns.lidnet.net    internet address = 219.112.99.131
     

    And why has the DNS request been send to 127.0.0.1 and not to the default dns server?

    Is there a way to debug DNS lookups?



  • 4.  RE: DNS lookup problem

    Broadcom Employee
    Posted Apr 03, 2012 11:46 AM

    This is how the Messaging Gateway performs DNS lookups. Can you post the exact error message you are seeing? I am going to guess that it is 'No MXs for this domain can be reached' which means we could not contact any of the servers that an MX query returned.