All DNS lookups extremely slow
-
nslookup will use what 'system' (PC) uses.
An application like Firefox, out of the box, will completely bypass the system DNS, and goes directly to the outside DoH server, doing its DoH thing. The pfSense resolver will never see the requests. -
@jrey said in All DNS lookups extremely slow:
did I miss something on here?
you don't need to adjust those to be honest, the defaults should be fine.. And that sure has nothing to do with whatever issue your having.
-
did I miss something on here?
My question was more about the OP stated changing them in reference to something said "on here".
the defaults should be fine
I'm 100% in agreement with this
-
@jrey said in All DNS lookups extremely slow:
reference to something said "on here".
No idea where he would of seen that - I have sure never stated anything of the sort. And don't recall any one saying it, if I would of seen it I would of questioned it.
-
@johnpoz
The pfsense vm is running 2.6.0 right now and its on ESXi 6.0 which will be updated to the most recent patch for esxi 6.0 this week. The pfsense vm also has the vmxnet3 nic's which I know usually work better than the e1000. I have to get the firmware/bios updated on the host and then I plan to patch. I know the host is running extremely old esxi software but they have to continue to keep 4 NT4 servers running for their manufacturing.I think the settings I found for adjusting things under Advanced Settings were from another support forum. I mistakenly lumped them with the suggestions I got from this group, sorry about doing that.
Anyone else have any ideas after updating the host and the pfsense version to 2.7.2 so they are running current software
I also changed all of my advanced settings back to the defaults for the DB size and the number of entries in the DB.
-
@rollin1 bumping those settings to those values - you must be handling a shit ton of dns to a bunch of different clients all going to lots of different places ;)
If I had a need for dns that those settings would make sense, prob wouldn't be running it on my router ;) And would have a dedicated NS properly sized for my needs.
-
@johnpoz
Those settings were never something I adjusted in any other pfsense install that I have done but the latency is too significant to not notice. What do you think if I change all the settings to forward vs look everything up? I have honestly wondered through out this whole issue if the problem could be with the vm itself. I mean after the DNSSEC settings were changed the lookup times improved but they are definitely not normal. What do you think about the following steps- Update ESXI 6 - Client has been running esxi 6 with no patches for a while
A. Once patched to most recent patch for ESXi 6 I can then deploy a fresh 2.7.2 pfsense vm
B. After patches the new 2.7.2 pfsense vm will actually run and not power off
C. Import the clients config on the new vm and see how everything runs
Does anyone see any issue with doing this? I basically want to rule out anything with the existing pfsense vm and their configuration is very basic (no vpn's, no complex network)
- Update ESXI 6 - Client has been running esxi 6 with no patches for a while
-
@rollin1 I moved away from running pfsense on esxi many years ago - It did have some advantages, but also drawbacks.. I have seen issues where user having performance issues.. But haven't paid much attention to them since not currently running on esxi.
But isn't esxi 6 eol? Like last year??
Isn't 8 current?
-
@johnpoz
The most current version is 8 yes. They have 4 vm's that are NT4 which is extremely old and they machines are slated to be retired in 2024 so the vm's have to stay around until that time. Once I can retire those vm's I can upgrade their hosts to the most current version of ESXi 7. The servers are off on their own vlan and arent accessible from the workstation network so at least they are isolated from everything else. -
-
@johnpoz
Your telling me they are old. My immediate reaction was to tell them well when are we phasing these out? They are finally already in process to replace these machines finally.
