Custom Nameservers

what to call them?

[mm1220]

Hello all,

My host has given me custom nameservers as part of a package. Now I could go for:

ns1.mydomain.com to ns4.mydomain.com

but I'm thinking of being creative:
north.mydomain.com south.mydomain.com etc

anyone got any other suggestions or even reasons why this is a bad idea?

[davezan]

How about iamthealpha.mydomain.com and andtheomega.mydomain.com? ;)

[py9jmas]

See RFC 1178 - Choosing a name for your computer
[faqs.org...]

[mcavic]

Some of my favorite computer names:

zeus, thor, isis, mischa, petya

[vkaryl]

py9jmas, that's a nice article. Thanks.

[ritch_b]

Interesting article indeed!

To chip in my two penneth, I've a dubious partiality for using a car-related theme:

scirocco.mydomain.com
corrado.mydomain.com

I know, I should get out more...:) Since the nameservers are only for my benefit and, on the whole, nobody else should ever need to refer to them, having names that are open to misspelling isn't really a problem for me. If this wasn't the case though, I'd certainly pick easier to use names that aren't as likely to be misheard or misspelt.

Until that day though, I've an entire range of VW cars to use!

R.

[topr8]

use ns1. etc

following the conventions is much more professional, it also saves confusion, 1 would be primary 2 secondary etc

[rfgdxm1]

Really, is this something THAT important? Do whatever floats your boat. Personally, I think topr8 has the right idea. Just follow standard convention. The advantage of this is that you don't need to remember what name you chose for your nameservers. Just use the standard defaults, and you need not worry about forgetting anything.