I've been having this issue with a web app located on a local webapp server. When the address is used outside my network it resolves perfectly and goes streaight into the website. Yet when tired to access from inside the network it give a website not found. When I run nslookup internaly for webapp.capsure.com without the dot at the end it gives me my internal address fine. Yet when I nslookup webapp.capsure.com. with the dot it gives me an ip address that does not exist (184.108.40.206). This issue started to happen all of a sudden without any changes to the servers.
Internally i can access the site with the ip fine... but my dns seems to not pick up or take effect on any of my client computers. My domain controller is the DNS, AD, and Excahange server and it has not gone down at all and for some reason dns stopped resolving yesterday morning.
I do not own capsure.com and just have the subdomain with them since its their app we are currently using (when it was working). They host their domains with Network Solutions and according to support they had network solutions update their records which was their first solution to the problem "wait until the updated records poppulate". Its been a day and it seems to be more than that. When i run a tracert from inside the network it points to the 220.127.116.11 and stops at hop 10.
When I run tracert from outside the network it hops all the way to the external ip of the server.
I would appreciate the help i need this webapp to be up since it does a crucial function at this place.
Addresses are fake if you need me to place real addresses so you can help let me know.
Thanks in advance