Re: intermittent SERVFAIL for high visible domains such as *.google.com

2018-01-23 Thread Brian J. Murrell
On Mon, 2018-01-22 at 12:45 +, Tony Finch wrote: > > lame-servers is also a log category, and tends to be quite noisy > about > various problems :-) Turns out I do already have lame server logging enabled. I.e.: 20-Jan-2018 12:01:37.053 lame server resolving 'backup-ns.yn.cninfo.net' (in '

Re: intermittent SERVFAIL for high visible domains such as *.google.com

2018-01-23 Thread Brian J. Murrell
Here's a new most interesting data point. All of these outages happen right after a DHCP client connect and sends a DDNS update to BIND. It would be an interesting experiment to isolate the zone that receives DDNS updates for the DHCP clients onto a separate server to see if that makes this probl

Re: intermittent SERVFAIL for high visible domains such as *.google.com

2018-01-23 Thread Reindl Harald
Am 23.01.2018 um 13:25 schrieb Brian J. Murrell: Here's a new most interesting data point. All of these outages happen right after a DHCP client connect and sends a DDNS update to BIND. It would be an interesting experiment to isolate the zone that receives DDNS updates for the DHCP clients on

Re: intermittent SERVFAIL for high visible domains such as *.google.com

2018-01-23 Thread Niall O'Reilly
On 23 Jan 2018, at 12:25, Brian J. Murrell wrote: > I don't think it's possible > to run two BINDs on the same machine on different ports and have one > (on port 53) delegate a zone to another running on some other port. You could use different __addresses__, if you have any to spare. Best regar

Re: intermittent SERVFAIL for high visible domains such as *.google.com

2018-01-23 Thread Brian J. Murrell
On Tue, 2018-01-23 at 13:38 +0100, Reindl Harald wrote: > > pretty sure it's possible and likely not much different than the > unbound-sample below which asks a rbldnsd on port 1043 on the same > machine > > stub-zone: > name: "zone-name." > stub-addr: 127.0.0.1@1053 That's the sort of path

Re: intermittent SERVFAIL for high visible domains such as *.google.com

2018-01-23 Thread Brian J. Murrell
On Tue, 2018-01-23 at 13:38 +0100, Reindl Harald wrote: > > pretty sure it's possible and likely not much different than the > unbound-sample below which asks a rbldnsd on port 1043 on the same > machine > > stub-zone: > name: "zone-name." > stub-addr: 127.0.0.1@1053 This all falls apart be

Re: intermittent SERVFAIL for high visible domains such as *.google.com

2018-01-23 Thread Grant Taylor via bind-users
On 01/23/2018 05:25 AM, Brian J. Murrell wrote: It would be an interesting experiment to isolate the zone that receives DDNS updates for the DHCP clients onto a separate server to see if that makes this problem go away for the main server, but I don't have another machine to run another BIND on

Re: intermittent SERVFAIL for high visible domains such as *.google.com

2018-01-23 Thread G.W. Haywood via bind-users
Hi there, On Tue, 23 Jan 2018, Grant Taylor wrote: ... I'm sure that you could do some networking magic to cause connections to $AlternateIP port 53 to be re-routed to $DifferentIP $AlternatePort. http://netcat.sourceforge.net/ -- 73, Ged. ___ Ple

Re: intermittent SERVFAIL for high visible domains such as *.google.com

2018-01-23 Thread Brian J. Murrell
On Tue, 2018-01-23 at 09:53 -0700, Grant Taylor via bind-users wrote: > > Could you try disabling DDNS updates for a little while? That's effectively what I have done. I set up a second server configuration running new zone on a different IP address and pointed the DHCP server at it so that the