DNS Security

[Logesh]

Hi, 

We are getting warning message (Warning: No valid DNS Security License) when we commit every time. currently we are using PAN OS 9.0.5. Is it possible to disable this warning message.

Regards,

Logesh S.

[kiwi]

Hi @Logesh ,

At this time there's no way to suppress warning messages during commit.

Fix the warning 🙂

Or reach out to your local SE and have him add your vote to the existing feature request there is for this (FR ID: 2689 - Suppress Warnings in Commit)

Cheers,

-Kiwi.

[Logesh]

Thanks @kiwi, i will check the same.

[reaper · Accepted solution]

this means you enabled or changed the action on the 'palo alto networks dns security' option in DNS signatures of one or more of your spyware profiles

you should set it to 'allow' with no packetcapture if you do not have a license

[TomYoung]

You are THE MAN!  This answer should be marked as the solution.  I love clearing all commit errors.  It should be emphasized more in best practices.

[mlinsemier]

Just a quick update on this older topic that under PANOS 10.0.x, the DNS Sec license is now integrated in the policy and you can no longer make this change.  Additionally, you cannot change the built-in default policy either.  The kicker is that my Palo Alto account manager offered to sell me DNS Security licenses to get rid of the error and the TAC Engineer told me that its "cosmetic and just a warning" and to file a feature request through my account manager.  

I love when my security team sends me messages every day asking why where are warnings in Panorama about security policies being committed with warnings.  Hopefully as more of us move towards 10.0.x Palo Alto will do something about this.  It frustrating as this option shouldn't be configurable if we don't have a license.

-Matt

[crodrigueze]

Hi Matt, I have the same in PANOS 10 I deleted that warning deleting all botnet-domains, it works if you don't want use the sinkhole feature.

[fpadmin]

So we need to have a license now to utilize SinkHole? 

[mlinsemier]

Can you clarify a bit on what you deleted and where so I can review?  I'm not sure where you are seeing botnet-domains.

[ksauer507]

How do you get rid of this warning on PANOS 10.0.6?  Where do you delete all botnet-domains ?  I guess I can just import them via minemeld anyway?

[jesseivens]

I ran into this issue when I upgraded some VM-500s to 10.0.6.  I was able to clone the default spyware profile, which I named "default-no-dns-sec"  Then I went into CLI and issued the following commands to delete DNS specific items.

delete shared profiles spyware default-no-dns-sec botnet-domains lists default-paloalto-dns
delete shared profiles spyware default-no-dns-sec botnet-domains dns-security-categories pan-dns-sec-cc
delete shared profiles spyware default-no-dns-sec botnet-domains dns-security-categories pan-dns-sec-ddns
delete shared profiles spyware default-no-dns-sec botnet-domains dns-security-categories pan-dns-sec-grayware
delete shared profiles spyware default-no-dns-sec botnet-domains dns-security-categories pan-dns-sec-malware
delete shared profiles spyware default-no-dns-sec botnet-domains dns-security-categories pan-dns-sec-parked
delete shared profiles spyware default-no-dns-sec botnet-domains dns-security-categories pan-dns-sec-phishing
delete shared profiles spyware default-no-dns-sec botnet-domains dns-security-categories pan-dns-sec-proxy
delete shared profiles spyware default-no-dns-sec botnet-domains dns-security-categories pan-dns-sec-recent

On this firewall I have not "production" traffic yet, so I was able to disable all policies.  I enabled 1 with this new profile and pushed from Panorama.  No issues with the commit and no more warning.  All policies and/or Security Profile Groups will need to be updated to completely solve this.

I do have a TAC case open, so I am waiting for confirmation from TAC on this.

[mlinsemier]

Thanks for the update on this and I'm interested to hear what TAC replies with now.  It's kind of ridiculous that this is something that has to be done manually.

[jesseivens]

So far not much.  I am upgrading my PA3260s tonight from 9.1.9 to 10.0.6.  This is the same think I did on the VM500s.  I have also upgrade a VM100 and PA220, neither of which I had this problem.  Only issue was on the VM500s.  I ask TAC why this was and this is all I got back.  

It is a buggy behavior, I've been checking similar cases with the same issue, different platforms. Also on versions 10.0.5 and 10.0.6.
We don't have a root cause of the issue yet, but I'm glad the workaround worked for you.

I did do the workaround in Panorama on a shared profile, so it was only a 1 time change, since it is shared and I was able to push to all my different device groups at once.  I also took the opportunity change all policies to Security Profile Groups.  So if I need to change again, it is only a group change which affects all the policies that it is applied to.  Hoping that doesn't bite me down the road 🙂

[jesseivens]

Per my TAC case, Engineering had found that the issue is traced to a known issue PAN-164941 currently. The commits will retain the warnings but the commits will still go through and the issue will be resolved in Fixed Versions: 9.1.11, 10.0.8.  

My work around posted removed the warnings and no further issues on any of my models. 

[RPBagiyev]

Hi Reaper,

When I commit changes in Palo Alto (Software Version 10.0.6) I got a lot of warnings (No Valid DNS Security License).

In Objects > Security Profiles > Anti-Spyware there are 2 predefined profiles: default and strict.

I cloned strict profile. Changed Action to allow under Signature Policies, changed Policy Action to allow under DNS Policies, changed Sinkhole IPv4 to IPv4 Loopback IP (127.0.0.1). I did these things at different times. But it didn't help. I still got these warnings and its annoying. Could you show me exact place what to do?

P.S. I don't have a DNS Security license.