3600 IN A .64 25.0% of queries will be returned by .152 (dns2.freehostia.com) cc. Checking the above tests for your domain may give you some more clues as to where the source of the issue lies. try checking what are answers for dns queries from all responsible servers - visit for instance , type your domain name, select type: ANY and run the check.
Registries may protect their root nameservers from overuse by setting a high TTL of up to 48 hours or more for those NS records.Although we ensure 1 hour for A/AAAA/MX/TXT/CNAME-records and 48 hours for NS-records, it might take up to 72 hours until the settings are visible.If you change your domain name's nameservers, we submit your change request to the registry within minutes, and they publish your authoritative NS (nameserver) records within their root zone. For example, Veri Sign refreshes zones for domain names every three minutes.More specifically from your question it sounds to me like you authoritative name servers have not been updated (or are listed wrong so the wrong ones are being queried). The only time it should take more than the TTL to update would be if you're changing records with your registrar.Domain Name System (DNS) client computers can use dynamic update to register and dynamically update their resource records with a DNS server whenever changes occur.14400 IN A .113 25.0% of queries will be returned by .161 (ns2.softuff.com) cc. It sounds like the DNS server YOU are using is caching the old result. let us know what domain name you're having the issue with and I'm sure someone here will look into it for you and tell you if its propagated or not. One weekis more than enough time for any propagation to happen.