Domain naming conventions...

truenegative

truenegative

Verified User
Joined
Feb 16, 2006
Messages
152
Hey all...

I'm looking for some best practice ideas for naming the network that my servers/network devices, etc....

Lets say my company is called xyz, and I have xyz.com. I would think that using server1.xyz.com, server2.xyz.com and so on, would be somewhat of a security risk.

So, I got to thinking, should I pick a "network" name that I can almost use for marketing as well. Something like you server would be hosted on our "cool network name" network. Then all the servers would be server1.coolnetworkname.net, server2.coolnetworkname.net, etc.

Do you guys have any ideas, suggestions, or caveats to doing something like this? I want to figure this out somewhat quickly because if I need to change the main dns, it would affect a minimal amount of customers. on the server I have.

Thanks :)
 
I would think that using server1.xyz.com, server2.xyz.com and so on, would be somewhat of a security risk.
Click to expand...
I'm a bit puzzled by this. Why would you think that would be a security risk?
 
Re: Re: Domain naming conventions...

Aspegic said:
I'm a bit puzzled by this. Why would you think that would be a security risk?
Click to expand...

Well, maybe I'm paranoid, being in the network industry, but i would think that its one step for a "hacker" to have to go through to find your server. Since the company name won't link to it, and your customer's domain names won't really link to it....maybe i'm just out of my mind...
 
Your intentions are well founded, but really aren't necessary in today's internet.

common server naming conventions are perfectly acceptable - and with proper use of a firewall and prudent security measures, you'll be fine

Joe
 
currently my device (ie server, router, switch, etc) naming conventions are celesital objects (everything from planets to constellations, etc). However, I've been considering going to more of a business like standardized naming as well such as city-sdasrv01 or something similar.

Back to the domain issue, I could always do it for marketing reasons, and basically "name" the network something cool, and base marketing off that.
 
Re: Re: Re: Domain naming conventions...

tarionyx said:
Well, maybe I'm paranoid, being in the network industry, but i would think that its one step for a "hacker" to have to go through to find your server. Since the company name won't link to it, and your customer's domain names won't really link to it....maybe i'm just out of my mind...
Click to expand...
If anyone knows how to find your website all they have to do is a traceroute to it, and the reverse DNS will show them not only your network, but where it is and what it's named and how to find it.

Jeff
 
Re: Re: Re: Re: Domain naming conventions...

jlasman said:
If anyone knows how to find your website all they have to do is a traceroute to it, and the reverse DNS will show them not only your network, but where it is and what it's named and how to find it.

Jeff
Click to expand...

good point. so you got me, the only reason is to be cool.
 
ok so if i decided to change the domain of the server...what are the best steps to do so?

change it in DA, then on the server itself?
 
Changing it in DA should change it on the server; you'll need to both change the domain name, and the server hostname (in DirectAdmin).

Jeff
 
ok thanks for all your help again jeff :)

you probably have a lot of beers owed to you....if you're going to cisco networkers....PM me and I owe you some beer :)
 
I'll be at the west coast (USA) ISPCon next winter, and possibly at the webhosting con later this year.

:D

Jeff
 
You must log in or register to reply here.
Back
Top