DNS Server - The operation Timed Out
Hello All;
I am loading my internal website in a FRAME, and posting it on one of my live external sites at my hosting providers.
I can load the site on a proxy server, and it loads the site fast, and without issue.
However, when I load the page with the website in an iframe on one of my websites at my hosting provider.
It gives this error: The operation Times out
Windows 2003 Server / Windows DNS Server
I have the website DNS setup, and has been setup for over a year now (I just renewed the DOMAIN the other month)
The mail server is also running on the machine as well, and works great.
And yes, www has an A record as well
What DNS settings do i need to add in order to make it so I can load my internal sites in an iframe, like the proxy loads it.
Thanks
Carrzkiss
I am loading my internal website in a FRAME, and posting it on one of my live external sites at my hosting providers.
I can load the site on a proxy server, and it loads the site fast, and without issue.
However, when I load the page with the website in an iframe on one of my websites at my hosting provider.
It gives this error: The operation Times out
Windows 2003 Server / Windows DNS Server
I have the website DNS setup, and has been setup for over a year now (I just renewed the DOMAIN the other month)
The mail server is also running on the machine as well, and works great.
And yes, www has an A record as well
What DNS settings do i need to add in order to make it so I can load my internal sites in an iframe, like the proxy loads it.
Thanks
Carrzkiss
Let me ask a dumb question.... can you access your internal site from the internet? Also, can you resolve your internal server name from the internet?
If not, setup is not gunna work.
Your server at the hosting provider needs to be able to access the resources you are calling. It needs to be able to query DNS for the internal server's name & IP Address and then needs access to the tcp port that the internal server is running a web server on.
I keep repeating "internal" because you are trying to hit a service inside your network, which is typically protected by a security device... firewall. Unless you let in those services, you will receive: service unknown, request timeout, etc, errors.
My guess is that you are using an internal hostname and domain link in the iFrame and the external web server cannot resolve the internal server's IP because inbound DNS is being blocked. If you are using one of the private IP ranges on your internal network, this won't work because those addresses are not routable outside of your network.
Dan
If not, setup is not gunna work.
Your server at the hosting provider needs to be able to access the resources you are calling. It needs to be able to query DNS for the internal server's name & IP Address and then needs access to the tcp port that the internal server is running a web server on.
I keep repeating "internal" because you are trying to hit a service inside your network, which is typically protected by a security device... firewall. Unless you let in those services, you will receive: service unknown, request timeout, etc, errors.
My guess is that you are using an internal hostname and domain link in the iFrame and the external web server cannot resolve the internal server's IP because inbound DNS is being blocked. If you are using one of the private IP ranges on your internal network, this won't work because those addresses are not routable outside of your network.
Dan
ASKER
@Dan.
Taken from the second line of my question:
>>>> I can load the site on a proxy server, and it loads the site fast, and without issue.
So, with that pointed out.
All access ports are indeed opened. and ready.
DNS, Mail, Web are all opened.
As the proxy server would not have been able to access it otherwise.
As for having the wrong address in the iframe, NO
It if the fully qualified domain name, just like the one that I used in the proxy server.
Any other idea's?
Could there be something in the DNS?
Taken from the second line of my question:
>>>> I can load the site on a proxy server, and it loads the site fast, and without issue.
So, with that pointed out.
All access ports are indeed opened. and ready.
DNS, Mail, Web are all opened.
As the proxy server would not have been able to access it otherwise.
As for having the wrong address in the iframe, NO
It if the fully qualified domain name, just like the one that I used in the proxy server.
Any other idea's?
Could there be something in the DNS?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It is an internal issue.
Since the site resides behind my firewall, it is not going to load the page, unless it is through a Proxy Server.
Since the site resides behind my firewall, it is not going to load the page, unless it is through a Proxy Server.
http://www.aaronpeters.nl/blog/iframe-loading-techniques-performance
all the best