T
Terje Trane
I'm a bit surprised right now....
I'm editing some websites on a couple of servers with virtual webs on. One
server is the internal work server where we develop and test sites and one
is the actual production server that people see. I did a mistake in adding a
DNS entry on the DNS-server, pointing www-work.ourdomain.com to the external
instead of the internal server. So, when I opened what I thought would be
the work-in-progress I saw the old published site.
Ok, I fix the DNS and press F5 in IE. Did not help. Ah, it is in the cache,
I thought, and pressed Ctrl-F5. Still the same. I flushed the clients DNS
cache (ipconfig /flushdns) and checked a ping to the www-work server: it
shows the right IP-address. IE does not. I delete temporary internet files:
does not help. I restart IE: does not help. I telnet to port 80 on www-work
and do a GET / HTTP/1.1 request with Host: www-work.ourdomain.com, and there
I see the work-in-progress. Also on another computer I can pring up the
correct page. It is just in an instance of IE that first has been using the
wrong IP-address that does not work.
The questions are: What is happening? Has IE an internal DNS cache? Is there
a way to workaround/solve this?
I'm editing some websites on a couple of servers with virtual webs on. One
server is the internal work server where we develop and test sites and one
is the actual production server that people see. I did a mistake in adding a
DNS entry on the DNS-server, pointing www-work.ourdomain.com to the external
instead of the internal server. So, when I opened what I thought would be
the work-in-progress I saw the old published site.
Ok, I fix the DNS and press F5 in IE. Did not help. Ah, it is in the cache,
I thought, and pressed Ctrl-F5. Still the same. I flushed the clients DNS
cache (ipconfig /flushdns) and checked a ping to the www-work server: it
shows the right IP-address. IE does not. I delete temporary internet files:
does not help. I restart IE: does not help. I telnet to port 80 on www-work
and do a GET / HTTP/1.1 request with Host: www-work.ourdomain.com, and there
I see the work-in-progress. Also on another computer I can pring up the
correct page. It is just in an instance of IE that first has been using the
wrong IP-address that does not work.
The questions are: What is happening? Has IE an internal DNS cache? Is there
a way to workaround/solve this?