DNS Doctoring not working/ setup correctly

I thought I had DNS doctoring setup correctly but it deosnt appear to be working. Can someone forward me the CLI commands to setup DNS doctoring where a http and https requests the get resolved to 142.176.xxx.xxx gets reverted to an inside webserver at 192.168.113.15.

The "dns" keyword at the end of the static lines is all you need.
The key is where is your dns server located? Are you using an internal DNS server for the internal clients?
If yes, then doctoring won't work anyway. The dns request must come from the client, pass through the firewall, then the response from an external dns server will be doctored before it is sent to the requesting pc.

This is what is wierd.
Yes the DNS server is local and the record on the server is pointing to the correct internal IP of the webserver. I have also manually input the record in the local machine(s) host file but for some unknown reason, at times both of these get ignored and a local PC will resolve the address to the external IP. I end up going around and doing a ipconfig /flushdns on the offending machines.

so, both the public facing and the local domains are yourcompany.com?
Are you using DHCP or is everything static? Do clients have your local dns as primary and an external as secondary?
Agree that it is odd, because 1) the hosts file should be preferred, and 2) if they did go outside to a resolver, it should be doctored as it comes back in..

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

"so, both the public facing and the local domains are yourcompany.com?" Yes. Should they be different?

"Are you using DHCP or is everything static?" a bit of both. all servers are obviously static as well as a few workstations. Most workstations are DHCP though
"Do clients have your local dns as primary and an external as secondary?" Yes. Right now I'm getting ready to test a machine with a static IP and external DNS servers only to see if DNS doctoring is working

Ok I just switched my machine over to a static IP with external DNS servers. Flushed the local dns, rebooted. then tried to go to www.mydomain.com. page couldnt be displayed. :(
Tried to ping www.mydomain.com and it resolved to the external IP :(
To me it doesn't look like DNS doctoring is working at all. ARGH... lol

Featured Post

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

As managed cloud service providers, we often get asked to intervene when cloud deployments go awry. Attracted by apparent ease-of-use, flexibility and low computing costs, companies quickly adopt leading public cloud platforms such as Amazon Web Ser…

Both in life and business – not all partnerships are created equal.
As the demand for cloud services increases, so do the number of self-proclaimed cloud partners. Asking the right questions up front in the partnership, will enable both parties …

As a trusted technology advisor to your customers you are likely getting the daily question of, ‘should I put this in the cloud?’
As customer demands for cloud services increases, companies will see a shift from traditional buying patterns to new…