Strange errors from DNS-O-Matic
DnsOMatic returns weird errors from ChangeIP and No-IP:
<html><head><script type="text/javascript">location.replace("https://malware.opendns.com/?url=[redacted]&server=pao15&prefs=&tagging=&nref");</script></head></html>
However, when I use the actual urls (redacted above) for the individual services, they work OK.
I have submitted a ticket over a week ago, but they seem to have deleted it with no response.
Ideas? Suggestions?
-
I have the same problem with the ChangeIP service, sometimes with the DuckDNS service. I have submitted a ticket yesterday. It is still there and still "open".
You can view your tickets here: https://support.opendns.com/hc/en-us/requests
If it is no longer there, you must have formulated it so unluckily that they have treated it as scam.
It looks like the update servers are categorized as malware from a DNS-O-Matic point of view, because what you see as output is the redirection in case a malware domain is being hit.
-
Hi rotblitz,
I formulated it almost exactly like in my post above, except with the actual, non-redacted, URLs, and a polite request to fix it.
I noticed it with DuckDNS too, but it's sporadic, whereas the other two seem to be consistent.
Categorizing the update servers as malware is weird as they are configured by the DnsOMatic team.
-
Hi Guys,
I am also getting the same error using DNS-O-Matic with DuckDNS.
I changed my update interval to 5 minutes so I could troubleshoot easier.
Sometimes it is communicating without error and does update IP as it should, odd.
I will be interested to see what you get back from support, so please do update this thead.Thx
-
I wouldn't hold my breath.
I opened a ticket when yDNS stopped working with DnsOMatic.
After 2 month of back and forth, they told me that "The issue with YDNS has been filed with development, but I don't have an ETA for when it will be addressed."
That was over two years ago, yDNS still does not work.
-
Support came back with the following advice:
Please try the following steps:
- Access your OpenDNS dashboard
- Select the Security tab
- Uncheck the option Enable basic malware/botnet protection checkbox and apply that.
- Then reenable the option and then hit apply.
This has resolved the problem for a number of our clients. Please try this and advise if the problem is resolved or not.
-
Update: The problem seems to be intermittent. I have "Enable basic malware/botnet protection" enabled and just did a manual update, and the update succeeded. I am writing this on 2020/12/04 and my ticket opened on 2020/11/30 is still open, with no comments from the support team as of yet.
-
Can confirm. OpenDNS stuff seems to be stupid and incompetent. I already explained the issue many times to them. They don't understand, that this setting could not solve problem as this setting just would change the behavior for a network using OpenDNS, but meanwhile the code is running on DNS-O-Matic servers, this setting won't effect them. So they seem to have a false positive against themselves and proof, that using their OpenDNS service is no good idea as their malware protection is buggy or minimum has false positives. I again explained once they asked for a screenshot and diagnostics from the sourcing server, I should finally ask for root access to their DNS-O-Matic servers to perform that. However I provided them the mail again and diagnostics from my primary computer, which clearly states, that I use my own Pi-hole with own resolver and Synology with own resolver. Be also very interested in the updates of this thread.
-
On Nov 25 I got the response that escalation to level 2 support took effect for my ticket. I had nothing to do to get it escalated.
Ensure that they don’t wait for a response to your ticket. If you do not react in time, they may close it.
https://support.opendns.com/hc/en-us/requests -
My diagnostics (which are somehow useless) are escalated to Level 2 as well. I hope, there is a more competent supporter. I tried to explain once again, that looking for a bug e.g. on a full street power interruption wouldn't be solved by checking the DVD player and that's somehow similar or checking the light on a house on fire, but I'm afraid, their support has less to none competence and should better work as street worker. They neither understand, what's said or simply ignore it. It's somehow such easy, the checkbox mentioned above seems to be required to be unchecked for the OpenDNS resolvers used on the DNS-O-Matic servers (also it's curious, why they use such resolvers on their servers as this are servers and no clients and e.g. browser malware wouldn't affect such servers), it also shows their servers are useless because of false positives. That's why I use my own Pi-hole instead.
-
The ticket I opened about DuckDNS has not received any comments in a month.
The ticket I opened about ChangeIP and No-IP got deleted from the system.
Actually, all my tickets other than the DuckDNS one got deleted from the system, including the ones about yDNS -- which they haven't fixed in 2.5 years.
I wonder if that was done in spite because I marked one of my previous tickets as "not satisfied" when I closed it. The CSR emailed me to ask why and I replied with a polite explanation. Silly me for assuming they will actually use the feedback to improve their customer service.
-
I got some response from second level support, however, they just recognized some false entries on OpenDNS for a few hostnames and should have been fixed, but I mentioned, that also other DynDNS providers fail. They did not found any false entries and still work on. I also asked, why they use OpenDNS malware protected DNS servers on their DNS-O-Matic infrastructure as it doesn't make sense for me, it just could produce false positives like here but the protection level for a server system (just running update scripts and not surfing the web) wouldn't be such high, that it makes any sense instead of using "normal" or "unfiltered" DNS servers. Still await response after this feedback.
Please sign in to leave a comment.
Comments
40 comments