afraid.org - dnsomatic ERROR: Unable to locate this record

Comments

20 comments

  • Avatar
    rotblitz

    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.

    0
    Comment actions Permalink
  • Avatar
    Brian Hartvigsen

    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.

    0
    Comment actions Permalink
  • Avatar
    Brian Hartvigsen

    I stand corrected.  I just saw the message rotblitz indicated on my account.  Odd.  Alright, getting a report open to get that updated.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    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
    0
    Comment actions Permalink
  • Avatar
    Brian Hartvigsen

    Already on the list, as well as changes to dtdns and yi.org for incorrectly labeling some successful updates as errors.

    ChangeIP specifically failed because we were expecting the target to be a domain, not a set.  That's being fixed.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    Awesome!

    0
    Comment actions Permalink
  • Avatar
    Brian Hartvigsen

    Those changes have all been pushed at this time.  If you see erroneous ERROR messages, please open a support ticket or a new thread here.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    Brilliant! Confirmed, all clean now with afraid.org and ChangeIP. Thanks a lot!

    0
    Comment actions Permalink
  • Avatar
    tuchtach

    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

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    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.

    0
    Comment actions Permalink
  • Avatar
    tuchtach

    I am sure the key is ok as my other two accounts are updating without issues.

    I have opened a ticket with openDNS

    Thanks

    tuchtach

    0
    Comment actions Permalink
  • Avatar
    Brian Hartvigsen

    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.

    0
    Comment actions Permalink
  • Avatar
    tuchtach

    Hi

    A friend of mine has an account at afraid which key ends with .....== and there it works without issues.

    Not sure if this helps ...

    tuchtach

    0
    Comment actions Permalink
  • Avatar
    Brian Hartvigsen

    It only seems to impact keys that end with a single equal sign.  For some reason if there are multiple equal signs then the URL encoding doesn't create an issue.  DNS-O-Matic doesn't treat them differently, all equal signs were being URL encoded.

    0
    Comment actions Permalink
  • Avatar
    tuchtach

    Would it help if I open a ticket at Afraid.org? Or would that be contra-productive?

     

    0
    Comment actions Permalink
  • Avatar
    Brian Hartvigsen

    I have sent an email to our contacts there.  You can open a ticket with them if you like, it shouldn't hurt anything.

    0
    Comment actions Permalink
  • Avatar
    Brian Hartvigsen

    Our changes were pushed this morning at 9:30am Pacific Time.  This also coincides with the last time we saw an "Error: Unable to locate this record" response from afraid.org.

    0
    Comment actions Permalink
  • Avatar
    tuchtach

    Hello Brian.

    Since then I never got an error.

    I have closed the ticket.

    Thanks for your effort

    Kind regards

    tuchtach

    0
    Comment actions Permalink
  • Avatar
    stuart

    was this issue ever resolved; I have a link with an '=' sign on the end and seem to be having the same issue.

    0
    Comment actions Permalink
  • Avatar
    mattwilson9090

    According to the forum traffic from a year and a half ago this was resolved back then. Something may have changed since then to create a new problem with similar symptoms.

    Is this something that just started happening?

    0
    Comment actions Permalink

Please sign in to leave a comment.