RiotGames / developer-relations

Riot Games Developer Ecosystem Bug Reporting
http://developer.riotgames.com
744 stars 44 forks source link

[BUG] DNS is returning "No such name" for the NA spectator server #686

Closed uncgopher closed 2 years ago

uncgopher commented 2 years ago

Bug Description
When attempting to spectate a game on the NA server using the command line prompt, the game fails to load (stuck at a black screen). Currently all other regions work using this method. If I spectate a friend playing on the NA server by using the client, the spectator mode correctly launches without issue.

Problem Description
It appears there is an issue with the DNS that the command prompt triggers. When running Wireshark, there's a failed DNS call to "spectator.na.lol.riotgames.com" with the error message "No such name".

Expected Result
The NA spectator command should work correctly, just like the other regions.

Actual Result
The NA spectator command does not launch the spectator client.

Developer Impact
This is preventing any spectating of pros visiting NA for Worlds 2022 when they are playing in solo queue.

Edited to add more explicit steps to reproduce

uncgopher commented 2 years ago

Looks like it's a new URL, replacing the old address with "spectator-consumer.na1.lol.pvp.net" launches the spectator client correctly, e.g. cd "C:\Riot Games\League of Legends\Game\" & "League of Legends.exe" "spectator spectator-consumer.na1.lol.pvp.net:80 cK2hxUNCv07nRQRu6AxZrO39wO9bvg4S 4447670607 NA1" "-UseRads"