From: "Peter Müller" <peter.mueller@link38.eu>
To: development@lists.ipfire.org
Subject: Re: DNS.WATCH up again
Date: Sat, 04 Aug 2018 19:41:35 +0200 [thread overview]
Message-ID: <8f631e10-548e-ed75-ee4b-b7a1fc4b2473@link38.eu> (raw)
In-Reply-To: <bbbc2323b1b0078b3994ddaf8662cdb4b25a4465.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 3058 bytes --]
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.
(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.
(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...
I am happy with having them deleted from the Wiki list. Will stop using them
during the next few days.
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
>>
>>
--
"We don't care. We don't have to. We're the Phone Company."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-08-04 17:41 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 [this message]
2018-08-05 10:34 ` Michael Tremer
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=8f631e10-548e-ed75-ee4b-b7a1fc4b2473@link38.eu \
--to=peter.mueller@link38.eu \
--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