DNS based rules requirements
-
Drools with Envy over @jimp lab...
While I don't have the lab jim has - I also have never seen this on multiple netgate appliances nor VMs.. I also on purpose put in an alias on my 2.4.4 to resolve with filterdns and not seeing any issues.
-
@johnpoz said in DNS based rules requirements:
Drools with Envy over @jimp lab...
-
Thanks for the help @jimp, you might be onto something with the shellcmd entries. I use a shellcmd to kick off a python script that stays running as a service.
python2 /usr/local/customscript/server.py
I ended up having to put this in the /usr/local/etc/rc.d folder
Sorry for filing the bug, I figured that I was seeing it across so many systems that it was a core issue and not a shellcmd entry.
-
Hi!
Me too. hostnames in alias doens't resolve, everything else does and dns is running.
I don't have any customization like that. Anyway to troubleshoot this? -
Do you see filterdns running per the command above?
-
Fyi, I didn't see it running on my systems at boot until after I edited and saved a firewall rule.
-
Well its not going to run unless you have an alias setup that needs to be resolved.
-
I meant I had rules set up than needed filterdns to run. But when I checked at CLI the process wasn't running until I edited and saved a rule with an alias in it. Then like 30 seconds later filterdns was running
-
Had just converted my alias to IP just to get it working. Converted one back to hostname now.
It looks like it running now.[2.4.4-RELEASE][admin@fw.*******]/root: ps -ax | grep filterdns 91818 - Is 0:00.45 /usr/local/sbin/filterdns -p /var/run/filterdns.pid -i 300 -c /var/etc/filterdns.conf -d 1 99513 0 S+ 0:00.00 grep filterdns
Can I check if it resolves? Right now the alias I use probably has states open (external backup coming in so can't kill states right now)
-
You can check the contents of the alias at Diagnostics > Tables.