Hi,
I am new here and I am not a professional system administrator but as I have worked in sales for datacenter infrastructure I have a rough idea how things should work. Of course I have some sysadmin knowledge on Microsoft and Linux as well.
For a small company I set up a AD/DNS/Exchange environment. Everything works fine but there's one issue:
I can't reach my own companies website via webbrowser which is hosted by a web hosting provider.
The strange this is that I am able to ping the www address, nslookup and test-net-connection delivers correct results.
DCdiag doesn't return any error.
I have tried this from a Windows 10 client, from the AD/DNS itself and it's every time the same behavior.
All other websites are accessible except our companies one.
Some more information:
- all servers are VMs
- as naming scheme for the AD I have chosen: ad.contoso.com (replaced contoso by my companies name)
- in the forward lookup zone I created the host A entry for www.contoso.com which points to the webhosters ip address
- I only use root hints, no dns forwarders
- in the W10 client, I only use my local dns server as dns entry
As I never set up such an environment before, I first set up the VM for the AD/DNS with contoso.local.
After having read more I have realized that this naming is not best practice any more.
The weird thing is that with this AD I can reach my companies website without any issues.
So, I should be a routing/firewall problem.
If someone can help me resolving this I would be extremely happy.
Holger
.