At work we have an internal server which we use to host things like a wiki and other internal applications - we also use it to demo applications we're currently building within an environment other than our own machines.
Historically employees have had to use
http://ServerName:Port to navigate applications on this server and this is precisely what I'd like to overcome; what I want to enable my colleagues to do is use a friendly, familiar and also somewhat descriptive URL. How might one achieve this?
I followed an article which walked through the process of setting up DNS on a server but to no avail.
Is there a clean-cut, efficient way to do this as I'm just wasting time right now?
I set up
Forward Lookup Zone(with defaults so it auto-added
CNAMErecord which uses the parent domain
I can hit
http://ServerName which directs me to the default website (which is some Sharepoint thing, I think, stored in the
c:\inetpub\wwwroot folder), however on setting up a new website in IIS and adding the header values I want (say,
wiki.servername(.co.uk)), I simply can't land on this page as it tried to enter the wild.
Any thoughts on how I might achieve this or what I might be doing wrong?