OpenDNS Forums
The official support and discussion site of OpenDNS
Support
K-12 Forums
Categories
- Administrative
- Adult site blocking
- DNS-O-Matic / dynamic IPs
- Domain blocking
- Domain Name System (DNS) troubles
- Mobile instructions
- OpenDNS services
- Proxies, accelerators, and more
- Router instructions
- Satellite
- Shortcuts
- Wishlists and feature requests
-
Feeds
Vanilla 1.1.4 is a product of Lussumo. More Information: Documentation, Community Support.
This discussion has been inactive for longer than 30 days, and is thus closed.
-
- CommentAuthorpeterdynip
- CommentTimeJun 26th 2009
Sometimes are there Errors without description, then I have to force an Update from DNS Allocator 1 or 2 times and it is working.
But that is very bad, because then all the time the filter is not working and all sites are available. -
"Errors without description"
In DNS-O-Matic click the history icon of the related service in error. You will see something like:
---
DynDNS details:
Errors requiring your attention
abuse
History
79.211.xxx.xxx, Jun 1, 2009 10:21 am, ERROR
---
In this example "abuse" is the error description. What is it in your case? -
AdministratorDNS Allocator is not a supported method for updating your OpenDNS account. Please try downloading an update client from http://www.opendns.com/support/article/90Thankful People: Brian Hartvigsen
-
- CommentAuthorpeterdynip
- CommentTimeJun 26th 2009
No, update client I don't want to have.
The history from DNS-O-Matic:
84.171.xx.xxx, Jun 25, 2009 3:37 pm, OK
84.171.xx.xxx, Jun 25, 2009 3:21 pm, OK
84.171.xx.xxx, Jun 25, 2009 2:30 am, ERROR
84.171.xx.xxx, Jun 25, 2009 2:24 am, ERROR
In DNS Allocator is sometimes said:
nohost but with a few tries more it is successful, but DNSomatic still has an error. -
@peterdynip
"nohost"
What did you set up as "host" for DNS-O-Matic in DNS Allocator? If you want to cover all services, it must be all.dnsomatic.com.
And yes, for past errors you don't get a description, only for the most recent one. However, you can set up DNS-O-Matic to send you e-mail notifications, always or just in case of errors, so you would be able to see the error description.
"update client I don't want to have."
Why not? What are your special requirements? And why not send updates from your router directly to DNS-O-Matic, in case you have more than one DDNS service to update?
@miked
"DNS Allocator is not a supported method ..."
Yes, confirmed, exactly since today.
Let's see if you fixed the other bug with abusive updates at this occasion, else DNS-O-Matic is now totally useless for me...
-
I have been relying on DNS Allocator for over 12 months for updating my OpenDNS account and it has worked very well. Reason for using it? All computers are Linux. The ADSL router updates DynDNS and from there DNS Allocator updates DNS-O-Matic. So can someone suggest what my alternatives are other than doing a manual update?
Unfortunately manual updates is not satisfactory as I am not always in a position to access OpenDNS from our network. For example, Today I have just accessed my computer for the first time, and received notification from DNS-O-Matic about the IP mismatch sent over 7 hours ago. In the meantime other computers have been in use all that time. So for 7 hours, we've had no filtering at all.
Suggestions please. -
- CommentAuthormaintenance
- CommentTimeJun 27th 2009
http://ubuntuforums.org/showthread.php?t=566698
I'm sure you could script it to be run by cron as well.Thankful People: nzkiwi -
Thankyou maintenance
It's a start. I've never tried scripting under Unix, and it's many years since I even wrote a DOS batch file, but I'll give it a go.
In the Ubuntu forum thread inadyn is used to update DynDNS, but as my ADSL router does that job, I can dispense with that part. The script uses inadyn to update DynDNS, then fetches the IP address and updates OpenDNS. I'm sure I can work something out that will suit my purpose. -
- CommentAuthorpeterdynip
- CommentTimeJun 27th 2009 edited
The update program I can't use because I am not allowed to install it on all computers.
And my PC is not used every day.
I configured in DNS Allocator all.dnsomatic.com and at the begin it worked.
But now since 2 days it isn't working, this morning I have the problem too.
DNS Allocator has already the right IP but DNS O Matic not.
That is written in the DNS-O-Matic mail:
OpenDNS response for 'Home':
--------------------
The IP Address you have supplied to DNS-O-Matic
differs from the IP Address that you are coming from.
OpenDNS does not allow you to update to an IP Address
that you don't actually own.
--------------------
"And why not send updates from your router directly to DNS-O-Matic, in case you have more than one DDNS service to update?"
how is that possible? -
'"And why not send updates from your router directly to DNS-O-Matic, in case you have more than one DDNS service to update?"
how is that possible?'
That depends on your router. My Belkin router Has a DDNS section in the configuration menu, with a choice of either DynDNS.org or TZO.com. So in my case directly updating DNS-O Matic via the router is not an option
-
- CommentAuthormaintenance
- CommentTimeJun 27th 2009
http://www.opendns.com/support/dynamic_ip_downloads/
Instructions on using DynDNS Updater with OpenDNS can be found here.
http://www.opendns.com/support/article/187
http://www.dyndns.com/support/clients/windows.html
http://www.dyndns.com/
http://www.dyndns.com/support/clients/hardware/
http://www.dyndns.com/support/clients/noncertified/
I guess I'd look at the hardware, non certified. This is the Belkin router listed:
http://www.dyndns.com/support/clients/noncertified/f5d8233-4.html
Follow the various instructions per you router, though they are shown for the update client rather than on of the OS clients. -
- CommentAuthorpeterdynip
- CommentTimeJun 27th 2009
http://sonium.blogspot.com/2008/02/opendns-fritzbox-howto.html
that is an instruction for dnsomatic directly updating via fritzbox
I hope it will work now -
- CommentAuthorpeterdynip
- CommentTimeJun 27th 2009 edited
after restarting fritzbox it is working!
1 to 13 of 13
This discussion has been inactive for longer than 30 days, and is thus closed.
