|Your network computers are looking to your internal DNS server for addresses (which they have to do for Windows networking to work). That DNS server records cyberfox24.co.uk as the address of your server (192.168.0.9) which is not the address of your external web site. Using the same domain name for an internal Windows network and an external public network can lead to this sort of problem.|
The easiest solution would be to rename your external web server as www.cyberfox24.co.uk and then add an "A" record in your internal server linking www.cyberfox24.co.uk with the IP address of the external web server.
Your internal server should list itself as its DNS server, either as 192.168.0.9 or as localhost (127.0.0.1). It can then either resolve external addresses directly or, slightly more efficient, be set up to forward queries that it cannot resolve to 220.127.116.11. I forget the exact procedure for this on Windows server, but you are looking for "forwarders" in the DNS Server properties.