Why Is Firefox and Edge So Slow After Changing DC Addresses, While Chrome Works Fine?

0
11
Asked By TechieNinja99 On

I've recently switched my domain controllers (DCs) from 192.168.x.x IP addresses to 172.x addresses. I've updated all references to the old IPs that I could think of, and the replication seems to be working without any errors. However, I'm experiencing slow webpage loading times in Edge and Firefox on various machines, even though they're on the same subnet. Strangely, Chrome works perfectly and loads pages instantly without any issues. The DCs can resolve their DNS forwarders, and I've also tested with different ones, plus they can reach all root DNS servers. I'm completely stumped and would appreciate any ideas or advice on what to look for. Thanks!

2 Answers

Answered By DevToolDude87 On

It could be useful to leverage the developer tools in both Edge and Firefox to get more insights into what's causing the slowdowns. This way, you can pinpoint where the lag is happening.

TechieNinja99 -

That sounds good! Can you give me specific steps on what to check for in the developer tools?

Answered By NetworkGuru21 On

You might want to check if Firefox and Edge are still trying to resolve the old DC addresses for DNS, while Chrome could be using DNS over HTTP and bypassing this issue. I'd suggest looking into your DHCP settings to see what DNS servers are being handed out.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.