[176637] in North American Network Operators' Group
Re: Google public DNS - getting SERVFAIL for any domains delegated
daemon@ATHENA.MIT.EDU (Erik Levinson)
Sun Dec 7 12:46:48 2014
X-Original-To: nanog@nanog.org
Date: Sun, 07 Dec 2014 12:44:36 -0500
From: Erik Levinson <erik.levinson@uberflip.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
In-Reply-To: <20141207171922.GA32179@sources.org>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org
On 07/12/14 12:19 PM, Stephane Bortzmeyer wrote:
>
> Since Google Public DNS validates, and Go Daddy supports DNSSEC, it
> would be useful to test with dig +cd (Checking Disabled) to determine
> if it is a DNSSEC problem or not.
>
Tried, still SERVFAIL. I succeeds with +trace though...
>> You can look at targetly.co as one example (should be just an A
>> record to 184.168.221.38 but getting SERVFAIL when querying
>> 8.8.8.8).
>
> Works for me
>
Maybe a geo-specific issue then, which is even more weird, because it's
still not working for me from two different ASs, though both in Toronto,
and a traceroute makes it appear like they're not hitting the same nodes
(but maybe they are).
What's even more weird is I can actually resolve one domain,
startupong.com, but still not targetly.co and others.
--
Erik Levinson
CTO, Uberflip
416-900-3830
1183 King Street West, Suite 100
Toronto ON M6K 3C5
www.uberflip.com
