PFSense forwarder (dnsmasq) unusually slow

xrctp1

I have been experiencing 2-5s delays when resolving names using PFSense's forwarder. Is there some sort of tuning to fix this? I tested resolution from the pfsense box itself and got responses in milliseconds.

ihoman202

Same here, both unbound & dnsmasq are slow as a snail

johnpoz

Your going to have to actually give some details to work with here people!

Where are you forwarding too? What does a query direct to that look like from your client as far as time.. What does the query time look like from client to pfsense?

Example if your forwarding to 8.8.8.8

$ dig www.google.com @8.8.8.8

; <<>> DiG 9.14.1 <<>> www.google.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34825
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;www.google.com.                        IN      A

;; ANSWER SECTION:
www.google.com.         285     IN      A       216.58.192.132

;; Query time: 21 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sat May 18 15:49:17 Central Daylight Time 2019
;; MSG SIZE  rcvd: 59

Here is to unbound on pfsense.

$ dig www.google.com

; <<>> DiG 9.14.1 <<>> www.google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50496
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.google.com.                        IN      A

;; ANSWER SECTION:
www.google.com.         257     IN      A       172.217.6.100

;; Query time: 1 msec
;; SERVER: 192.168.3.10#53(192.168.3.10)
;; WHEN: Sat May 18 15:49:41 Central Daylight Time 2019
;; MSG SIZE  rcvd: 59