DNS - Forward lookup zone: "A" record issue
Hi Guys,
I have a 'www' A record added to the forward lookup zone in DNS for the company website (hosted externally to the local domain).
I can ping www.website.com from any workstation internally and it resolves to the correct external IP.
However, I am unable to open the site.
Initially I thought it was a browser cache issue, but it happens in IE and Chrome. The record was inserted last week, but it still gives error:
The site can't be reached
server IP address cannot be found
nslookup gives the correct website address and external IP.
Any ideas will be appreciated,
I have a 'www' A record added to the forward lookup zone in DNS for the company website (hosted externally to the local domain).
I can ping www.website.com from any workstation internally and it resolves to the correct external IP.
However, I am unable to open the site.
Initially I thought it was a browser cache issue, but it happens in IE and Chrome. The record was inserted last week, but it still gives error:
The site can't be reached
server IP address cannot be found
nslookup gives the correct website address and external IP.
Any ideas will be appreciated,
Mahesh
check if outbound http and HTTPS ports are opened from internal network to website public IP, it might be blocked
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
And are you sure the website doesn't respond to the internal address... when it sees an internal address?
Sarang is probably on the right track, as I've seen that multiple times. When you browse to http://www.website.com, does the URL in your browser's address bar change to simply http://website.com ? If so, there's definitely a redirect there.
You can verify a lot of claims by using curl ... ( https://curl.haxx.se )
curl -v -L http://www.example.com
will show all negotiations & headers including redirects.
curl -v -L http://www.example.com
will show all negotiations & headers including redirects.
ASKER
Thanks Sarang, this was the issue.
Is there no way to forward requests for a website in DNS, if it is presented without the 'www'?
Is there no way to forward requests for a website in DNS, if it is presented without the 'www'?
Glad that we find the cause and to answer your question Nope..This is catch 22 situation..If you allow website to work without "WWW" then the internal DNS queries will fail and if you allow internal DNS queries to work then website without "WWW" will fail so in such scenario any one of them fail so better get the redirection disabled.