Removing forward lookup zone broke our site - why?

Posted by user102469 on Server Fault See other posts from Server Fault or by user102469
Published on 2011-11-29T15:48:53Z Indexed on 2011/11/29 17:53 UTC
Read the original article Hit count: 341

Filed under:
|
|
|
|

I'm fairly new to the job and trying to get to grips with the infrastructure here. We've moved a site from being locally hosted on our own network to an external host (1&1). I've transferred the DNS hosting from the previous DNS host to 1&1 to keep things simple.

Once everything had gone through, visitors that were external to our network were being directed to the new site on 1&1 but requests from within our network were still going to our own server.

I noticed in the DNS server that there was a forward lookup zone for the site pointing to our own server still. My (admittedly simplistic) understanding was that pausing that zone would then cause the DNS server to get the address for the site from our external DNS servers and our users would start landing on our new site. However, what happened instead was that they were being met with "page not found" type errors. I've resolved it my modifying the forward lookup zone A record to point to the external web server but would like to get an understanding as to why pausing the zone didn't work. Would deleting the zone work? I am reluctant to try that as creating it again will not be as easy as simply pressing "start".

Many thanks.

© Server Fault or respective owner

Related posts about Windows

Related posts about dns