Similar issue to this
I'm working with a domain on a company we acquired xcitemedia.com.au hosted in Crazy Domains (soon to be migrated to Route53 which will likely resolve the issue?)
it has an existing wildcard *.xcitemedia.com.au IN A 188.8.131.52 (with a 14400 TTL which I've now set to 300)
I created connect.xcitemedia.com.au IN A 184.108.40.206 (~48 hrs ago)
This propagated pretty much everywhere worldwide in with 5-10 minutes.
My issue is 220.127.116.11 and 18.104.22.168 from "within Australia" are still caching incorrectly/resolve in wildcard IP and not seeing new A record
I have tested from my home in Melbourne, My Melbourne Office Melb and Brisbane office (all result in wildcard IP)
I have access to servers in the UK which resolve correctly when querying 22.214.171.124 and 126.96.36.199
Everywhere else is fine eg 188.8.131.52 and 184.108.40.206 including 220.127.116.11 from m the UK servers its just Australia!
the name servers respond correctly too .... ns1.syrahost.com ns2.syrahost.com
The 18.104.22.168 the digwebinterface.com is working too
nslookup -debug connect.xcitemedia.com.au 22.214.171.124
dig connect.xcitemedia.com.au @126.96.36.199
https://intodns.com/xcitemedia.com.au does show some errors but none that explain why 188.8.131.52 is working or not working based on GEO location.
I understand google DNS Server (184.108.40.206) uses Anycast so there are multiple of the same of the same IP around the world.
I even initiated a flush of A type with this tool.
Any help appreciated