<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
-----BEGIN PGP SIGNED MESSAGE----- <br>
Hash: SHA1 <br>
<br>
Hi Ken,<br>
<br>
what exactly do you mean if the .watch tld is owned by our company?<br>
.watch tld is provided by Donuts (<a class="moz-txt-link-freetext" href="http://www.donuts.co/">http://www.donuts.co/</a>). dns.watch
is<br>
the domain name we rent, that is correct. Owning a top-level-domain<br>
would be way too expensive for a small Bavarian company ;)<br>
<br>
We do not provide any "security filters". We want to offer resolvers<br>
where we do not alter any part of the records. Some people requested<br>
this, but right now we do not feel comfortable with it.<br>
<br>
Hope I could answer your questions. Let me know if you have more.<br>
<br>
Sincerely,<br>
German Hoeffner<br>
<br>
DNS.WATCH Administrator<br>
<br>
<br>
<br>
On 17.08.2014 04:32, Ken Peng wrote:<br>
<span style="white-space: pre;">><br>
> Thanks for the info.<br>
> I have two another questions,<br>
><br>
> 1st, does the .watch tld owned by your company fully?<br>
> 2nd, do you provide the security filter as OpenDNS does?<br>
><br>
><br>
><br>
><br>
><br>
> 在 2014-08-16 06:34，German Hoeffner 写道：<br>
> Hello everyone!<br>
><br>
> First of all, a short introduction of myself: My name is
German Hoeffner<br>
> and I'm working for companies in the hosting sector. One of
those<br>
> companies is Ideal-Hosting which I am also a shareholder of.<br>
> Ideal-Hosting UG (haftungsbeschränkt) is a hosting company
located in<br>
> Germany, which has (fortunately) very strict data privacy
law. We're<br>
> involved in many projects which we think the "Internet
community"<br>
> benefits of.<br>
><br>
> I've recently been informed that dns.watch was discussed on
this mailing<br>
> list some time ago. I went through the archive thread (which
you can<br>
> find here:<br>
>
<a class="moz-txt-link-freetext" href="https://lists.dns-oarc.net/pipermail/dns-operations/2014-July/011948.html">https://lists.dns-oarc.net/pipermail/dns-operations/2014-July/011948.html</a>)<br>
> and noticed that there are some open questions.<br>
><br>
> Q: Who is operating DNS.WATCH?<br>
> A: Ideal-Hosting is operating the DNS.WATCH Project as a
not-for-profit<br>
> project. It's important to us that the users and people who
are<br>
> interested in the project know who is running DNS.WATCH and
that they<br>
> can reach us in case any they have any questions or issues
with our service.<br>
><br>
> Q: Why are the resolvers slow from certain locations?<br>
> A: While we're operating an excellent network in Frankfurt,
Germany,<br>
> we're not anycasted (yet). We already have specific plans on
anycasting<br>
> the resolvers and it should go live later this year. However,
we will<br>
> continue to offer explicit Germany only resolver addresses,
as this is<br>
> important for some people.<br>
><br>
> Q: Why is DNSSEC not enabled on dns.watch<br>
> A: It is currently not possible for us to set DNSSEC (DS)
entries with<br>
> the domain api of our registrar. As soon as this is possible,
we'll<br>
> start using DNSSEC.<br>
><br>
> Thanks again for all the suggestions and comments on the
first thread.<br>
> We take all feedback serious, as you can see we've now
enabled mail on<br>
> the domain as well.<br>
><br>
> Questions, anyone?<br>
></span><br>
-----BEGIN PGP SIGNATURE-----
<br>
Version: GnuPG v2.0.22 (MingW32)
<br>
Comment: Using GnuPG with Thunderbird - <a class="moz-txt-link-freetext" href="http://www.enigmail.net/">http://www.enigmail.net/</a>
<br>
<br>
iQEcBAEBAgAGBQJT8NbAAAoJEFXDutqVVa2xWm4H/Rb3DY44Kz0Dy589ssLIb+FT
<br>
c//1NiEonkRIlUK109h6Vek1B+CP0PtkQlb54zop0arNsu5EKqnIOaNGdn69ENNN
<br>
bh4fcDtrqF3SZZIcRsW4KDjg2cb4qZq7Bry/qYsWA92PemuQd20c9J39ZZ5d8uN2
<br>
DmE5a28k8cq79xHEu+ornaaidOl+kjf/rI3rIJljs2OOrL1is0GDf5Q8ppYEW2KU
<br>
uuMGjiRsLZADXbwPI2/peJc5adzSo8Js3DNLaCt7fpAF8/CO84N+YSdVqVHgRxeD
<br>
5xfRGeW5HgfQhyVKQpmp0cqbDfFCE7QpEHu7V1wXwAS1ZM6pV6BDxAUxq6fgW/Q=
<br>
=9QcE
<br>
-----END PGP SIGNATURE-----
<br>
<br>
</body>
</html>