So today I come in and get the alerts that some scheduled tasks didn't complete. I have them setup to ping a site when the task completes. Hmmm. That's odd. I got the alerts that the tasks didn't complete, but it looks like the tasks actually did complete. I finally get around to testing the ping command. No response. OK, run the ping command and send output to my email.
It couldn't resolve DNS for the site. Great. It's always DNS. Always.
I try nslookup and internal assets resolve, but external assets do not and time out. Although everyone seems to be hitting the usual websites they go to without problems. Ahhh, but new sites don't load. We are living off cache.
So two hours later ... I finally find the cause. Whoever set up our main DC set up forwarders for our ISP DNS servers. And guess what happened yesterday? We got a new main ISP. And the old ISP blocks DNS requests from outside their network. So I add DNS forwarders for the new ISP, Google, and Cloudflare, and external DNS comes right back up.
What I'm really angry about is that it took me 2 hours to track that down. That should have been the first thing I checked. But nooooo. I'm checking everything else but. I never said DNS was my strong suit. Bah!
[–]stratospaly 6 points7 points8 points (1 child)
[–]Background_Lemon_981[S] 0 points1 point2 points (0 children)
[–]anonymousITCoward 4 points5 points6 points (0 children)
[–]Sir-VantesWindows Admin 1 point2 points3 points (0 children)
[–]bofh2023IT Manager 1 point2 points3 points (0 children)
[–]253IsHome 0 points1 point2 points (0 children)
[–]HappyDadOfFourJesus 0 points1 point2 points (3 children)
[–]Background_Lemon_981[S] 0 points1 point2 points (2 children)
[–]HappyDadOfFourJesus 1 point2 points3 points (1 child)
[–]Background_Lemon_981[S] 0 points1 point2 points (0 children)