On Sat, 14 Aug 2021 at 14:46, A. Schulze via Unbound-users < [email protected]> wrote:
> > > Am 14.08.21 um 11:30 schrieb José Ramón Muñoz Pekkarinen via Unbound-users: > > > local-data: "router.mydomain.com. IN A 192.168.1.1 192.168.2.1 > 192.168.3.1 > > fd01:5f3b:820e::1" > > local-data: "gw.router.mydomain.com A 192.168.1.1 192.168.2.1 > 192.168.3.1 > > fd01:5f3b:820e::1" > > this looks like invalid to me, (but may be wrong) > I would write this as: > > local-data: "router.mydomain.com. IN A 192.168.1.1" > local-data: "router.mydomain.com. IN A 192.168.2.1" > local-data: "router.mydomain.com. IN A 192.168.3.1" > local-data: "router.mydomain.com. IN AAAA fd01:5f3b:820e::1" > local-data: "gw.router.mydomain.com. IN A 192.168.1.1" > local-data: "gw.router.mydomain.com. IN A 192.168.2.1" > local-data: "gw.router.mydomain.com. IN A 192.168.3.1" > local-data: "gw.router.mydomain.com. IN AAAA fd01:5f3b:820e::1" > Hi, Thanks for the answer, you are totally right with this, I just missed that ipv6 entries are AAAA instead of A, so when I tested this approach unbound didn't start at all. After doing this config change it starts nicely and returns the right ip over ping and dig: # ping gw.router.mydomain.com PING gw.router.mydomain.com (192.168.2.1) 56(84) bytes of data. 64 bytes from 192.168.2.1 (192.168.2.1): icmp_seq=1 ttl=64 time=1.98 ms 64 bytes from 192.168.2.1 (192.168.2.1): icmp_seq=2 ttl=64 time=4.44 ms Thanks! José.
