DnsResolve error

Help and Feedback Scripting Support
#1

I don’t know if this belongs here or in engine bugs or what not, but I seem to be getting these errors sometimes and losing connection to roblox servers (not being able to log in to studio, loading textures and stuff, loading stuff in games)

988×73 4.46 KB

It happened to lately and it happens a lot of times which is annoying, anyone know how I could counter-act this issue? It might be my connection to ROBLOX but I don’t know the troubleshooting steps.

4 Likes
#2

DNS related network errors could be at fault of your local network (PC, firewall, router, modem)

Try flushing your DNS on your PC and router and see if that helps. (Google steps to flush DNS)

4 Likes
#3

run ipconfig /flushdns in your cmd power shell

3 Likes
#4

i had the same problem, here are a few stuff i found out to try

  1. Reset the router
  2. Run cmd as admin and run "ipconfig /flushdns
  3. Allowed it thru firewall
  4. Tried re-installing roblox studio (i dont think it really helped much)
  5. After all that didnt work, i went in wi-fi configs and changed the dns settings to 8888 8844, i dont know how to explain it, but i watched the video linked below (it honestly helped me a lot)
1 Like
#5

For #5 from @JP_Pontes JP, he is suggesting to change your DNS server settings to use the Google DNS servers (8.8.8.8 and 8.8.4.4). \

It might be better to check with your ISP as to what DNS servers you should be using. If they are correct and you still get failures, then you might want to change them. There are risks with this as your ISP may have some form of location caching for services such as Netflix. Using Google DNS may send you to content servers further away and induce latency.

1 Like
#6

Im getting the same problem, couldnt open studio today (it was weird sinse days ago). The google server thing with 8888 8844 really solved it. Really weird though, that shouldnt happen.

Tried all the other steps before and didnt worked.

1 Like
#7

Same thing here, it started just this month for me, it’s weird, i dont want just to assume it’s a global issue, but i guess there is no way to know if the problem started in roblox studio or not