DNS only resolves when using my nameserver

[Kevin Darcy]

No, no other nameserver needs to *replicate* your zone information, but
your domain needs to be *delegated* from somewhere, which in turn means
that you need to register the domain, if you haven't already. If you're
not familiar with the concept of domain registration, here's a brief
guide: if your desired domain is underneath a "generic" top-level domain
-- a gTLD -- like "com", "net" or "org", then you can use a variety of
registrars to register it, e.g. register.com. If, on the other hand, it's
underneath a country-code top-level domain -- a ccTLD -- like "ca", "uk",
"de" or whatever, then you have to go through the registrar for that
particular domain, which is often a governmental or quasi-governmental
organization, and often has restrictive rules on who can register and/or
what subdomains they must register in.

On the other hand, if you have registered a domain and it's only
resolving on your nameserver, then there may be some sort of problem with
the registration/delegation.

It would have eliminated some guesswork if you had just mentioned the
name of the domain. Is it some sort of secret?


- Kevin

Sean Goss wrote:

>  I am attempting to run my own nameserver using BIND and am having
> quite a bit of trouble. None of my host names resolve unless my name
> server is being used as one of the DNS servers in networking setup. In
> other words, no one that does'nt know the IP address of my name server
> can access my systems by name. Do I need to get other nameservers to
> replicate my information? Any help will be greatly appreciated.