General discussion

Locked

server1.companyname.com

By minookarthik ·
Is it risky to have fqdn as server1.company.com, regarding internet security. Is it relatively safer to have it as server1.companyname.local?

This conversation is currently closed to new comments.

4 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by BFilmFan In reply to server1.companyname.com

Unless you are hosting externally-facing web servers inside of your network, there is no good reason to use anything other than .local on your internal DNS namespace.

Collapse -

by minookarthik In reply to server1.companyname.com

Will the .local be of any future consequence if we decided to bring in the mail in house...so the mail ids would be username@companyname.local

Collapse -

by adembo In reply to server1.companyname.com

The .com is not a security risk unless you have that domain name registered. Do you? If so, then do not include the .com, if not, then no big deal. You can have it be .whateveryouwant

Collapse -

by minookarthik In reply to server1.companyname.com

Yes our domain is registered and we have our site running with a hosting company. Now I've have already named my internal domain companyname.com, so what should i do to protect it. Its already behind a soho firewall and most of the ports are closed, is it relatively safe now? What other things can I do to make it safer? Thanks for your answers, I really appreciate it.

Back to Networks Forum
4 total posts (Page 1 of 1)  

Related Discussions

Related Forums