Localise queries

[A. Schulze]

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"

Using the dig (or nslookup) command you can check if the expected answers are given.

> 	When I connect to the wifi(192.168.2.0/24), and I ping
> gw.router.mydomain.com, the answer is showing 192.168.1.1, instead of
> 192.168.2.1.

"ping gw.router.mydomain.com" instruct your OS to

1. resolve the name to a list of IPv4 and IPv6 addresses
2. chose one of them and send ICMP echo requests

Your OS choosed 192.168.1.1 ...

Andreas