Re: SRV Record Server Availability

2021-01-06 Thread Mark Andrews
Well mDNS is not DNS. It is a multicast request to all devices on the local network to respond. To get the functionality being requested in the DNS it requires something to be polling the availability of the server listed in the SRV records and to add/remove/adjust them depending upon their

Re: unsubscribe

2021-01-06 Thread Mark Andrews
Send the unsubscribe request to “bind-users-requ...@isc.org” or “bind-users-requ...@lists.isc.org”. Those are the administrative addresses. > On 7 Jan 2021, at 01:07, Michalewicz, Brian R (THIP) > wrote: > > >

Re: SRV Record Server Availability

2021-01-06 Thread Andrew P .
Isn't this sort of dynamic functionality (real-time presence or absence of SRV records) what mDNS and the avahi daemon are for? From: bind-users on behalf of Matus UHLAR - fantomas Sent: Wednesday, January 6, 2021 8:51 AM To: bind-users@lists.isc.org

unsubscribe

2021-01-06 Thread Michalewicz, Brian R (THIP)
** This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended

Re: re:Re: "not subdomain of zone {XXXX} -- invalid response" errors found in named.run log

2021-01-06 Thread 同屋
Actually, the background is a little bit complicated. In short, the topo is as belows. dns1 were swapped by a new one (say dns1*), then the issue happened. After that, we dropped all the request from dns1*, then the issue was gone. There is no config change during the whole process, no

Re: SRV Record Server Availability

2021-01-06 Thread Matus UHLAR - fantomas
On 06.01.21 21:41, Wilfred Sarmiento via bind-users wrote: Your understanding is correct, i just thought that SRV can detect whose server is alive so it can choose and provide an answer with the available Server. DNS is not designed to provide this functionality. While technically you can

Re: SRV Record Server Availability

2021-01-06 Thread Wilfred Sarmiento via bind-users
Hi Tale, Happy new year! Your understanding is correct, i just thought that SRV can detect whose server is alive so it can choose and provide an answer with the available Server. Thank you! On Tue, 5 Jan 2021, 23:53 tale wrote: > On Tue, Jan 5, 2021 at 4:30 AM Wilfred Sarmiento via

re:Re: "not subdomain of zone {XXXX} -- invalid response" errors found in named.run log

2021-01-06 Thread 39223722
Thanksmark,butwhythisissueisrelatedtoloadbalancer? -- Original Message -- From: "Mark Andrews"; Date: 2021-01-06 19:09 To: "同屋"<39223...@qq.com; To: "bind-users"; Subject: Re: "not subdomain of zone {} -- invalid response" errors found in named.run log

Re: "not subdomain of zone {XXXX} -- invalid response" errors found in named.run log

2021-01-06 Thread Mark Andrews
Complain to the administrators of the zone. They have not properly delegated it. We see this often with load balancers. The zone a.b.example has been delegated but the answer is as if it is from b.example. -- Mark Andrews > On 6 Jan 2021, at 21:02, 同屋 <39223...@qq.com> wrote: > >  > The

"not subdomain of zone {XXXX} -- invalid response" errors found in named.run log

2021-01-06 Thread ????
The version of bind is BIND 9.10.5-P3 id:7d5676f One day, I found that the size of named.run is increasing very quickly. And a lot of "invalid response" entries were spotted in the log. Details is as follows (I replace the sensitive info with {},{AAA} etc.) DNS format error from {IP}#53