For others with issues, it appears that Godaddy has cut off DNS API access for those with less than 10 domain names. You may want to consider migrating to Cloudfare or another provider.

@Pipe said in PfSense com 2 LANS porém LAN 2 não navega: justamente pensando nisso, sobre o NAT. Se for permissão no Unbound, o teste abaixo Query refused, e não timeout no DNS. Testa isso por no prompt do CMD DOS, digite: nslookup (dê enter) terra.com.br (dê enter) exit E cole o output aqui por favor.

I submitted a few related bug reports and enhancement requests, in case anyone is going to track this or suggest solutions: https://redmine.pfsense.org/issues/15199 https://redmine.pfsense.org/issues/15200 https://redmine.pfsense.org/issues/15203 https://redmine.pfsense.org/issues/15209

@jhg what size screen are you using, or how small do you have your browser window set to?

@optimusprime pfSense as a software resolution, or boxed into devices like this are not to be compared with solutions from (example) Cisco solutions. Or Microsoft for that matter. If you look for 'certificates' or 'exams' then you probably won't find what you're looking for. @optimusprime said in pfSense Exam & Certification: At official netgate site Look at their other official site. And while you have Youtube open, tens of thousands of pretty good video's are available from other channels that tell you everything you need to know, and more, as the subject is just huge. edit : btw : I'm saying all this as this is what I think. I'm didn't 'look'. Maybe it actual exist, but not in my physical neighborhood, and I'm not planning a trip to the US so I can learn the official way how to analyze a NAT rule

@Gertjan Yessir, I have that package installed since I'm using shellcmd to work around another issue. Much easier than manually editing config.xml, and also much easier to see if/how earlyshellcmd/shellcmd is being used on an existing install.

@eiger3970-0 You are correct. The sentence "The Save as default button stores the current package settings a new default value for future use." is grammatically incorrect. The article "a" should be replaced with the preposition "as" to accurately convey the meaning.

Typo on host config on Pf2. Should be copy the RSA public key from Pf1…..not Pf2

This should be OK now if you try it again. The server-side redirects are back in place.

@pierrelyon Great tip! I find that there is a "recipe" titled "Recipe 9 - Isolate your IoT devices". I purchased the book on the strength of your recommendation.

I found my issue: the group membership attribute should be "memberOf" instead of member as posted by OP.