I have been assigned this problem with no previous DNS experience so I've been cramming Linux DNS for the last couple of weeks.

The company I work for has two offices in different cities. I'm trying to attempt a DNS configuration where each office has their own DNS primary and secondary that they can edit independently with changes being shared between the two.
I know that this can be partially accomplished with a master-slave configuration but the slave site would have to put a request in to add or change a system.

One option I was looking at was to add a subdomain but this would mean changing the names of all the systems.

We originally had a master-slave all Linux solution but our remote site who was the master changed the DNS server to Windows and broke some functionality and ended remote administration.

Is there some elegant solution to this?

For master slave you could have:

Site A:
-------
Master A
Slave B


Site B:
-------
Master B
slave A

So if cxn goes down, you've got a copy of both at each location.

Always have caching on as well.

Note that a given machine/server can be both a Master for eg zone1 and a slave for eg zone 2 at the same time.

You might want to look at 'forwarders' & 'notify' options to increase update efficiency.

check out the chapter here http://www.linuxtopia.org/online_boo...namedconf.html

Thanks for the suggestion.

But in this configuration if Site B were to add a system to Master B then Master A and Slave A would not be in sync with Master B and Slave B.

Hi,
If you add/change something in Master B (located at Site B),
the server Slave B (located at site A) will sync with
Master B, everything works ok.

Master A/Slave A works in the same way, Master A is located at Site A
and Slave A is located at Site B.

Best regards,

I understand that the slaves will sync with the masters. But Master A and Slave B will not have the same information and vice versa. So I'm assuming that forwarding will need to be used between the primary and secondary on each end.