Here is my setup:
for internal DNS'es.

1) Japan : ns1.jp.mysite.com
2) US : ns2.us.mysite.com
3) EU : ns3.eu.mysite.com


I got them connected by VPN.

now i want each of them to resolve all the machines on the other end.

Like ns3.eu.mysite.com should be able to resolve <host>.us.mysite.com & <host>.jp.mysite.com

got a lot of suggestions from different ppl on this. kinda confused.. whats the best way to get these to work?

like
2,3 should be slave to 1 & 1,2 should be slave to to 3 & so on..

or maintain 1 central DNS with all other being slaves or ..
something else...

thanks ...

like
2,3 should be slave to 1 & 1,2 should be slave to to 3 & so on..

or maintain 1 central DNS with all other being slaves or ..
something else...

From a DNS resolution perspective, either way will work just fine. I can think of a few requirements to consider that might help the decision process:

1) Bandwidth across the VPN's. i.e. zone update traffic
2) Size of the zone files
3) Are you going to implement DDNS?
4) The use of forwarder statements instead of slaves. i.e. DDNS implementation

We have a sufficient amount of bandwidth on the VPN & then again

not too many updates / changes would be done on zones that ..
the zone tx data mite over-burden the VPN.

Also do you know of any good DDNS clients to run from windows & linux for a Bind 9 server.
any links mite give me a head start

thanks. for your reply