Re: 9.18 BIND not iterated over all authoritative nameservers

2023-10-28 Thread Paul Stead
be different. Please do not > feel obligated to reply outside your normal working hours. > > On 28. 10. 2023, at 17:50, Paul Stead wrote: > >  > As a previous ISP admin I too have come across similar situations and > frustrations. > > I can only say that Google and Cl

Re: 9.18 BIND not iterated over all authoritative nameservers

2023-10-28 Thread Paul Stead
As a previous ISP admin I too have come across similar situations and frustrations. I can only say that Google and Cloudflare seem to follow Postel's Law moreso than BIND. I agree this perpetuates bad practices but end users aren't interested in technical reasoning, especially when "it works ever

Re: Correlation between NOTIFY-Source and AXFR-Source

2023-03-11 Thread Paul Stead
op of the list. Anand has done a better job at describing this function in other software than my attempts Paul On Sat, 11 Mar 2023, 17:16 Grant Taylor via bind-users, < bind-users@lists.isc.org> wrote: > Hi Paul, > > Thank you for explaining. > > On 3/10/23 12:21 AM, Pau

Re: Correlation between NOTIFY-Source and AXFR-Source

2023-03-09 Thread Paul Stead
On Thu, 9 Mar 2023, 23:53 Grant Taylor via bind-users, < bind-users@lists.isc.org> wrote: > On 3/9/23 2:25 PM, Paul Stead wrote: > > Chiming in to say +1 to Kalus' logic and sight of benefit here. > > Please forgive my ignorance in asking: > > Why doesn't

Re: Correlation between NOTIFY-Source and AXFR-Source

2023-03-09 Thread Paul Stead
On Thu, 9 Mar 2023, 20:27 Klaus Darilion via bind-users, < bind-users@lists.isc.org> wrote: > > -Ursprüngliche Nachricht- > > Von: bind-users Im Auftrag von Mark > > Andrews > > Gesendet: Donnerstag, 9. März 2023 21:04 > > > > Named just uses the notify to trigger an early refresh process

Re: Problem resolving a domain

2022-05-13 Thread Paul Stead
t; > On 13 May 2022, at 22:58, Paul Stead wrote: > >  > Further to this, I've discovered that disabling DNS cookies also seems to > help with resolution - > > $ dig +nocookie +timeout=1 +retries=0 IN A > myapplication.glbaa.barclays.com. @ns21.barclays.com. >

Re: Problem resolving a domain

2022-05-13 Thread Paul Stead
e DNS software seem to fall back gracefully and resolve these problems Paul On Fri, 13 May 2022 at 13:51, Paul Stead wrote: > I have noticed this, too, > > The problem seems to be related to edns - disabling edns for the upstream > servers looks to resolve the issue, this can be seen with

Re: Problem resolving a domain

2022-05-13 Thread Paul Stead
I have noticed this, too, The problem seems to be related to edns - disabling edns for the upstream servers looks to resolve the issue, this can be seen with later versions of dig - $ dig *+noedns* +timeout=1 +retries=0 IN A myapplication.glbaa.barclays.com. @ns21.barclays.com. I have config alo