-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I looked at this, and the man page LIES. --interface-name returns all the addresses associated with an interface.
Question: is openWRT associating the same name with more than one interface (which would be the only way that localise-queries would make sense, if you believed the man page.) ie interface-name=myrouter,eth0 interface-name=myrouter,eth1 localise-queries and expecting to get the address of eth0 or eth1, depending on where the query was sent to. If it is, then it's probably working by accident, but I have to make sure that doesn't break; Cheers, Simon. On 01/02/17 13:41, Kevin Darbyshire-Bryant wrote: > > > On 17/01/17 04:05, Eric Luehrsen wrote: >> Hi Kevin, >> >> Reading the man page, I would expect the primary address is >> returned (localized) and it acts just like any /etc/hosts entry. >> This would imply that this is a bug or oversight. >> >> quote: -interface-name=<name>,<interface>[/4|/6] Return a DNS >> record associating the name with the __ primary address __ on the >> given interface. This flag specifies an A or AAAA record for the >> given name in the __ same way as an /etc/hosts line __, except >> that the address is not constant, but taken from the given >> interface >> >> >> (I don't use router DNS that specifically, so I failed to test >> this detail before submitting to LEDE. ) >> >> Eric > > Hi Eric, > > Sorry for the the late reply - I've been distracted by many other > things. Your recent lede/dnsmasq.init changes are absolutely > wonderful and really useful. If it weren't for this 'featurette' > of localised queries not working, it would be perfect. > > I wonder if Simon could be persuaded to look into this ready for > 2.77? > > :-) > > Kevin > > >> >>> Kevin Darbyshire-Bryant Wed, 11 Jan 2017 10:24:34 -0800 Hello >>> All, Recently LEDE changed the way it allocates names to >>> interfaces, now using '-interface-name' rather than putting >>> names in /etc/hosts or similar. Unfortunately this new method >>> appears incompatible with 'localise-queries' in that all >>> interfaces/aliases are included in the reply to 'nslookup >>> hostname' and not in a 'preferred local interface' order. Is >>> this an oversight/feature/bug? Cheers, Kevin >> _______________________________________________ Dnsmasq-discuss >> mailing list Dnsmasq-discuss@lists.thekelleys.org.uk >> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss >> > > _______________________________________________ Dnsmasq-discuss > mailing list Dnsmasq-discuss@lists.thekelleys.org.uk > http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBCAAGBQJYk1XfAAoJEBXN2mrhkTWiXhUQAJfYoPb9i/egmOf1d417TdOF hX0khXuboOHObp+6FK7QREduQ7yCG1QbdxSKNJPWT6q3GBotYSwmfSd9F/EETyBs /OGRhvBZtk2kFyf79tJvLBNtJAOcmm8ml9K8mOl/NYtBP6yYkwwjcYXUEp9dLKUB xuS+MPvI4Z1+DqmrDkmayevfgwRLuz1S+0SmMBMo+K6yZ2853HwKGBh7+U5+ZBB8 DfwFsriisJbSc2EG5RJBGuXH7aclB3+5+8UAMdgmT68/M2Eb9icnjqpJMLF90nm7 h3sEz4YtBDVeVm1ki4cpbtzFCOouZfEpe/jekHSRtwycH+dm51W/T2kTPCjg2shk aNfLxQURZcVrx0ZhbZkyk0zFmbchHWuhWY9KDn93jcwyU4ESkf44t2A0hhFAn6Xp bu37/7ZdYmBekTaO7PohRtFcCmTe9oRXhfYDTzgbEG+cbWb1ITf4rvJPaj4x9ZVN vkVCWd54UF7CV1t/tgfBtEldNDkwkxxm6a0kxdi7q1B5mis6fig79Aj9Yu+GrXdI j3Jmb/TTQzjtFGqiK7zjOXBinZa+j+ih1nzrn4qupz20pXf8RlwCf7fV4M5qi5E2 ogx4VkiIDgLvLouGRZ8/o8R78JK1jppuTwazRUywbl4HkZJ5ZbTRv6mQ5ZVMuw2D PjHoM4/xBls7wsU6wDrg =vMD4 -----END PGP SIGNATURE----- _______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss