I posted a question on this problem: https://www.experts-exchange.com/questions/29019573/Cannot-get-DNS-to-use-2-hosts-for-the-same-IP.html
, thought it was solved, and closed it. I did so too soon, so now I'm posting again.
I am running Slackware64 14.2, Samba 4.4.13 and BIND 9.10.4-P6 on host 192.168.0.2. This host is the Active-Directory/Domain controller for our office Windows domain.
Lately, I added a VirtualBox XP guest virtual machine to the domain running SQL Server 2005 to service a legacy application. The virtual machine implements a virtual "router" which dhcp assigns an IP to the XP: 10.0.2.15 (host name: traverse). In the VM I have configured port-forwarding to forward requests made to the Linux VM host (192.168.0.2) on port 1433 to the VM port 1433.
From domain workstations you cannot access the SQL Server via 10.0.2.15:1433. You can, however, access the SQL Server via 192.168.0.2:1433.
No problem, I thought. I created an 'A' record in the zone file as:
TRAVERSE A 192.168.0.2
so now there are two hostnames that resolve to 192.168.0.2. That worked ... for a while. Initially, the host command gave:
$ host traverse
TRAVERSE.hprs.local has address 192.168.0.2
Domain workstations were able to access the SQL Server on the XP virtual machine. However, after some period of time that changed:
$ host traverse
TRAVERSE.hprs.local has address 10.0.2.15
Something is changing the DNS entry for this host from 192.168.0.2 to 10.0.2.15. What? In the logfile I have the following, which might provide a clue: