search for: securityedg

...ta > ?????????? ? ? ?? |---> anything outside the AD domain --> ask forwarder > > Rowland > Thanks for the reply Rowland. Yes, I'm sure it was working before & now I've figure out what the real issue was. When we upgraded our Comcast service & came with their new SecurityEdge service. A cloud based web filter that's supposed to block malware, phishing, etc.. https://business.comcast.com/learn/internet/security-edge However, it seems it's also blocking BIND from receiving the DNS replies from the root servers. To fix it I put BIND in forwarding mode to 1.1.1....

OK here's our setup, we're running pfSense as our firewall/router. We have a dual-WAN with a Comcast Business Gateway and another local ISP. We're running Samba 4.7.6 as the AD DC & Bind 9.9.4. Here's the issue, we just upgraded our Comcast service to a higher speed & they replaced the modem/gateway. Everything was working fine, before the modem swap. Once they did