afraid.org - dnsomatic ERROR: Unable to locate this record
Hi
We have a free account at afraid.org and want to update it through dnsomatic.com.
It waited some time for first update but then showed "Error" on dnsomatic service site.
The log shows "ERROR: Unable to locate this record".
Maybe a typo in the key we thought. So we rotated the key at afraid and put the new one also into dnsomatic.
But the error still remains.
We tried also another DNS name at afraid, but the error is the same.
Does someone have any idea how to solve this/analyze this?
Thanks
tuchtach
-
I also get always error messages, daily updating three hostnames at afraid.org, but the updates are successful nevertheless. There seems to be a problem with DNS-O-Matic not recognizing the correct update message which is:
Updated <hostname> to <IP address> in 0.007 seconds
However, if it really shows "ERROR: Unable to locate this record", your problem is definitely not related to DNS-O-Matic, but there is really a problem with your key or hostname at afraid.org or the way you entered it at DNS-O-Matic. The keys start normally with Ujg4VWFr these days. If you don't get it right, you may contact the owner (Josh) of afraid.org to possibly find out.
-
afraid.org uses messaging as follows:
Updated # host(s) [LIST] to [IP] in 0.013 seconds
We also detect their no change message as being a successful update:
ERROR: Address [IP] has not changed.
If you see other messages that we should accept as successful updates, please take a screenshot of the history log in DNS-O-Matic showing the message and open a support ticket with that as an attachment.
-
Great stuff, Brian! Thanks.
And while we are that matter, please get also the ChangeIP stuff corrected which is also not recogized as successful.
The success response from ChangeIP is (example):
200 Successful Update (Address Used: IP address) Updated target: *1 Updated 3 host records Updated 1 zone serial numbers Reviewed 3 possible records Total updates: 394 Lockout counter: 1 out of 60 Lockout reset: 59 mins Elapsed time: 0.01 seconds NIC version: 2.68 For XML output add &xml=1
-
The update still does not work.
I have deleted and recreated the entry again.
The key is not like rotblitz said, it starts with VWM4aHU2MzF......
Any other idea?
Thanks
tuchtach
-
I'm afraid(.org :) you must open a support ticket. We users can't help with this, as staff must check your DNS-O-Matic account. Whatever, I'm pretty sure you did something wrong, either at DNS-O-Matic or at afraid.org. I have three afraid.org hostnames all orderly updating since ions. I got the impression this works even more reliably than with e.g. DynDNS.
-
tuchtach - I may have identified the issue. It looks like your key may end with an equal sign (=), it's part of the padding used in the base64 encoding utilized by afraid.org. This is url encoded (aka percent encoded) on our side to %3D. Apparently afraid.org does not want the this URL encoded as if you pass a key with the raw equal sign it works fine, but if you pass it a URL encoded key it fails.
Given that an equal sign has special meaning in a URL it does not seem incorrect to URL encode it's value, however it is apparently incorrect for afraid.org. I am contacting the guys at afraid.org as this handling seems odd, but I'll also get a bug opened with our development team.
Please sign in to leave a comment.
Comments
20 comments