I was configuring PAT to an address of xxx.xxx.45.5, but after checking with my ISP and the entries they have for us in their DNS servers they show an address of xxx.xxx.45.2. Hmmm. I'm going to try changing my PAT to use the 45.2 address and see it that solves my problem.
could you let me know if you resolved the problem as i struck up with the same?, I want to know how you resolved the DNS problem if so, becuase at my customer end i can't ping DNS hence no browsing ,I deployed lot of PIX es but never face such a problem, and never i explicitly permited the DNS , all other s work fine , only problem with this site,
The Web site you are looking for is unavailable due to its identification configuration settings
"This error indicates that the gateway could not find an authoritative DNS server for the Web site you are trying to access. "
Well, I was doing a few things wrong. The first thing was putting an ACL on the inside interface. I didn't need to put an ACL on the inside interface since everything from the inside is permitted out by default. To test this I removed all ACL's on inside and outside interfaces.
The second thing was that all of our workstations were set to look at only our DNS servers and not our ISP DNS servers. To solve this I could either modify all of the workstations to have our internal DNS server ip address as the primary and the secondary DNS server ip address of our ISP. The second option was to have our DNS server send any requests that were not in it's list out to our ISP. That's what I did because we have over 1000 workstations and I didn't want to modify all of them.
The third thing I forgot to change was on the workstation in IE. It was sent to use a Proxy Server because our old firewall was doing Proxy Services, so I had to remove the setting to "Use a Proxy Server".
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...