NSUPDATE

General questions.
Post Reply
gian
Posts: 137
Joined: December 14th, 2011, 4:21 pm
Location: Milano, Italy

NSUPDATE

Post by gian » May 3rd, 2016, 1:32 pm

hello,

I just received the following message from NSUPDATE.
I wonder if it is possible to config the client at all, in order to comply to the server requirements.

Thanks for your time and help.

-Gian

*************************************************************************************
Issue: The abuse flag for your host was set.

Explanation:
The abuse flag usually gets set if your update client sends way too many
updates although your IP address did not change.

Your update client sent 125 faulty updates since we last checked.
We have reset the faults counter to 0 now, but we are rejecting updates
for this host until you resolve the issue.

Resolution:
You can easily do this on your own:
1. fix or replace the update client on this host - it must not send
updates if the IP did not change
2. visit the service web interface and remove the abuse flag for this host

Notes:
- this is usually caused by a misbehaving / faulty update client
(on your PC / server or router / firewall)
- the dyndns2 standard explicitly states that frequently sending
nochg updates is considered abuse of the service
- you are using way more resources on the service than really needed
- for Linux and similar OSes, you can use the ddclient software - we
give copy&paste-ready configuration help for it on our web UI
- if you need something else, use anything that can be considered
a valid, well-behaved dyndns2-compatible update client
- if you already used such a software and you ran into this problem,
complain to whoever wrote it about it sending nochg updates

User avatar
Arne.F
Core Developer
Core Developer
Posts: 8522
Joined: May 7th, 2006, 8:57 am
Location: BS <-> NDH
Contact:

Re: NSUPDATE

Post by Arne.F » May 3rd, 2016, 3:39 pm

IPFire sends only updates if the ip that is reported by a dns resolve is not matching to the current ip. For me it looks that nsupdate.info doesn't spread the ip to the dns but count a second try as abuse.

Pfsense users report the same https://forum.pfsense.org/index.php?topic=108526.0 with nsupdate.info.
So use an working ddns provider...
Arne

Support the project on the donation!

Image

Image

Image
PS: I will not answer support questions via email and ignore IPFire related messages on my non IPFire.org mail addresses.

Post Reply