Hey folks,
Thank you all for the replies. Initially I expected that dhcp-option
would work dynamically or take effect every time the IP of an upstream
server was changed. This was a misunderstanding. If understood right
from all the replies, dhcp-option plays a role only when a dhcp request
On 2020-07-30 08:09, wkitt...@gmail.com wrote:
On 7/29/20 7:59 PM, Dan Schaper wrote:
You've told dnsmasq to send a lease with option 6 (DNS) set to
10.88.13.3. Where dnsmasq forwards the queries to is not relevant to
your issue, you only have one upstream server configured.
are you saying
On Thu, Jul 30, 2020 at 02:20:42PM +, Horn Bucking wrote:
>
> On 7/30/20, wkitt...@gmail.com wrote:
>
> > On 7/29/20 7:59 PM, Dan Schaper wrote:
> > > You've told dnsmasq to send a lease with option 6 (DNS) set to
> > > 10.88.13.3. Where dnsmasq forwards the queries to is not relevant to
> >
Yes, basically this is what's happening.
The amount of addresses vary on the lo0 interface, depending on how many
jails are fired up with a respective IP address, so I can't tell. Right
now I have around 30 of them, but since I manage them with the
aforementioned ansible scripts, they can be more
On 7/30/20, wkitt...@gmail.com wrote:
On 7/29/20 7:59 PM, Dan Schaper wrote:
You've told dnsmasq to send a lease with option 6 (DNS) set to
10.88.13.3. Where dnsmasq forwards the queries to is not relevant to
your issue, you only have one upstream server configured.
are you saying that
On 7/29/20 7:59 PM, Dan Schaper wrote:
You've told dnsmasq to send a lease with option 6 (DNS) set to
10.88.13.3. Where dnsmasq forwards the queries to is not relevant to
your issue, you only have one upstream server configured.
are you saying that this
