Waiting for DNS records to update..
It's always a difficult choice; Do I work on something else or do I hope record will be updated in few minutes..

I always choose wrong, will keep you updated :p

Well... DNS record did actually update in okay-ish time, but then I spent all night debugging why something was not working instead of going to sleep :/

As @jespersh said.

@jespersh I guess this is the reason why sleep is useful.. I completely forgot about setting shorter TTL value.

@jespersh @Linux TTL has nothing to do with how long it takes to propagate across the global internet infrastructure. It depends on the location of the originating name servers, and where you / your clients are geographically expecting to see the domain mapping complete. Further apart (geographically) = typically longer wait times. I've seen the full "worst-case" 24-hour scenario a few times

@fullstackchris

Sorry, it has everything to do with it.
Otherwhise, time to change DNS provider

@Linux If you're a small fish, changing TTL will do little to nothing. You're at the mercy of nameservers updating their entries

Many large DNS providers have a lower DNS TTL.

Eg Query with SOA and look it up...

https://support.cloudflare.com/hc/...

Cloudflare DNS is 5 min.

What's true is that an ISP providers DNS can be very slow - but all large DNS providers have usually a very low TTL.

When you just need the server side to become "alive"…

It's minutes,, instant if you have an own nameserver and can flush.

With clients it's an entirely different thing, as said before, it can take a lot more.

But usually - if it's a new entry - negative TTL is lower than the regular TTL.

@IntrusionCM Yea I actually noticed that. My domains are at OVH and if I create a new entry it's available in minutes but it I update existing entry it takes a lot longer

@fullstackchris

And that why a lower TTL will help you in those cases. If not - you have something wrong with your SOA and/or auth nameservers