DNS does not have a single time to propagate. You will hear 24-48 hours often quoted, which is a common setting, but you need to know the specifics of your DNS records before you make changes.
Each record in DNS has a TTL value, which lets parties know how long they can consider a resolution to be valid for.
fruitter.com. 21600 IN A 62.149.128.160 For fruitter.com, the A records have a TTL of 21600 seconds. This is 15 days. So anything that does a DNS query - including other DNS servers and hosts for fruitter.com do not need to, and should not, query the name servers for fruitter.com again until the 15 days has elapsed.
You can force a refresh on your host, by flushing DNS. You can clear the cache of your DNS server. These will get you a fresh up to date copy of the records. But this only affects what you control. Everyone else on the internet will be using the 15 day TTL.
So, if you are planning a change to anything that relies on DNS, your first step should be to understand the TTLs currently in place, and reduce them. Changing the TTL to 60 means that in 15 days time, you can make changes to DNS that will propagate inside a minute.
Of course, during this time, your DNS servers will see increased traffic, as the responses that are given are only valid for a minute, after which a new query to your servers must take place. So you need to plan for that too.
Finding a middle ground is the common approach. Reduce the TTL to the largest tolerable window depending on traffic and lookups. Make the change, then once the TTL has expired, change the TTL to something larger.
Some DNS providers, such as the one you are using, will set the TTLs very high by default to reduce the stress on their servers.
In some cases, DNS is used for high availability across sites, and so the TTLs are set as short as 15 seconds so that they can be quickly redirected to new IP addresses in response to outages. In these instances, large amounts of DNS queries are expected.