![]() ![]() In all other cases it warns user that request was ignored because of agent that does not follow our specifications. This answer indicates good update only when 127.0.0.1 address is requested by update. The user agent was not sent or HTTP method is not permitted (we recommend use of GET request method). If no hostnames were specified, notfqdn will be returned once. The hostname specified is blocked for update abuse. Also returned if trying to update a round robin (which is not allowed). Too many hosts (more than 20) specified in an update. The hostname specified does not exist in this user account (or is not in the service specified in the system parameter). The hostname specified is not a fully-qualified domain name (not in the form or ). The client must stop updating that hostname until the user confirms that the problem has been resolved. The codes below indicate a problem with a specific hostname. This value will be separated from the return code by a space. Note that, for confirmation purposes, good and nochg messages will be followed by the IP address that the hostname Additional nochg updates will cause the hostname to become blocked. The update changed no settings, and is considered abusive. The update was successful, and the hostname is now updated. The codes below indicate that the update of a hostname was completed successfully. If multiple hosts were specified, only a single !donator will be returned. The username and password pair do not match a real user.Īn option available only to credited users (such as offline URL) was specified, but the user is not a credited user. ![]() The client must stop updating until the user confirms that the problem has been resolved. The codes below indicate that the client is not configured correctly for the user’s account. Retrying the update automatically in those cases is abuse and may result in client blocks. Many of these errors involve configuration mistakes within the client or inconsistencies between the client configuration and the user’s account status in all of those cases, the client must stop updating until the user has corrected the problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |