05-17-2018 11:47 AM
My customer has reported ISE making a DNS query every time it sends a syslog. Doesn't seem desirable behavior, is this normal behavior or should I request they open a TAC case?
It looks like ISE makes a DNS query for the syslog server prior to every syslog message. In our environment, it looks like that means a new DNS request every 0.1 seconds from each server. This is despite the DNS TTL for our syslog server being 900 seconds
We'd probably prefer ISE to respect the DNS TTL (or at least something resembling it).
Solved! Go to Solution.
06-03-2022 05:18 AM
I understand that you can configure ISE to keep a DNS cache using the command "service cache enable hosts ttl [ttl in seconds]". Trying this myself.
05-17-2018 03:17 PM
Hi John,
Let me do some research internally & respond to you. If the customer can't wait, please request them to open a TAC case.
- Krish
05-18-2018 08:57 AM
Hi John,
I consulted the DNS RFC & it says resource record 'may be cached' (read it as optionally cached) for the TTL time interval. So even if ISE is not honoring TTL, it is not a standard violation.
Is it possible for your customer to try a couple of options - try a different DNS and/or add a static host entry to see if there is any change. If your customer wants to pursue this further, please request them to open a TAC case.
- Krish
05-24-2018 12:45 PM
So you confirm that ISE performs a DNS query prior to sending each syslog message?
06-03-2022 05:18 AM
I understand that you can configure ISE to keep a DNS cache using the command "service cache enable hosts ttl [ttl in seconds]". Trying this myself.
06-03-2022 02:27 PM
Hi @stefan.tabell ,
yes, but if I'm not mistake, this command (ise/admin(config)# service cache enable ...) is an option on ISE 2.7P3+.
Regards
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide