This is only part of it. As Netlify operates a global CDN, the node closest to visitor (or the IP of the network that person it connected to) will serve the site. These IPs will change too. If you look at the following
% dig www.renegademma.com.au A +noall +answer
; <<>> DiG 9.10.6 <<>> www.renegademma.com.au A +noall +answer
;; global options: +cmd
www.renegademma.com.au. 20 IN A 54.206.231.79
www.renegademma.com.au. 20 IN A 54.206.202.192
the value 20 is the TTL. In 20 seconds, these records will change. And here is what they look like 20 seconds later…
% dig www.renegademma.com.au A +noall +answer
; <<>> DiG 9.10.6 <<>> www.renegademma.com.au A +noall +answer
;; global options: +cmd
www.renegademma.com.au. 20 IN A 54.253.175.63
www.renegademma.com.au. 20 IN A 54.206.231.79
Check out [Support Guide] How are requests routed to the nearest Netlify CDN node? for more details on this.
So if you add a A record pointing to one of Netlify’s IPs, only that IP will serve the site regardless of where the visitor is. This is, to say the least, sub-optimal.