Server move - all working except inbound email

Discussion in 'Installation/Configuration' started by smackYYZ, Jan 16, 2007.

  1. smackYYZ

    smackYYZ New Member

    I moved my servers to a new colocation, I changed IP numbers both throught the admin pages and also via phpMyAdmin.

    DNS not done on ispconfig box is done by third party, and was updated.

    To date everything is working fine except inbound email. See maillog sample:

    Jan 16 10:22:35 mail postfix/qmgr[4037]: 029071C071D: to=<[email protected]>, orig_to=<[email protected]>, relay=none, delay=1, status=deferred (delivery temporarily suspended: connect to ip-208-67-219-40.n.opendns.com[208.67.219.40]: Connection timed out)


    Any ideas/insight would be appreciated.

    Mike
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Is this "ip-208-67-219-40.n.opendns.com" the new hostname or the old hostname?
     
  3. smackYYZ

    smackYYZ New Member

    till,

    It is neither my new or old hostname. The hostname has not changed, just it's IP address. That appears to be a resolved name from a DNS server.

    I've not yet published a reverse DNS for this server. hmmmm

    But if I do :
    host 64.34.158.169

    I get:
    169.158.34.64.in-addr.arpa domain name pointer control.virtualbizpark.com

    which looks right.

    Any other ideas?
     
  4. falko

    falko Super Moderator Howtoforge Staff

    As far as I see there's no PTR record for your new IP address yet:

    Code:
    mh1:~# dig -x 64.34.158.169
    
    ; <<>> DiG 9.2.1 <<>> -x 64.34.158.169
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32760
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
    
    ;; QUESTION SECTION:
    ;169.158.34.64.in-addr.arpa.    IN      PTR
    
    ;; ANSWER SECTION:
    169.158.34.64.in-addr.arpa. 86400 IN    PTR     control.virtualbizpark.com.
    
    ;; Query time: 25 msec
    ;; SERVER: 213.191.92.84#53(213.191.92.84)
    ;; WHEN: Wed Jan 17 19:09:41 2007
    ;; MSG SIZE  rcvd: 84
    But I think your error is caused by DNS not being updated fast enough. DNS changes can take up to 72 hours until they are propagated, so maybe you might have to wait a little bit longer.
     

Share This Page