Externally, people are unable to reach our website - aaa-aa.com. Internally, we can resolve the site with no problem by ip and name. From the outside, via hot spot, from home, and based on complaints from suppliers, the website does not seem to exist. However, an NSLOOKUP on 8.8.8.8 for aaa-aa.com does resolve our name to the correct .aaa IP address. We check with our domain host, and those records are pointing to the right address too.
My boss has determined it is not a problem with IIS or any connected internal service. Inside is fine, outside is the problem. Aaa-aa.com should currently not be available because of this problem. Normally, it would resolve our company website.
Bb-bbbbbbb.com is for our primary address (email, etc.). At its most basic, you should not get a response unless you change ports or add more to the URL.
The bulk of our internal client traffic leaves our building on one of our IP addresses - x.x.x.bbb. This is our Exchange IP, and also standard traffic. Currently, and it should not be, our web server is sending web traffic to the .bbb address. When we google “what is my ip address” we get the .bbb. When we do a “shields up” search, it also probes the .bbb address. Traffic from this server should be from .aaa, inbound and outbound.
I have looked over our firewall routes. From what I can discern, our entries are correct and have not changed in over a month. Our internal x.x.x.aaa (web server) should route to external x.x.x.aaa. We even opened and additional 8080 port just to make sure that our ISP was not blocking 80 for some reason. We even added an “any/any ip” rule for about 10 minutes at the beginning of our ACL list, and were still unable to access our website externally. I tried configuring a different ASA and substituting that and had no luck.
Between 4:30-5a Wednesday morning, external traffic stopped and only internal IP addresses were listed. The Windows software firewall has always been “off” and still is.
We are at a loss. We have called our ISP and they claim they are not blocking any ports and that our ip addresses are correct and working. The same is true for our domain host. To me, it seems that something is routing our traffic to the wrong IP address. Externally, NSLOOKUP shows the correct destination IP. I thought maybe our firewall is redirecting traffic, but we can’t if that either. We need a fresh set of eyes.
