Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DNS Naming Convention

Status
Not open for further replies.

jojo235

Technical User
Oct 17, 2003
3
US
Let's say I have a domain on a shared host ( called
At the registrar, I listed ns1.host.com as the DNS.

Then I get a new dedicated server where I set up my own name server and call it ns1.blahblah.com

Now, I go to the registrar and point a different host to use DNS of new server, ns1.blahblah.com
It then prompts me to enter ip address of ns1.blahblah.com which I do, and after 24 hours am able to visit on the new server.

My question is, what's to prevent me from naming my name server ns1.yahoo123.com, as long as it's not registered in any DNS servers, should I be able to use it? And what would happen if yahoo decides to buy the yahoo123.com domain and want to use ns1.yahoo123.com domain as their own name server?

Thanks in advance for clearing this up.
 
If I get you correctly, you are using this server only for your own DNS resolution, because no one else in the world would know the IP address except your own computers with that address set as the DNS server.

You can actually name it anything you want, actually, but unless it is properly registered, it will not be the SOA (start of authority) of the domain and would be ignored by the world. No one but your own computers would know to look to that server.

Am I getting your question correctly?
 
"If I get you correctly, you are using this server only for your own DNS resolution, because no one else in the world would know the IP address except your own computers with that address set as the DNS server."

Well, I went to netsol.com and for my blahblah2.com domain I pointed the DNS to my name server ns1.blahblah.com. And then I entered the ip address where ns1.blahblah.com is located (the new server).

"unless it is properly registered, it will not be the SOA"

Based on the explanation above, is ns1.blahblah.com registered properly?
 
Yep, sounds like.

So in answer to your first question.

"My question is, what's to prevent me from naming my name server ns1.yahoo123.com, as long as it's not registered in any DNS servers, should I be able to use it?"

Nothing at all.

"And what would happen if yahoo decides to buy the yahoo123.com domain and want to use ns1.yahoo123.com domain as their own name server?"

The only people that would be affected if this were to happen would be people using you DNS server to resolve yahoo123.com, Unless you advertised your server as a "caching server" ("come use my great DNS server!") no one but folks internal to your site would be using this server.

You can name the server anything you want. As long as it is not registered as SOA for the domain, no one externally will be directed to it to resolve names. (and no one would be able to find it, because it would not be registered in DNS in the server that really was SOA for the domain.)

Dana


 
"Unless you advertised your server as a "caching server" ("come use my great DNS server!") no one but folks internal to your site would be using this server."

Well, I'll be the only one using my name server, but if I go to and enter my domain name, the following is what I see:

INFO NS records at parent servers Your NS records at the parent servers are:

ns1.blahblah.com. [66.150.my.ip] [TTL=172800]
ns2.blahblah.com. [66.150.my.ip2] [TTL=172800]

[These were obtained from e.gtld-servers.net]
PASS Parent nameservers have your nameservers listed OK. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers. If you aren't listed there, you can't be found. But you are listed there, with 2 entries.
PASS Glue at parent nameservers OK. The parent servers have glue for your nameservers. That means they send out the IP address of your nameservers, as well as their host names.
--
So it would seem that ns1.blahblah.com must be a unique value. Which brings me back to my initial point, since they don't know I also own how can they allow it to be registered as ns1.blahblah.com; If the real owner of the blahblah.com domain ever wanted to set up and register a name server as ns1.blahblah.com, it would not be possible it would seem.

There still seems to be some piece of information I'm not aware of.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top