I setup a BIND9 DNS server in the LAN as a backend to Samba4 service. The network address of my LAN is 192.168.2.0/24 and I statically specify the IP address of DNS server as 192.168.2.144.
Unfortunately, there is another MIC on my DNS server (in fact, the DNS server is a virtual box, the extra MIC is the virtual bridge). They are in different network, the network address of the virtual bridge is 192.168.122.0/24.
I bind a domain name dc.foo.bar to the static address 192.168.2.144 in /etc/named.conf. However, when I query the DNS information with host -t A dc.foo.bar, two entries are returned, one is 192.168.2.144 while the other is 192.168.122.1.
I don't want dc.foo.bar binds to 192.168.122.1, neither do I know how it is added into the DNS service. How could I trouble shot the problem and remove the erronous DNS address entry?
I paste the result from dig for reference
[root@dc ~]# dig A dc.foo.bar ; <<>> DiG 9.8.2rc2 <<>> A dc.foo.bar ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62496 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;dc.foo.bar. IN A ;; ANSWER SECTION: dc.foo.bar. 900 IN A 192.168.122.1 dc.foo.bar. 900 IN A 192.168.2.144 ;; Query time: 1 msec ;; SERVER: 192.168.2.144#53(192.168.2.144) ;; WHEN: Sun Aug 11 22:12:03 2013 ;; MSG SIZE rcvd: 72
I double check the samba log and bind configure.
I'm quite sure the problem is introduced by samba.
In samba configure file, there is a parameter
interfaces in global section.
Initially, I left it defaults and I find the address 192.168.122.1 is resolved by the internal bind from samba log.
I then specified it interfaces = eth0, i.e. only the physical NIC should be resolved.
Now from the samba log, 192.168.122.1 is not loaded ever.
However, dig still returns both address for dc.foo.bar.
So the problem may be a deprecated entry in
Any idea about it so I can reconstruct the
Thank you in advacne!