@johnpoz
Hello,
Yes, Running the dig command from my workstation does resolve with the output below. I am also running pfBlockerNG-devel. But I don't think it's blocking it because it happens for short periods of time and not as long as I have my blocked sites to be blocked for. This is also the case in Snort that I am running. It's blocking time period is longer than this time this seems to not resolve for. It's not happening 100% of the time. Are there logs that I should look at to see this error and check them against pfBlocker and Snort to verify? If so what Logs and where? I am new to dinging around in logs and how best to filter them.
dig abc.netgate.com
; <<>> DiG 9.18.18-0ubuntu0.22.04.2-Ubuntu <<>> abc.netgate.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 52553
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;abc.netgate.com. IN A
;; AUTHORITY SECTION:
netgate.com. 1432 IN SOA ns1.netgate.com. admin.netgate.com. 2024042005 3600 3600 604800 3600
;; Query time: 3280 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Sat Apr 20 11:27:19 CDT 2024
;; MSG SIZE rcvd: 90