As far as I see there's no PTR record for your new IP address yet:
mh1:~# dig -x 184.108.40.206
; <<>> DiG 9.2.1 <<>> -x 220.127.116.11
;; 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:
;18.104.22.168.in-addr.arpa. IN PTR
;; ANSWER SECTION:
22.214.171.124.in-addr.arpa. 86400 IN PTR control.virtualbizpark.com.
;; Query time: 25 msec
;; SERVER: 126.96.36.199#53(188.8.131.52)
;; 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.