Docker - Returning Loopback Address

I git-cloned the master (at commit 42a1650d3146e025d996ce5b9b5dfbd9bd8fbe88) then ran through the documented Docker build steps, exposed the ports, etc. However, even after updating realmlist to use my DNS entry, the packet-capture still shows that it's trying to connect via the loopback.

Am I missing something here? I'm substituting my DNS entries below... but they resolve to the correct external IP and aren't in any hosts files. Port 8085 also is reachable from my test client (verified via telnet)

mysql> select * from realmlist\G
*************************** 1. row ***************************
                  id: 1
                name: BB Home
             address: boonebytes.example.internet.accessible
        localAddress: 127.0.0.1
     localSubnetMask: 255.255.255.0
                port: 8085
                icon: 0
                flag: 0
            timezone: 1
allowedSecurityLevel: 0
          population: 0
           gamebuild: 12340 1 row in set (0.00 sec)

Auth Server log-tail (recognizes DNS entry):

Updating Auth database...
>> Auth database is up-to-date! Containing 1 new and 35 archived updates.

Started auth database connection pool.
Loading IP Location Database...

Added realm "BB Home" at boonebytes.example.internet.accessible:8085.
Ping MySQL to keep connection alive

World Server log-tail:

AzerothCore rev. unknown 1970-01-01 00:00:00 +0000 (Archived branch)
(Unix, RelWithDebInfo, Static) (worldserver-daemon) ready...
Starting up Auction House Listing thread...
Calendar deletion of old events.
AC> Update time diff: 2. Players online: 0.
Update time diff: 1. Players online: 0.

Wireshark screenshot attached from the Realmlist response packet, indicating the loopback is being sent to the client (accessing across the internet, no VPN). The Wireshark capture does not show any attempts by the client to connect to the server on 8085; just 3724.

Thanks in advance!

I found the solution to my issue. Posting here in case others run into the same issue. Sorry in advance for missing the commands; I had rebuilt the images a few times until I realized what had happened.

• The docker containers were asking the host for DNS lookups.
• The new CNAME entry I added externally resolved to an A record that was overridden in my internal DNS server.
• Example: "games.example.com" was a CNAME to "myserver.example.com". MyServer would resolve to an external IP if queried from the internet, but the internal DNS server resolved it to 127.0.0.1 (to keep internal traffic from hitting the internet).
• It didn't completely register with me that the server would do the DNS resolution locally and only send the IP to the client.
• Specifying the external IP in the realmlist table (instead of just the DNS record) was the trick. Alternatively, I probably could've also added a Type A DNS for "games.example.com" to resolve to the external IP as well.

Additional troubleshooting tip: Consider installing DNS utilities on the Auth Server, and run a DNS lookup directly from that container for the domain you're specifying in your realmlist.

Hope this helps!