This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Firefox takes a long time to resolve first website, but is fine after that

  • 1 baphendule
  • 0 zinale nkinga
  • 1 view
  • Igcine ukuphendulwa ngu billeverhart

more options

We are using firefox on Redhat 7 workstations and, when we first open firefox and attempt to load a web address it takes 25-30 seconds to connect.

After that first attempt, web addresses load almost instantly.

Our systems are only connected to a local network and not the internet, if that makes a difference. Also, we are using web addresses and not IP addresses. When I try by Ip address it's much faster, but I get the security risk warning for the ssl cert. So I'm not sure if my issue is something between firefox and dns, or if it has to do with the SSL certs? Both dns and ssl are handled by Red Hat IDM.

We are seeing the same behavior on all of our workstations.

We are using firefox on Redhat 7 workstations and, when we first open firefox and attempt to load a web address it takes 25-30 seconds to connect. After that first attempt, web addresses load almost instantly. Our systems are only connected to a local network and not the internet, if that makes a difference. Also, we are using web addresses and not IP addresses. When I try by Ip address it's much faster, but I get the security risk warning for the ssl cert. So I'm not sure if my issue is something between firefox and dns, or if it has to do with the SSL certs? Both dns and ssl are handled by Red Hat IDM. We are seeing the same behavior on all of our workstations.

Okulungisiwe ngu billeverhart

All Replies (1)

more options

I noticed today that if I start firefox with --safe-mode the issue goes away.