Unsure, but see the manual page
http://www.mikrotik.com/testdocs/ros/3.0/system/ddns.php

Whereas this is intended to keep a domain name in sync with your dynamic IP address, perhaps it can be used to keep your IP address in sync with OpenDNS, either directly or via DNS-O-Matic. Not sure if the MicroTik OS will let you use the command this way or not.

If you can run this in a script, you are probably in business.

hxxps://username:password@updates.opendns.com/nic/update?hostname=network label
(replace xx with tt)

username = your username
password = your password
network label = your network label


[edited to break link per the rotblitz method]

I am assuming that is not your actual password, right? (Good. )

If you send the same through a browser address bar, does it work?

What change are you expecting? Has you IP been updated if you check your Dashboard?
If not, ensure that password and username are entered exactly as you have them in your Dashboard and OpenDNS Updater (capitalization counts).

Are you using OpenDNS at all? http://welcome.opendns.com

If the problem is simply that blocking seems not to work, clear your browser cache and local resolver cache. http://www.opendns.com/support/article/209

If you ISP uses a proxy of some sort, OpenDNS filtering may not work for you.

If none of my suggestions are of help, you may wish to check back later when others have had a chance to see your post. Realize, also, that your dynamic IP probably does not change all that often, and it would be fine to simply have the Updater start when your PC does. (Many users do not keep their PC running 24 hours a day, and it is not a problem.)

Best of luck in getting this working to your satisfaction.

"good 41.235.12.62"
This is what must be returned by OpenDNS. This is the confirmation for having updated the IP address in your dashboard.

Back to the update URL and process:

1. Your client (e.g. mikrotik 2.9) must support TLS/SSL to update OpenDNS.
http://www.opendns.com/support/article/83
http://www.opendns.com/support/article/88
If it does not, you can go through DNS-O-Matic (http://www.dnsomatic.com/).

2. Your client must be able to support HTTP Basic Auth. A browser (or Windows Explorer) can derive user ID and password from the URL, but this is not how it works technically or with most other clients. At the server end, the user ID and password must not be part of the URL.
http://forums.opendns.com/comments.php?DiscussionID=4024#Item_12
http://forums.opendns.com/comments.php?DiscussionID=4029#Item_6

"i put some thing in DNS when i site blocking
this line
/ ip dns static
add name="www.block.opendns.com" address=74.125.67.100 ttl=1d
this make the blocked page go to www.google.com"

Sorry, what exactly do you mean by "in DNS", is it your mikrotik?
But this blocking/redirection works on your mikrotik level and is nothing to do with OpenDNS.

OpenDNS filtering and blocking can be defined at https://www.opendns.com/dashboard/settings/0/content_filtering
See here how it works: http://forums.opendns.com/comments.php?DiscussionID=3635#Item_2
Don't forget to flush your browser cache and local DNS cache after each settings change.

"I only got the message box the first time. Subsequent attempts simply yield..."
Sure, browsers and Windows Explorer are clever enough to keep the credentials "in mind" (i.e. memory), until the next browser restart...

i change mikrotik again and now itried this
https://updates.opendns.com/nic/update?hostname=home
asking me user and password
then ansering me >>>> good 41.235.45.245

then?

Good point! I had overseen the domain name.

@khaloudy

Is filtering working, or no?
If no, have you cleared browser and local resolver caches?

last answer from mikrotik is
mikrotik dosnot support https?
what that mean?