Hosting public dns without domain name

  • Thread starter Thread starter Daniel Tan
  • Start date Start date
D

Daniel Tan

Can i host a public dns server without having subscribe to a domain
name ? User will have to key in my dns server ip in ther machine to
act as forwarder. Pls advise. Thanks

Rgds
Daniel
 
In
Daniel Tan said:
Can i host a public dns server without having subscribe
to a domain name ? User will have to key in my dns server
ip in ther machine to act as forwarder. Pls advise. Thanks
Click to expand...

No you cannot, in order to have a public name server registered at the
parent servers for the TLD, it must have a second level domain name.
 
Why ?

Kevin D. Goodknecht Sr. said:
In

No you cannot, in order to have a public name server registered at the
parent servers for the TLD, it must have a second level domain name.
Click to expand...
 
In
Daniel Tan said:
Why ?
Click to expand...

You would have to ask ICANN that question, your name server must be listed
at the TLD servers in order to host public domains.
 
Let me try.

If you host www.whatever.net. Say one of my clients want to go to that site.
The client will ask my DNS server for www.whatever.net. My DNS server will
"truthfully" say, I don't know, but let me see if I know the name server
responsible for whatever.net. Of course, my DNS server does not know that
yet, so it will say "no problem, I'll just go ask the name server for the
"net" domain. So, my DNS server will walk up to the "net" name servers (the
TLDs, the Roots servers) and say:
Excuse me guys, but I am looking for the nameserver for the zone called
"whatever"

Now the question is what do you think would happen IF the TLD servers don't
ahve a name for you? They would just laugh at my DNS server. Then my DNS
server would get mad and go smack my client and the client would get upset
and do a BSOD and my support calls would go through the roof. All because of
you :)

Ahem..... I got a little carried away there....but you get the picture. You
are required to publish a Name/IP pair with the Root Servers so that we all
can find your server and ask it for the records that it says it is
responsible for. It just keeps things orderly and proper, see?

--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
Microsoft MVP - Directory Services
www.readymaids.com - COMPLETE SPAM Protection
www.akomolafe.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
 
In
Deji Akomolafe said:
Let me try.

If you host www.whatever.net. Say one of my clients want to go to
that site. The client will ask my DNS server for www.whatever.net. My
DNS server will "truthfully" say, I don't know, but let me see if I
know the name server responsible for whatever.net. Of course, my DNS
server does not know that yet, so it will say "no problem, I'll just
go ask the name server for the "net" domain. So, my DNS server will
walk up to the "net" name servers (the TLDs, the Roots servers) and
say:
Excuse me guys, but I am looking for the nameserver for the zone
called "whatever"

Now the question is what do you think would happen IF the TLD servers
don't ahve a name for you? They would just laugh at my DNS server.
Then my DNS server would get mad and go smack my client and the
client would get upset and do a BSOD and my support calls would go
through the roof. All because of you :)

Ahem..... I got a little carried away there....but you get the
picture. You are required to publish a Name/IP pair with the Root
Servers so that we all can find your server and ask it for the
records that it says it is responsible for. It just keeps things
orderly and proper, see?
Click to expand...


Not really totally understanding Daniel's post, but after trying to re-read
thru it multiple times and decipher it, I think Daniel wants to just host a
private domain name and his private users will only use his server for that
specific domain's resolution, but at the same time configure a forwarder so
it will resolve other outside names. If that is the case, sure why not? But
for public use, I agree, no way.

But what doesn;'t make sense is that his "User will have to key in my dns
server ip in ther machine to act as forwarder." That is a DNS function, so
if I re-read this a few more times trying to undestand it, it seems that he
wants to host this private domain name and have specific client networks'
DNS servers use his DNS server as their forwarder so it will be able to
resolve this private name, and still resolve outside names with a configured
forwarder.

Just a WAG...
:-)

Ace
 
Ace, thanks for reply and u r partially right. What i trying to figure
out is hosting a public dns server for all user, not for my office
user only. It will be like ISP dns server where everyone can use it as
forwarder. What do you mean by private domain name and have specific
client networks' DNS servers use his DNS server as their forwarder ?
What i mean for user will have to key in the dns server ip as
forwarder is for public user where we normally key in our isp dns ip.

Rgds
Daniel
 
Just follow what Kevin told you originally. There is no other option for
you.

--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
Microsoft MVP - Directory Services
www.readymaids.com - we know IT
www.akomolafe.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
 
In
Daniel Tan said:
Ace, thanks for reply and u r partially right. What i trying to figure
out is hosting a public dns server for all user, not for my office
user only. It will be like ISP dns server where everyone can use it as
forwarder. What do you mean by private domain name and have specific
client networks' DNS servers use his DNS server as their forwarder ?
What i mean for user will have to key in the dns server ip as
forwarder is for public user where we normally key in our isp dns ip.

Rgds
Daniel
Click to expand...


From your response, you are hosting a public zone. As Kevin mentioned, you
need to register that zone with the registrar and register your DNS server
as a hostnameserver with the registrar. Otherwise, its a private domain and
you would need to tell your specific users to specifically use YOUR DNS to
resolve this domain.

Ace
 
Ace, what you mean is if i don't register to the TLDs registrar it
won;t become a public name server but my internal or specific(remote)
user will be able to use it as forwarder if they know my dns ip
address, right ?

Rgds
Daniel
 
In
Daniel Tan said:
Ace, what you mean is if i don't register to the TLDs registrar it
won;t become a public name server but my internal or specific(remote)
user will be able to use it as forwarder if they know my dns ip
address, right ?
Click to expand...

Correct.

Ace
 
Back
Top