On 3/8/07, Oded Arbel <[EMAIL PROTECTED]> wrote:
What are you using a name server for ?
* If you are using a name server to provide DNS services to your own
local network, then you better reference the main root servers.
No.
* If you are using a name server to cache DNS queries for local
processes ("caching name server") then you should forward all real
requests to your ISP's DNS - same as what a regular process would do.
Yes.
* If you are using a name server to host a domain (an "authoritative
name server"), then you shouldn't have your name server do external
queries as all, so it doesn't matter how you are not resolving outside
addresses.
Yes.
My DNS server is both a authoritative name server for my domain names,
and also a caching name server for all other domain names. I also
have a mail server, which uses my DNS server to resolve domain names.
And also, my ISP has only 2 DNS servers, and I don't want to rely
completely only on them. If both of them don't work, I still want my
server to work. I'm using my 2 ISP DNS servers also as secondary name
servers for some of my domain names (such as speedy.net), and as
caching name servers for the rest of my domain names (such as
pazgal.com) - that is, they are listed as authoritative name servers
although they are not. It works fine (they return a correct
non-authoritative answer). When I shut down my DNS server, the domain
names such as speedy.net resolve fine, while domain names such as
pazgal.com do not (depends on the cache).
> P.S. How do I check which version of BIND I'm using?
I usually do rpm -q bind, why ? what do you do ?
[EMAIL PROTECTED] speedy]$ rpm -q bind
bind-9.2.1-9
Uri.
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
