How did you determine that "it is trying to route to the public IP address." By running netstat one one of the clients?
If you do an nslookup pointed to an internal DNS server on one of the clients having the problem, it resolves the correct DMZ ip, right? On Thu, May 27, 2010 at 3:44 PM, mqcarp <mqcarpen...@gmail.com> wrote: > OK here is what is happening. When you go to one of the internal sites > through a browser, it stalls, and then says it can not be reached, but > what I noticed is that it is trying to route to the public IP address, > not the DMZ address, which is what the internal DNS should be doing. > So for some reason it has determined that it can not route that way > and is sending the request to the DNS forwarding address. If you do an > nslookup for the site, it brings up the DMZ address. Very odd. We are > going to blow out the DNS zones. Possibly the records are corrupt? > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
