This should be fixed now. Sorry that this was not a April Fools day joke :)
Yunhong
On Wed, Apr 1, 2015 at 11:21 AM, Yunhong Gu wrote:
> Thanks, I am investigating.
>
> On Wed, Apr 1, 2015 at 11:17 AM, Brett wrote:
>
>> 1 gw-vlan100 (213.248.204.1) 0.512 ms 0.320
On Mon, Mar 9, 2015 at 10:58 PM, Mark Andrews wrote:
>
>
>
> In message <
> cagmqtqjrpx_xg_ojtshsw5yqaefkzwdma16xw7iry9pr0_f...@mail.gmail.com>
> , Yunhong Gu writes:
> >
> > Returning NOTIMP may confuse resolvers as it is not clear "what is not
> >
Returning NOTIMP may confuse resolvers as it is not clear "what is not
implemented". A NOTIMP response to an ANY query with EDNS0 option could
cause a retry-without-EDNS0 query, or mislead the resolver to believe that
the nameserver does not support EDNS0.
Yunhong
On Fri, Mar 6, 2015 at 2:10 PM,
Hi, Adam
I am on the team of Google Public DNS. Thanks for the report. We will
check Australia related service. (No, this is definitely not
intentional). You can also open a ticket here
(https://developers.google.com/speed/public-dns/groups) if the problem
persists.
Thanks
Yunhong
On Tue, Oct 2,
