Net or Com for my Nameservers?

[Kenny]

A bit of information please?

I'm setting up my own NS1, NS2 and I was going to
go with ns1.xxxxxx.com and then I wondered if I
should use ns1.xxxxxx.net and leave the com
for Home Page and all.
I've seen that done lots of times and didnt know
why... who has some info on this?

Thanks, kid5150

 

[RJ]

Really makes no difference at all. You could go with ns1.xxxx.com for your nameservers and still use www.xxxx.com for your homepage. I really can't think of any advantage to using a different extension for a DNS server.

 

[Xyzer]

I dont think that it really matter, i always think that .com sounds better though.

 

[Maverick]

Doesn't really matter really, but I'd go with the .com just the same.

 

[shadow_boi]

yea, just use .com, doeant make any difference

 

[Kenny]

Thanks for everyone input, I will go with the dot com.
Peace, kp

 

[faisj]

I have used .net

 

[stscac]

I have used .net

Same here. Obviously, you already know that from a technical standpoint that it really does not matter. I think that .net gives it more of a technical meaning. Plus, if you own the .com and the .net, which one gets used more?

.com, in most cases. So, start making use of the .net

-Steve

 

[Kenny]

Same here. Obviously, you already know that from a technical standpoint that it really does not matter. I think that .net gives it more of a technical meaning. Plus, if you own the .com and the .net, which one gets used more?

.com, in most cases. So, start making use of the .net

-Steve

Thats what I was thinking, net for the net part
com for the com part.... but I went with the com.

 

[dongan]

.com would be the best for name servers. It would't affect your homepage at anyway.

 

[Tippy]

I use/used TLDNS.com as my nameservers but I'm thinking of using TLDN.net, I kinda like the .net more so for this usage, but as many mentioned it doesnt really matter, just a personal thingy.

 

[AdoptableDomains]

It really doesn't matter. you can use any extension, and it doesn't even have to be the same domain name for that matter. For consistency, most use ns1 and ns2, but the subdomain can be anything, and technically speaking, it wouldn't even have to be third level domains if you dedicated a domain name as a DNS server. Even the ns1. and ns2. could be different root and second level domains.

For redundancy, some companies use totally separate domain names and servers so that if one is down for some reason, the other shouldn't be. For maximum reduncancy, you might have ns1.domainA.com as a DNS server on the west coast and ns2.domainB.net on a DNS server on the east coast (or different country) with different backbone providers and registered with different registrars. You might even have 4 or 5 backups instead of the typical 1 server and one backup.

 

[NameRegistration]

It does not matter but I would rather use the .net. It matches better the extension IMHO.

 

[localpub]

It's better that the DNS match the domain's extention; i.e. use ns1/ns2.yourdomain.com for your dotcoms and ns1/ns2.yourdomain.net for your dotnets. I am pretty sure that makes domains faster to resolve. When browser or mailclient is searching for your dotcom, the first place for it to start is usually .com root-servers. If for your .com domain you're using .net nameservers, the .com root-servers usually have no 'clue' about them and forward the packet to .net root-server. This takes additional miliseconds, which sometimes are very precious.

This is my understanding how DNS works. If somebody of you will have something to add, feel free to do so.

 

[seeker]

It really does not matter at all from a technical point of view.
However, it does look more professional IMHO to use .net for nameservers.
Especially if you own both com/net of a domain, I would use net for nameservers, it gives you that extra 'look' that you are doing it professionally.
at least that is what I have noticed over the years, and what I do.

 

[ammo]

Id think its more proffesional to use a .com for nameservers, Just looks the part a little more. But technicly it doesnt matter, You can use them however you want.

 

[localpub]

But technicly it doesnt matter.

I think technically it DOES matter, few slight miliseconds. One more lookup, if the domain and DNS haven't the same tld. *Practically*, though, it really doesn't matter.

Please correct me if I'm wrong here.

 

[seeker]

AFAIK, it will not make a differene if the domain in use and the NS are not the same.
in either case, they would still be looking up the domain to route the IP...

 

[primacomputer]

Technically it does make a difference...sort of.

First off the root-servers have names like “a.root-servers.net”, so maybe .net is the “in thing”.

The TLDs .com and .net are handled by the same root servers which have names like “a.gtld-servers.net” There is no way .com is inherantly any faster or slower than a .net. There are no extra lookups.

Any latency issues are going to be more related to the users ISP and your DNS settings than anything else. For example, if you allow your zone to be cached for 30 days then (in theory) each ISP will only have to query each host once every 30 days. The rest of the time the request will be given to the user by the ISP without any further work to slow it down. Of course doing this means you may have to wait 30 days for changes to your zone to take effect, so don't do it.
By the same token if your settings are two low this could result in your DNS being queried to often meaning more latency.

But it happens to be an obscure artifact of the DNS design that a name server record stored in the .com zone file does not contain an extension if it is itself a .com. This saves five bytes (“.NET.”) times two since you have at least two name servers. Each of these ten bytes obviously takes time to process By using a .com name server with a .com name you presumably save each query of the gTLD root server 10 bytes of processing time (out of a 3GB of total). We aren't talking anything as massive as a millisecond here, but it would be something