Nagios Support Forum

Solved! In case anyone else has this problem. Long story very short, I had previously tried to pair down the number of IP addresses that have tcp/53 access to our DNS Servers and went a bit too far and siphoned off something I shouldn't have. I had a few other issues crop up after the expiration timer hit which led me down this path.

Anyway, Verizon must be doing something in the DNS reverse lookup space that other carriers are not doing, as I only had this issue with Verizon. Once I sorted out the ruleset on both the firewall and the DNS server side, everything started working again.

Hope this helps!

aastaguy wrote:Solved! In case anyone else has this problem. Long story very short, I had previously tried to pair down the number of IP addresses that have tcp/53 access to our DNS Servers and went a bit too far and siphoned off something I shouldn't have. I had a few other issues crop up after the expiration timer hit which led me down this path.

Anyway, Verizon must be doing something in the DNS reverse lookup space that other carriers are not doing, as I only had this issue with Verizon. Once I sorted out the ruleset on both the firewall and the DNS server side, everything started working again.

Hope this helps!

Great!

Locking thread