Project

General

Profile

Bug #1407

GUI is sluggish without working DNS

Added by Jim Pingle over 8 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
Web Interface
Target version:
Start date:
04/02/2011
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.0
Affected Architecture:
All

Description

If you don't have functional DNS, the GUI can be extremely sluggish.

Common scenario to reproduce:
  • Multi-WAN setup where for whatever reason all DNS servers are going over the WAN that is down (in my case is was my cable provider handing out 8.8.8.8 as a DHCP DNS server when I had it set for a static route over DSL...)
  • If the WAN with DNS is down, navigating the GUI is quite slow.
  • Fix DNS and it's back to being speedy

Associated revisions

Revision 6265b041 (diff)
Added by Ermal Luçi about 8 years ago

Tell the local system to use the locally running dns forwarder as a primary source. This should help ticket #1407

Revision 8ac329da (diff)
Added by Ermal Luçi about 8 years ago

Tell the local system to use the locally running dns forwarder as a primary source. This should help ticket #1407

History

#1 Updated by Ermal Luçi over 8 years ago

  • Status changed from New to Feedback

Can you try a snapshot from tomorrow.
I fixed #1410 and that would fix this as well.

#2 Updated by Jim Pingle over 8 years ago

  • Status changed from Feedback to New

That may help with multi-wan, but doesn't help the case when there is only one WAN, or all WANs are down.

#3 Updated by Chris Buechler about 8 years ago

  • Priority changed from Normal to High

still hit this and it creates major issues with trying to operate or troubleshoot the system when there's no Internet.

#4 Updated by Ermal Luçi about 8 years ago

Can you check if /etc/resolv.conf has any entry during this time?

#5 Updated by Chris Buechler about 8 years ago

resolv.conf was populated in this case.

This instance was exacerbated by AutoConfigBackup so it was even worse than usual. I'll create a separate ticket for that

#6 Updated by Ermal Luçi about 8 years ago

Does it happen if resolv.conf has an entry
'options timeout:1'
'options attempts:1'

#7 Updated by Ermal Luçi about 8 years ago

  • Status changed from New to Feedback

Please test latest snapshots fixes have been pushed there.

#8 Updated by Peter Baumann about 8 years ago

Hi all,

I just tested successfull with the following snapshot:
2.0-RC3 (amd64)
built on Mon Aug 15 22:32:41 EDT 2011

What I did:
- removed every dns server entry > webgui response is normal.
disabled internet link so no dns server reachable -> webgui response is normal.

So, I think this is working now.

Peter

#9 Updated by Ermal Luçi about 8 years ago

  • Status changed from Feedback to Resolved

When having localhost as a first server in resolv.conf, as is done on latest snapshots, this bug does not manifest.
So basically this is related to the resolver library timeouts.

The workaround works for now and there are very rare occasions when a forwarder is not running on pfSense itself.

Also available in: Atom PDF