With a little planning a DNS structure can work very effectively. How you do it depends on your current set-up and how you prefer to have it organised.
I would personally do the following:
Primary Site Master Server:
zone localdomain.local.
SOA for localdomain.local = ns1.localdomain.local
Nameservers for localdomain.local = ns1.localdomain.local
zone site1.localdomain.local.
SOA for Site1.localdomain.local = ns1.localdomain.local
Nameservers for Site1.localdomain.local = ns1.localdomain.local
ns1.site1.localdomain.local IN CNAME ns1.localdomain.local
zone site2.localdomain.local.
SOA for Site2.localdomain.local = ns1.site2.localdomain.local
Nameservers for Site2.localdomain.local = ns1.site2.localdomain.local
The reverse lookup table should also be considered:
If the local site has the range 10.0.0.0/24 and the remote site has the IP Range 10.1.0.0/24 then:
zone in-addr-arpa.0.0.10.
SOA for in-addr-arpa.0.0.10 = ns1.localdomain.local
Nameservers = ns1.localdomain.local
zone in-addr-arpa.1.0.10.
SOA for in-addr-arpa.1.0.10 = ns1.site2.localdomain.local
Nameservers = ns1.site2.localdomain.local
The remote site's server will look similar:
zone localdomain.local
SOA = ns1.localdomain.local
NS = ns1.localdomain.local
zone site1.localdomain.local
SOA = ns1.localdomain.local
NS = ns1.localdomain.local
zone site2.localdomain.local
SOA = ns1.site2.localdomain.local
NS = ns1.site2.localdomain.local