How DNS works with load balancer in picture?

Stumbled upon an article explaining DNS Load Balancing and i got confused.

DNS load balancing enables the authoritative server to return different IP addresses of a certain domain to the clients. Every time it receives a query for an IP, it returns a list of IP addresses of a domain to the client.

With every request, the authoritative server changes the order of the IP addresses in the list in a round-robin fashion.

As the client receives the list, it sends out a request to the first IP address on the list to fetch the data from the website. The reason for returning a list of IP addresses to the client is to enable it to use other IP addresses in the list in case the first doesn’t return a response within a stipulated time.

When another client sends out a request for an IP address to the authoritative server, it re-orders the list and puts another IP address on the top of the list following the round-robin algorithm.

From the explaination above, i will imagine that Authoritative server will have to first fire a request to Load Balancer in order to know which app servers are in service, which then forward the list back to client browser.

Prior to this, i was having the impression that Authoritative server will only has the location of my load balancer, client browser will then send the request to load balancer, and then load balancer only take care on how to route the request being routed, all of these handled within load balancer itself, but clearly it conflicts with the article i've read. Wondering if any can shed some lights on this? And wondering if there is any way for us to verify all these by ourselves?