A lot of Postfix hostname resolve warnings

Discussion in 'General' started by hubik.tomas, May 3, 2014.

  1. hubik.tomas

    hubik.tomas New Member

    Hello everyone,

    I have installed ISPConfig on my Debian server a couple of months ago. I followed this tutorial:
    http://www.howtoforge.com/perfect-se...ot-ispconfig-3

    I am using stable Debian Wheezy with all packages up to date with ISPConfig 3.0.5.4p1.

    When looking at logs, I see, that I have many warnings (tens per day) from Postfix similar to this one:
    Code:
    Apr 28 17:05:11 vps postfix/smtpd[1835]: warning: hostname mx1.allomone.com does not resolve to address 212.11.123.245
    I tried to run nslookup on my server to check what is happening. Here is the output:
    Code:
    Server:         8.8.8.8
    Address:        8.8.8.8#53
    
    Non-authoritative answer:
    mx1.allomone.com        canonical name = allomone.com.
    Name:   allomone.com
    Address: 46.36.35.141
    
    Ok, the IP address is indeed different. But when trying the same nslookup from another server with Google DNS, it returned correct IP 212.11.123.245.

    So I tried to run dig with the following output:
    Code:
    dig mx1.allomone.com
    
    ; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> mx1.allomone.com
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11972
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
    
    ;; QUESTION SECTION:
    ;mx1.allomone.com.              IN      A
    
    ;; ANSWER SECTION:
    mx1.allomone.com.       2246    IN      A       212.11.123.245
    
    ;; Query time: 109 msec
    ;; SERVER: 8.8.8.8#53(8.8.8.8)
    ;; WHEN: Sat May  3 01:10:05 2014
    ;; MSG SIZE  rcvd: 50
    
    I can see the correct IP. So I tried ping:
    Code:
    ping mx1.allomone.com
    
    PING mx1.allomone.com (212.11.123.245) 56(84) bytes of data.
    64 bytes from mx1.allomone.com (212.11.123.245): icmp_req=1 ttl=59 time=8.27 ms
    64 bytes from mx1.allomone.com (212.11.123.245): icmp_req=2 ttl=59 time=8.14 ms
    
    Again correct IP. Retried nslookup:

    Code:
    nslookup mx1.allomone.com
    
    Server:         8.8.8.8
    Address:        8.8.8.8#53
    
    Non-authoritative answer:
    Name:   mx1.allomone.com
    Address: 212.11.123.245
    
    Now the answer is different and containing the correct IP.

    Could anyone help me with resolving my issue? I have no complaints about errors when sending e-mails from the users. It seems like Postfix is working, but generating these warnings.

    Here are my configs:
    resolv.conf:
    Code:
    doamin mydomain.com
    search mydomain.com
    nameserver 8.8.8.8
    nameserver 8.8.4.4
    
    hosts:
    Code:
    127.0.0.1       localhost
    my.ip.addr.ess   server.mydomain.com
    
    # The following lines are desirable for IPv6 capable hosts
    ::1     localhost ip6-localhost ip6-loopback
    ff02::1 ip6-allnodes
    ff02::2 ip6-allrouters
    
    hosts.conf:
    Code:
    multi on
    Thank you very much for any advice.

    Tomas
     
  2. srijan

    srijan New Member HowtoForge Supporter

    Hi

    Please paste your out put of

     
  3. hubik.tomas

    hubik.tomas New Member

    Hello,

    here is an output of dig for mydomain.com:
    Code:
    ;; Truncated, retrying in TCP mode.
    
    ; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> mydomain.com ANY +noall +answer
    ;; global options: +cmd
    mydomain.com.              3557    IN      SOA     ns.forpsi.net. admin.forpsi.com. 2014040901 3600 1800 2592000 3600
    mydomain.com.              3557    IN      RRSIG   SOA 5 2 3600 20140509173417 20140409173417 55446 mydomain.com. UZN5lEvJN6gREr114hd69ATzbnJMa2KCSO4XnaA4qYjbxm6GiHV/+M8O bd0/JXdOtnV2NZpUWKMw1MCWlDnFgrtiEp+4EVC/Ye0Js5R+7XgfHXJY ofdzy7wnVptNLqQ3ZBW3Z791eO2Pw+r6ZbobOZXRFwmEdEqraj3oGTbZ n2U=
    mydomain.com.              3557    IN      DNSKEY  257 3 5 AwEAAaTq8L53p5a2eX9kUP8BJrv2L5eYocPphGZrSAJLQNL5lbwt+p8R wlioLd+4MHTIXsXb8LhsKQbYISYf04WWZLla2UXqBvw8NlWPrQfdplWk 6VGiEU0KNZcqwoFEHpg7X+qMlTE+BzxJetIZ54wfiVa4T34RrKzlvfFG peWPqMvz11jJupGjwATcEWtugsQxmQjvwBj22AnC8GFDThGvrh5Fw339 QNPD/bvn7w6BIr/JHWNZWlG78VDduRuhoUuS+tyFae4ZDeFoy+b7qFPa glQgGHi8o8zuQtd/X9ZMo0tHaZWD5IP5bANE3AWV2APVb8HFaw3fu2Jf LlmWoGWYNk8=
    mydomain.com.              3557    IN      DNSKEY  256 3 5 AwEAAc+5KVkN6Ft7I8n45NpU77T4w2RlqA8iTJz/MjHl0507gEXkM8ZM n2UN2tluRc1w2qH1fN/Fg91vw5g2G8B96baldUsH9kWmS76TgTvGndrn wUgtagcK8M0cb6S3aseI7WTWg1WD3Zrb4XPMYGAWO9OH9LxRIJ62G33H iCD/lMXj
    mydomain.com.              3557    IN      RRSIG   DNSKEY 5 2 3600 20140509173417 20140409173417 57937 mydomain.com. GURzjRgjh5yx6ivuQdvLDTOpfTRzvrhfXOvIGvFNSg/zAphBGdBzIjTA l8RI3idqrPifUqStThGQKMdidWcDlbmzWKG0nZJgTNeYuTUsJeiWFuzd YoKnR3gx/qRvPHWGFwYfKP6HhaiEV9YOCouvzp0mhpwX0TGUIYHJvZMe dAnyhZSZqOz1XkG2tDuXkt0eidfdoG4tvGl0cRI3Cuh3fCstCbSxc3Bp 9pmAjryv6woIqzZqLEsSTCS8QLr3TRL5hg/wkjtYsDd1rdJz63mJJYI9 lLqs9+nc3S2imEgOQ3/i7PLdSTs9WmDfPDbeZW4b45GYSOEWbAvImlTu PIeDXw==
    mydomain.com.              3557    IN      RRSIG   DNSKEY 5 2 3600 20140509173417 20140409173417 55446 mydomain.com. D+FKgI8HtPzVLgJQkhnFIiLRUBQ5U3tu00L4DY+YBVaOItFmNZx8nTX1 PLgE7y/TgQb/7Ksm9wOVn6k7Tl5Yal7gdAfw0LtgVJ7VtAnhKw7Mcs/p l6VqqtWCElWHogu84oQIzJHXdMrJqTKwq7jYcYBLhSSlRQ9MEOJAxNeL 6ik=
    mydomain.com.              3557    IN      NS      ns.forpsi.net.
    mydomain.com.              3557    IN      NS      ns.forpsi.it.
    mydomain.com.              3557    IN      NS      ns.forpsi.cz.
    mydomain.com.              3557    IN      RRSIG   NS 5 2 3600 20140509173417 20140409173417 55446 mydomain.com. Fr96xJQNceeBJJt6XR5uIbPvMNlKkoLX/CI/cwUV5rh3WzU1ydX34Gqv E2VCqS50+bghHuPyKHX3kLF+JrNPQiFG/0nk8TWrfpoQKy0bkBRh6xUp ivdEpINvsdY9rCf03jTyVW18CKGJACoGsoEDPJqemluWbW0ICI0bEGUk sQI=
    mydomain.com.              1757    IN      A       my.ip.addr.ess
    mydomain.com.              1757    IN      RRSIG   A 5 2 1800 20140509173417 20140409173417 55446 mydomain.com. RbF8RmD4yTePkTKrDKh5OGW6Tb4kyK/lgtNrsehzNiTu9lzAJPoU0llK DyAuymoMRM1IGoykP3CEpG4l7zoiqHTeH91cxTBQDYC/LsslH8wm5DnP rrHSRparyI3NRamwMrTKLvvo9NZRq13waVSjUBYlDGarx5gyEbMu3utJ Emo=
    mydomain.com.              1757    IN      MX      10 mail.mydomain.com.
    mydomain.com.              1757    IN      RRSIG   MX 5 2 1800 20140509173417 20140409173417 55446 mydomain.com. E0ym0pjSD3ftgG2N81/v1HCFoodAORZG+MdS+ncYfVANmSzfZBiqiNql bAyjpyg0GC5Lh8iZ6jqHsp7MzCrwS1lZctHjUAdTwvbSWosZ5fXlRjrV V5H1bpOdjZtw5uhCFqy8LD3dI+Gb4PQhsS7t9dU2JPh9UQ71HbI6tUqX /VM=
    mydomain.com.              1757    IN      TXT     "v=spf1 +a +mx ~all"
    mydomain.com.              1757    IN      RRSIG   TXT 5 2 1800 20140509173417 20140409173417 55446 mydomain.com. TXNZlxul48Rr3UGOJa3AviSZ6qvThh8aZqKpdjPxX3qIV2vfJJ0m+jVl iqLGoNF/ZWYjVViUfKXaNIXmkcNlGP9l6ceZ8VXUffZJy3xrhHTzw+dF ycQ056purm+10T3YQfSO4emvdadqMUgb/59bZ0DdZmiCbPcu1rP3yijx V9E=
    mydomain.com.              3557    IN      NSEC    *.mydomain.com. A NS SOA MX TXT RRSIG NSEC DNSKEY
    mydomain.com.              3557    IN      RRSIG   NSEC 5 2 3600 20140509173417 20140409173417 55446 mydomain.com. g9HOfkTE3zpaAvbZka5qUDhlzcenuZp/Sp2RCdZdtvdVuZy7TA/DLHEG kFOgCiUML51+UBTNyy2l7Oqr5nb58FSWjIZiP2zJdw3koi0qvhV7r9Mc 4WJDxZgCW5t9yKHKbAHQhKCWwsXaH0frtC0kVX7mQ2FkbNDrz3oRdsNM jmk=
    
    And here for server.mydomain.com:
    Code:
    ; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> server.mydomain.com ANY +noall +answer
    ;; global options: +cmd
    server.mydomain.com.          1799    IN      A       my.ip.addr.ess
    server.mydomain.com.          1799    IN      RRSIG   A 5 3 1800 20140509173417 20140409173417 55446 ibento.cz. L3U8L80znImrv6VJYn+GKOSlNJO+6XMtDxkvzSUd/yUW7m9TPql2eic3 Kw4Tb5LeroouQ9q51jXHT2aiKeOgMSWnMIE1J78Bw73LNvEhQ4DDozTb JS4N5heTemG33psME5S1JFVv6S0Wx6m/LZr2FUrlhDR/pI7y3xz8asiO rpU=
    server.mydomain.com.          3599    IN      NSEC    ibento.cz. A RRSIG NSEC
    server.mydomain.com.          3599    IN      RRSIG   NSEC 5 3 3600 20140509173417 20140409173417 55446 ibento.cz. d3rKdtlVervbvPEIh3Ywuibu29dQuJ/FuMGR6Y8opyIkYehlt9jy93fN lVCIK2vtaFmWbuuDrozlS28knfJBy1FCLayiEn3e4Pcg9kXNmd2krB/s WO/L+GkAI+sPmPUV0SPYn+aLoC8cny6yImMCdl44gjoOXqxI1AW2mM2X upY=
    
    Btw, the server from the warning in the previous post is not my server and I have a lot of different server names and IP addresses in the log. And another note, I am using different subdomains for SMTP, IMAP, POP3, etc as I have free certificates from StartSSL not allowing wildcards. You can see my MX record mail.mydomain.com. and mail.mydomain.com is pointing to the same IP address asi server.mydomain.com. But I do not know if it could be somehow related to the warnings.

    PS: I masked my IP address with my.ip.addr.ess

    Thank you very much

    Tomas
     
    Last edited: May 5, 2014
  4. hubik.tomas

    hubik.tomas New Member

    And one more thought:

    I tried to nslookup the "incorrect" IP from the first nslookup output as I was wondering how this IP showed here and I got this answer:

    Code:
    nslookup 46.36.35.141
    
    Server:         8.8.8.8
    Address:        8.8.8.8#53
    
    Non-authoritative answer:
    141.35.36.46.in-addr.arpa       name = eam.securitynet.cz.
    Authoritative answers can be found from:
    
    And dig:
    Code:
    dig 46.36.35.141
    
    ; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> 46.36.35.141
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9223
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
    
    ;; QUESTION SECTION:
    ;46.36.35.141.                  IN      A
    
    ;; AUTHORITY SECTION:
    .                       1619    IN      SOA     a.root-servers.net. nstld.verisign-grs.com. 2014050500 1800 900 604800 86400
    
    ;; Query time: 12 msec
    ;; SERVER: 8.8.8.8#53(8.8.8.8)
    ;; WHEN: Mon May  5 11:11:57 2014
    ;; MSG SIZE  rcvd: 105
    
    Do not know if it can lead to some solution.

    Tomas
     
  5. hubik.tomas

    hubik.tomas New Member

    No ideas? :(

    I am a little bit desperate seeing my logs overflowing with these warnings where I do not know by which are they caused.

    Than you very much for any suggestions.

    Tomas
     
  6. hubik.tomas

    hubik.tomas New Member

    Really nobody knows what could cause these warnings?

    Thank you very much.

    Best regards
    Tomas
     
  7. hubik.tomas

    hubik.tomas New Member

    Still no ideas?

    Thank you.

    Tomas
     

Share This Page