RE: New BIND 9.16.19 I think don't run with Intel VLANs

Hi Peter, I remember you having this problem before with 9.16.18, did you ever get that version to work? I’ve just upgraded from 9.16.18 to 9.16.19 on Windows Server 2019 without issue but I don’t have any VLANs configured nor am I using an additional network card management application.

Re: Resolve any query to same IP address

Thanks for the answer. Worked here. Thanks! Em qua., 21 de jul. de 2021 às 12:23, Kevin Darcy via bind-users < bind-users@lists.isc.org> escreveu: > [ Classification Level: GENERAL BUSINESS ] > > Dot "." instead of asterisk "*" as the zone name. Remove the "hint" zone, > since that doesn't

Re: query-source and listened interfaces

I understand CDN might need a change. What I don't understand is why single recursive cache somewhere in the middle chain should serve different names to its clients. On 7/13/21 8:19 AM, Xinyu Wang wrote: > Should authoritative servers reply different way to each recursive > server IP? > >

New BIND 9.16.19 I think don't run with Intel VLANs

I have three PC's tested that all work fine on 9.16.15 or 9.17.12 with my Intel VLANs but 9.16.19 simply will not start. Is this a new limitation for BIND on windows now? or a change that causes it not to run if it detects VLANs with the intel APP?

Re: Resolve any query to same IP address

[ Classification Level: GENERAL BUSINESS ] Dot "." instead of asterisk "*" as the zone name. Remove the "hint" zone, since that doesn't apply when you host your own root zone. You need a proper MNAME for the SOA RR too. - Kevin On Wed, Jul 21, 2021 at 11:18

Resolve any query to same IP address

Hi, how can I get the same IPv6 address as the answer to any query to my Bind9? I am using Ubuntu 20 and Bind 9.11 whit configuration as bellow: -- $ cat /etc/bind/named.conf include "/etc/bind/named.conf.options"; include "/etc/bind/named.conf.local"; include