I have setup an intranet with my organization.
Is it possible to have the domain companyName.home?
I'm a complete newbie to this and I don't know what the limitations are, normally, for intranet domain names.
I am no expert, but internally on your own network you can do what you like ;-)..
If you configure your local machines (the ones you want to access this site at least) with a DNS server that has a record saying that "companyName.Home" is 192.168.1.whatever then thats where the names will get resolved to.
You could call it google.com and it would work.. but google would not.
often .local is used at the top level domanin (right most name) as AFAIK it is reserved and will never beon the internet.
If your TLD does not exist on the internet its a bonus (AFAIK) as it means there can be no overlap in routing or authentication with the public internet. EDIT this looks not to be the case see links below..
EDIT: don't use .local (see comments) but idid find tis relevant question serverfault:
they seem to be saying best practice is to use a real TLD.. have a look for yourself though.
You can set up CNAMEs and alternate A records for servers too that allow you to have short names for internal services and sites. though I don't know best practice on this I have certainly seen things like "http://intranet/" setup in quite a few places.
Probably best to ask the question again over on serverfault.. the experts are over there ;-) but hopefully you have some extra ideas to discuss it with them. Also there are many questions relating to this over there..
I am no expert, but internally on your own network you can do what you like ;-)..
If you configure your local machines (the ones you want to access this site at least) with a DNS server that has a record saying that "companyName.Home" is 192.168.1.whatever then thats where the names will get resolved to.
You could call it google.com and it would work.. but google would not.
often .local is used at the top level domanin (right most name) as AFAIK it is reserved and will never beon the internet.
If your TLD does not exist on the internet its a bonus (AFAIK) as it means there can be no overlap in routing or authentication with the public internet. EDIT this looks not to be the case see links below..
EDIT: don't use .local (see comments) but idid find tis relevant question serverfault:
Using .local for internal websites
and
Top level domain/domain suffix for private network?
they seem to be saying best practice is to use a real TLD.. have a look for yourself though.
You can set up CNAMEs and alternate A records for servers too that allow you to have short names for internal services and sites. though I don't know best practice on this I have certainly seen things like "http://intranet/" setup in quite a few places.
Probably best to ask the question again over on serverfault.. the experts are over there ;-) but hopefully you have some extra ideas to discuss it with them. Also there are many questions relating to this over there..
There are 2 suggestions on http://en.wikipedia.org/wiki/Top-level_domain#Pseudo-domains - .site and .internal, but there is no real standard yet.
You can add a DNS record to your internal DNS server that points to the web server.