It is possible and perfectly desirable. On the Linux machines:
- Add
search plumnicoll.family to your /etc/resolv.conf
On the Windows machines (instructions for Windows XP, other versions will require adaptation but should be similar):
- go to Start > Settings > Network Connections
- right-click local network connection > Properties
- left-click Internet Protocol (TCP/IP)
- left-click Properties
- left-click Advanced
- left-click DNS tab
- left-click Append these DNS suffixes
- left-click Add
- type plumnicoll.family
- left-click Add
- left-click OK
- left-click OK
- left-click OK
This is either
- a DNS configuration problem (at remote location)
- a DNS server problem (wrong views)
- a translating firewall problem
Scenario 1:
Make sure the remote location accesses the same (internal) DNS server that the main location uses. Test with
dig @internal-DNS-ip internal.website.com
and make sure that the ending ";; SERVER:" output repeats that IP. Does the answer contain the private IP address?
Possible scenario: the hosts at your remote location are instructed to contact a DNS server other than the internal one.
Fix: configure the remote location computers (or the DHCP server for them) to use the internal DNS.
Scenario 2:
Make the same "dig" query from a computer at main location. Do you get the private IP addresses?
Possible scenario: views instruct the internal DNS server to respond X to some clients and Y to the rest. The new link entailed new IP addresses for the remote location, and the view mask on the internal DNS server has not been updated.
Fix: update the address mask for the view @ internal DNS.
Scenario 3:
Some routers snoop into DNS responses and, when they find your public IP address matching an internal NAT, they replace it to the local address.
Possible scenario: the DNS replies always with the public address (no views), but queries from main location go through such router and queries from remote location do not.
Fix: configure views @ internal DNS so that all internal hosts receive the internal website IP natively.
Best Answer
Yes, slave should be the same as master in all regards, except that it has a reference to master to feed for any other changes. The purpose of a slave DNS is exactly to continue doing what master was doing until it failed.