On 5/5/22 1:35 PM, Maurà cio Penteado via bind-users wrote:
Hi folks,
Hi,
Thank you for the reply.
:-)
Unfortunately, I did not understand how I am supposed to add multiple A-records for the same name to the zone-file to fix this issue.
Based on your first message, you already have multiple A records for ns1.example.lan; 192.168.0.10 and 172.17.0.1.
My suggestion was to have bind order the two records in a way favorable to the requesting client. E.g. if the client is on the 172.17.0.0/24 network, reply with 172.17.0.1 and 192.168.0.10 verses if the client is on the 192.168.0.0/24 network where the response would be 192.168.0.10 and 172.17.0.1. Both get the same A records, just in a different order. Ideally the order puts the optimal IP for the client's use first.
On my Bind9 server, I have the following zone-files: forward.example.lan.db: ns1 IN A 192.168.0.10 ns1 IN AAAA fe80::f21f:afff:fe5d:be90
I don't see the 2nd, Docker (?), address; 172.17.0.1, in the zone. So if your client is still receiving that address in addition to the 192.168.0.10 address, then something else is happening outside of BIND.
-- Grant. . . . unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
-- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
