A
awreaper
I run an internal 2016 DNS server. I have approximately 150 WIndows 10 client machines. There is a website that I can't reach if I use my internal DNS server as my client's only DNS server. They can ping it and it resolves to the correct IP address but they get a site can't be reached page. If I change my clients DNS server to 4.2.2.2 and do an ipconfig /flushdns then they can access the page. Pinging it using 4.2.2.2 yields the same results as pinging it with my internal DNS server. It resolves to the same address and is pingable. I have tried this with multiple browsers and get the same results. Any help you can provide would be greatly appreciated.
Continue reading...
Continue reading...