CNTOOLS dynamic DNS support

Hello everyone, I have set up a dynamic DNS for my pool thru noip. Everything seems to be working fine when i use dns checker. Now when i use pool.vet or even list my pool in cntools. It doesn’t seem to show my dns that i entered or even seem to update the IP address at all. Still showing a previous IP. My BP /relays seems to be working fine and are processing transactions. Is dynamic dns not supported in cntools? or should have i added my dynamic dns into a typology file somewhere. Any one run into this problem?

The transaction was submited ok? What is the ticker?

I am still getting transactions on my relay and BP nodes. But showing offline on pooltool and showing outdated IP in pool.vet. ticker is fresh. Have you heard of any problems using dynamic DNS address in cntools when re-registering pool?

Go to log folder and check for the last messages from topology Updater

I am at work. But I will look at the logs. Is this for the BP or my relays?

Relays, you don’t have to run the topology updater on BP

relay looks good

GNU nano 4.8 topologyUpdater_lastresult.json
{ “resultcode”: “204”, “datetime”:“2021-08-21 04:17:46”, “clientIp”: “174.92.88.163”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-08-21 05:16:13”, “clientIp”: “174.92.88.163”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-08-21 06:16:17”, “clientIp”: “174.92.88.163”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-08-21 07:16:21”, “clientIp”: “174.92.88.163”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-08-21 08:16:25”, “clientIp”: “174.92.88.163”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-08-21 09:16:29”, “clientIp”: “174.92.88.163”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-08-21 10:16:33”, “clientIp”: “174.92.88.163”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-08-21 11:16:37”, “clientIp”: “174.92.88.163”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-08-21 12:16:41”, “clientIp”: “174.92.88.163”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-08-21 13:16:45”, “clientIp”: “174.92.88.163”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-08-21 14:16:49”, “clientIp”: “174.92.88.163”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-08-21 15:16:53”, “clientIp”: “174.92.88.163”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-08-21 16:16:57”, “clientIp”: “174.92.88.163”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-08-21 17:17:01”, “clientIp”: “174.92.88.163”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-08-21 18:17:06”, “clientIp”: “174.92.88.163”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-08-21 19:17:09”, “clientIp”: “174.92.88.163”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-08-21 20:17:13”, “clientIp”: “174.92.88.163”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-08-21 21:17:17”, “clientIp”: “174.92.88.163”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-08-21 22:17:21”, “clientIp”: “174.92.88.163”, “iptype”: 4, “msg”: “glad you’re staying with us” }
{ “resultcode”: “204”, “datetime”:“2021-08-21 23:17:25”, “clientIp”: “174.92.88.163”, “iptype”: 4, “msg”: “glad you’re staying with us”

so they ip is correct in Topologyupdater… but on pool.vet and when i “show” pool in cntools it has an old ip address listed.

Ok, understand now… it should work … try to register again … I don’t know what to say…

is there anything special to use dynamic dds tho? should i just re register with that address? I saw somewhere that someone changed there cnode hostname?

hello friend i think dynamic dns usefull for domains because your home ip is dinamyc but noip link your dynamic ip with a static domains all time are pinging each other, i think your node work in the first ocassion but when the ip is update you need register again the node…

I saw the dns were updated :beers::muscle: @JonSolo

1 Like