our internal LAN is ourcompanyname.lan -- our external website is ourcompanyname.com
our primary internal DNS zone is ourcompanyname.lan.
We are rolling out an on premise install of LYNC / Skype for Business. in order to get that to work with autodisocver / auto sign in we had to add various dns entries..
the problem we faced with that was that the users sip address was username@ourcompanyname.com so the client was looking for settings inside the ourcompanyname.com dns zone (which did not exist)
in order to get around this, i created a new internal DNS zone called ourcompanyname.com and added all of the dns entries. success, my problem was resolved and everything for LYNC / SFB worked without issues.
the problem i am facing now, is that users on the internal LAN cannot reach our external hosted website. I get why, as its querying the new zone ourcompanyname.com for the www, which it cant find.
my idea of a fix was that i add a HOST record point www requests to the external ip address of the webserver.. this is not working and i dont know why. it still will not resolve.. if i do an NSLOOKUP on the internal LAN of the www address it resolved to the external ip address but it still wont display the website..
any suggestions / best practice? - was i in the wrong creating a new zone like that?
thanks in advance