From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: DNS.WATCH up again
Date: Sun, 05 Aug 2018 11:34:02 +0100 [thread overview]
Message-ID: <bfb8b47add21e3ececdbd51d428f2c2a7f35febb.camel@ipfire.org> (raw)
In-Reply-To: <8f631e10-548e-ed75-ee4b-b7a1fc4b2473@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 4860 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
On Sat, 2018-08-04 at 19:41 +0200, Peter Müller wrote:
> Hello *,
>
> sorry for the late reply.
>
> It was me who added DNS.WATCH services to the DNS server list again as soon
> as they were available again here.
>
> My opinion of this service is as follows:
> (a) Being unavailable for weeks without any notice is certainly a bad sign.
> At least they cannot be considered reliable.
Which is probably one of the most important things when running a DNS
resolver.
> (b) They state "no logging" on their website (we will never know if this is
> true or not) - compared to more commercial services (Google & Co.), this is
> at least something.
It is a promise. Just like Google promised to never be evil... I am
quite confident that promises like those are being breached a lot.
> (c) Well, technically, they did not tried to manipulate DNS replies or something
> similar. The JavaScript on their website is funny of course, but it seems to
> be "just" for analytics...
Luckily nobody has to visit the website to use the DNS servers.
But there is a company behind it who's website doesn't load. No idea
what they are doing. IT is not their main business. I do not see why
anyone should be using this when there is so many alternatives around.
> I am happy with having them deleted from the Wiki list. Will stop using them
> during the next few days.
Okay.
It doesn't mean that nobody should be using them, but certainly we
won't recommend them any more.
- -Michael
>
> Thanks, and best regards,
> Peter Müller
>
> > Yes, I agree. We should remove them from the list.
> >
> > Not because of that bit of JS there (which is funny in itself), but basically
> > because they are unreliable and nobody knows who is behind it and how to get in
> > touch with them. At least that is my perception of all of this.
> >
> > And it is not that there are no alternatives. There are plenty and people should
> > choose from there.
> >
> > Best,
> > -Michael
> >
> > On Fri, 2018-07-20 at 20:09 +0200, Matthias Fischer wrote:
> > > Hi,
> > >
> > > On 20.07.2018 17:35, Michael Tremer wrote:
> > > > I have seen that you have re-added them on the wiki, too.
> > > >
> > > > Is this a trustworthy DNS provider?
> > >
> > > Jm2C:
> > > They failed on Februar, 4th for about two days and now again -
> > > even longer - without any comment.
> > >
> > > Besides, I found some intersting comments during searching here:
> > > https://forum.kuketz-blog.de/viewtopic.php?f=32&t=187 (german)
> > >
> > > The code mentioned there ist still present on their site:
> > >
> > > ...
> > > <!-- Ideal-Hosting Analytics -->
> > > <script type="text/javascript">
> > > var _paq = _paq || [];
> > > _paq.push(['trackPageView']);
> > > _paq.push(['enableLinkTracking']);
> > > (function() {
> > > var u=(("https:" == document.location.protocol) ? "https" : "http") +
> > > "://analytics.ihgip.net/";
> > > _paq.push(['setTrackerUrl', u+'piwik.php']);
> > > _paq.push(['setSiteId', 38]);
> > > var d=document, g=d.createElement('script'),
> > > s=d.getElementsByTagName('script')[0]; g.type='text/javascript';
> > > g.defer=true; g.async=true; g.src=u+'piwik.js';
> > > s.parentNode.insertBefore(g,s);
> > > })();
> > > </script>
> > > <noscript><p><img src="http://analytics.ihgip.net/piwik.php?idsite=38"
> > > style="border:0;" alt="" /></p></noscript>
> > > <!-- End Ideal-Hosting Analytics -->
> > > ...
> > >
> > > IMHO we should delete this entry.
> > >
> > > Best,
> > > Matthias
> > >
> > > > -Michael
> > > >
> > > > On Thu, 2018-07-19 at 19:35 +0200, Peter Müller wrote:
> > > > > Hello,
> > > > >
> > > > > looks like both DNS servers and website are up again.
> > > > >
> > > > > Best regards,
> > > > > Peter Müller
> > >
> > >
>
>
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE5/rW5l3GGe2ypktxgHnw/2+QCQcFAltm0poACgkQgHnw/2+Q
CQcKAQ/+JxyA5TY7EtISMbhtUNHXLFMeP4TCU4CdegbmppVLQ5UnppXc1I7BkGbh
Nyo+G7rs9lZREmBVJ+RR48dT3ZLJTCT3X5T/qNXVKKuzpttX4r6kO+CkCME9JlFz
p2zHInlxQpgHPiGLBOhhvU219glsgfR7zdCnc45RxBQ7WrivdsznxW0TcKbpR1q6
lmdB7+N0hk4vYGk1SkBk3E+3gtUnTbRnbI95ezlUJBo0ccgKnp6EcOs0ffNbOI7f
RJwDe/qoIvoqxNGiCaGGyh8FuosmdonBvrVchbFWyhYUxQiSFutSBlPLnFWCGWAl
2coi5Hry0d4lBmW4qCwOh7MnRw1qpaR8OjuEpFkGm4X+FTMRm+LGHRitQ405VRWZ
rsHS04lNevN+3KN3trPiOwH7j+7A9/9+ubWuJI73qLW70BRE0AMZEzdFN9w1ReIN
oIC8KkQZXAO1GJMRET3vv4SzXT7zSI5sas/Q07njwpyGaTxk+5gwWD+NhkN3IUzd
7kTs962Q8KWqgeIJAKDg5CfKcDj43AdBtjbelqjvfLzVU/S5Q4Xs2PDECpSxF6Gd
g2Fd59+IL5m7Xj9USmCGjLjVmih7e5knF02zpD62X2UzFwdXI1XdJPRf/T4VD7eP
GGjx+4NgJVeWUdwfiW0D3aShNCW20axvDnfzjOoyRVfIv1gvXPk=
=nga3
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2018-08-05 10:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-14 10:29 81.3.27.54 => rDNS => Reverse lookup failed Matthias Fischer
2018-07-14 13:34 ` Michael Tremer
2018-07-14 16:27 ` Matthias Fischer
2018-07-16 15:02 ` Peter Müller
2018-07-16 16:48 ` Michael Tremer
2018-07-19 17:35 ` DNS.WATCH up again (was: Re: 81.3.27.54 => rDNS => Reverse lookup failed) Peter Müller
2018-07-20 15:35 ` Michael Tremer
2018-07-20 18:09 ` DNS.WATCH up again Matthias Fischer
2018-07-21 11:17 ` Michael Tremer
2018-08-04 17:41 ` Peter Müller
2018-08-05 10:34 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bfb8b47add21e3ececdbd51d428f2c2a7f35febb.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox