DNS Resolver…I think?

  • Sorry, I'm still rater new to networking, I don't know if it's Resolver, Forwarder, or other. I'm hopping that people that know this a lot more than me can help fix this.

    Per NameBench:

    IP                    Descr.                            Hostname                                    Avg (ms)    Diff            Min          Max            TO    NX    pfSense                        router.imwac.co                            143.49                      2.0          1591.4            0    0    Comcast Chicago US    cns.area4.il.chicago.comcast.net    50.73    182.8%    16.7            341.1            0    0

    Comcast Chicago US is 182.8% Faster than your current primary DNS server (pfSense)

    I used the settings from a video that I can't find now. The idea was to have pfSense cache the DNS for 24hr. Now it's taking 3x longer than the DNS 200mi (320 km) away.

  • What version of pfSense are you using?  Are you using the DNS Forwarder or the DNS Resolver?  Default TTL on both is 1 day, I believe, so any lookups will be cached for that long.  Are you testing from WAN or LAN?

  • What version of pfSense are you using? 2.3.1-RELEASE-p1 (amd64) built on Wed May 25 14:53:06 CDT 2016 FreeBSD 10.3-RELEASE-p3 (but looks like there's an update available)

    Are you using the DNS Forwarder or the DNS Resolver?  Resolver I think. I don't remember messing with the forwarder settings, and it's not turn on with the check mark. But there were a few pages that I changed settings for.

    Are you testing from WAN or LAN? LAN side, my main system.

  • Any DNS server with a large cache from hundreds of thousands or millions of users will respond faster than your own system doing recursion, unless you also have a huge number of clients.

    Enabling forwarding mode in Unbound will let you take advantage of the cache of some other DNS server, either Comcast's or Google public DNS will end up being similarly fast in that case.

Log in to reply