Hi All,
I am a web developer/programmer and I have a problem. First off, I work for a relatively small to medium sized company with a somewhat dysfunctional IT department so I am not getting much help there.
I was tasked with refreshing the corporate website which I built on a new hosted server and when it was ready, I had an IT guy point the domain to the new server. It all went well except for some reason everyone that is connected to our corporate network is still seeing the old website. It has now been 48 hours and while everyone else in the world appears to be getting routed correctly, including me when I am home even if I am connected to my office VPN, people at the office that are connected to the network directly are not seeing it.
I have tried doing tracert and nslookup in both places and when I am connected to the network, I get the old IP and when I am home, I get the new IP.
Does anyone have any ideas why this might be happening? I was thinking that there must be a hard coded record somewhere that is telling local machines to point to the old site. The problem is that along with being mildly dysfunctional, the IT department is almost all new so none of them would know if an exception was made somewhere.
I was thinking maybe it has something to do with the web security company they use? I am at a loss but this site needs to be available to people on the network because it is hard to explain to a CEO how DNS works and expect them to accept that while they see one thing, everyone else sees the new website.
Thanks!
Red
I am a web developer/programmer and I have a problem. First off, I work for a relatively small to medium sized company with a somewhat dysfunctional IT department so I am not getting much help there.
I was tasked with refreshing the corporate website which I built on a new hosted server and when it was ready, I had an IT guy point the domain to the new server. It all went well except for some reason everyone that is connected to our corporate network is still seeing the old website. It has now been 48 hours and while everyone else in the world appears to be getting routed correctly, including me when I am home even if I am connected to my office VPN, people at the office that are connected to the network directly are not seeing it.
I have tried doing tracert and nslookup in both places and when I am connected to the network, I get the old IP and when I am home, I get the new IP.
Does anyone have any ideas why this might be happening? I was thinking that there must be a hard coded record somewhere that is telling local machines to point to the old site. The problem is that along with being mildly dysfunctional, the IT department is almost all new so none of them would know if an exception was made somewhere.
I was thinking maybe it has something to do with the web security company they use? I am at a loss but this site needs to be available to people on the network because it is hard to explain to a CEO how DNS works and expect them to accept that while they see one thing, everyone else sees the new website.
Thanks!
Red