master and slave zone for the same domain?

[Jim Reid]

>>>>> "Ramon" == Ramon Bastiaans <waxie at waxie.net> writes:

    Ramon> Can a dns server (bind / named in particular) have a master
    Ramon> and a slave zone for the same domain? 

No. Please think about it. To be master or slave for some zone, a BIND
server has to have a zone{} statement for that zone. It cannot have
two statements for the same zone. And it's meaningless for a name
server to transfer a copy of the zone to itself when it's already
authoritative for that zone. If this was possible, the name server
would generate SERVFAIL errors and scream about sending queries to
itself when the "slave" checked the "master" for the zone's SOA record
every refresh interval.

You also seem to have not understood the whole point for having at
least two name servers for a zone. This is done to prevent a single
point of failure. If one server dies, there's at least another one
somewhere that is reachable. Putting them on the one box is not very
wise.

    Ramon> Would it pollute the root servers?

No. Why would the root servers even care about your zone? The root
servers just contain delegations for the top-level domains. They won't
have any information about your zone and even if they did, couldn't be
"polluted" by having that information. Root servers don't cache DNS
data that didn't get loaded from their zone files.

    Ramon> The primary dns for this domain (a real domain) is hosted
    Ramon> on an other dns server with the real (internet reachable)
    Ramon> ip adres of the domain.

This is known as split DNS. You should be able to find plenty of
advice on how to set this up now that you know what it's called. :-)