Internal network naming convention
Posted on 2016-08-07
I've been asked to take over a Windows Server 21012 based network which has a raft of problems.
One of them is that the network has been called thecompanyname.net
They don't own thecompanyname.net, and it does exist on the public Internet.
Apart from them not being able to browse thecompanyname.net, which is never going to happen anyway, is there a compelling reason to reinstall the network?
I want it to be internal.thecompanyname.com.au, as they own and control thecompanyname.com.au
The business owner is reluctant to let me reinstall the network and I don't want to take the job unless I can do that