Re: DNS not resolving on google, but is on other services

2018-02-18 Thread @lbutlr
On Feb 17, 2018, at 06:04, Reindl Harald wrote: > "Is google just b0rked?" is mostly wrong to start with As I said, that seems unlikely. But the different behavior from multiple large DNS services was odd. > Delegation > > Failed to find name servers of david-dodge.com/IN. I may have been muc

Re: DNS not resolving on google, but is on other services

2018-02-18 Thread @lbutlr
On 2018-02-17 (02:48 MST), Niall O'Reilly wrote: > > In my not-very-extensive experience, Google's 8.8.8.8 service seems to have > limited tolerance of badly-behaving authority servers; in such a case, it > seems to give up early and report SERVFAIL. > > As it happens, there seem to be problem

Re: DNS not resolving on google, but is on other services

2018-02-17 Thread G.W. Haywood via bind-users
Hi there, On Sat, 17 Feb 2018, LuKreme wrote: ... Is google just b0rked? ... You might need to look closer to home. You claim three nameservers, but it appears that they're all on the same network segment - a *really* bad idea - and one of them doesn't respond to DNS requests, using IPs loca

Re: DNS not resolving on google, but is on other services

2018-02-17 Thread Niall O'Reilly
On 16 Feb 2018, at 23:23, LuKreme wrote: > Is google just b0rked? (Seems unlikely) or is there something in the > configuration for the dns that they don't like? In my not-very-extensive experience, Google's 8.8.8.8 service seems to have limited tolerance of badly-behaving authority servers; in