If the ping and traceroute test show your server with us in the outcome, you know the DNS is propagated. You can try speeding up the propagation time by having your TTL set to a lower number (not recommended). We set the default TTL to 14400 (4 hours); however the network that you are using to access the internet may update at a slower rate.You can try Clearing your DNS cache or "Hello siva, and thanks for the comment.I do not understand what I need to check, as I have never had this problem.
I am clueless as to why this is happening because using another registrar I have successfully updated DNS records for other clients which all point to the new server correctly.
I'm afraid that you're going to have to approach this from the client end.
Changing the timeouts is only going to help clients the next time they check in, which is usually after half the existing lease time, or sometimes during boot.
If I am not able to solve the problem using advice I will provide the IP/domain name here.
The most likely reason for this is that the serial number on the zone hasn't been changed - so the previous entry is being cached.