DNS manager keeps changing

App_rpt-users
1

The message log is full of these lines. Anyway to stop this?
[Jun 14 05:07:20] NOTICE[373] dnsmgr.c: host ‘register.allstarlink.org’ changed from 178.32.160.82 to 44.135.121.22
[Jun 14 05:07:20] NOTICE[373] dnsmgr.c: host ‘register.allstarlink.org’ changed from 44.135.121.22 to 216.244.83.154
[Jun 14 05:12:20] NOTICE[373] dnsmgr.c: host ‘register.allstarlink.org’ changed from 44.135.121.22 to 178.32.160.85
[Jun 14 05:12:20] NOTICE[373] dnsmgr.c: host ‘register.allstarlink.org’ changed from 216.244.83.154 to 44.135.121.22
[Jun 14 05:17:20] NOTICE[373] dnsmgr.c: host ‘register.allstarlink.org’ changed from 178.32.160.85 to 44.135.121.22
[Jun 14 05:17:20] NOTICE[373] dnsmgr.c: host ‘register.allstarlink.org’ changed from 44.135.121.22 to 216.244.83.154
[Jun 14 05:22:20] NOTICE[373] dnsmgr.c: host ‘register.allstarlink.org’ changed from 44.135.121.22 to 216.244.83.154
[Jun 14 05:22:20] NOTICE[373] dnsmgr.c: host ‘register.allstarlink.org’ changed from 216.244.83.154 to 178.32.160.82
[Jun 14 05:27:19] NOTICE[373] dnsmgr.c: host ‘register.allstarlink.org’ changed from 216.244.83.154 to 44.135.121.22
[Jun 14 05:27:19] NOTICE[373] dnsmgr.c: host ‘register.allstarlink.org’ changed from 178.32.160.82 to 192.83.199.4
[Jun 14 05:32:20] NOTICE[373] dnsmgr.c: host ‘register.allstarlink.org’ changed from 44.135.121.22 to 178.32.160.85
[Jun 14 05:32:20] NOTICE[373] dnsmgr.c: host ‘register.allstarlink.org’ changed from 192.83.199.4 to 44.135.121.22
[Jun 14 05:37:19] NOTICE[373] dnsmgr.c: host ‘register.allstarlink.org’ changed from 44.135.121.22 to 178.32.160.82
[Jun 14 05:42:20] NOTICE[373] dnsmgr.c: host ‘register.allstarlink.org’ changed from 178.32.160.85 to 216.244.83.154

2

This is normal behavior.

The resolved DNS target of the registration server constantly changes to one of the 5 regional hosts. You’re just seeing a log notification the module fires off when it notices this has taken place.

I suppose if you really wanted to avoid having this happen, you could opt to register node(s) directly towards one of the reg. servers by using the @IP address instead of @register.allstarlink.org. But I would not recommend anyone start doing that. i.e. You’ll forget you did that, and as soon as that single registration server has problems, you’ll be wondering why things stopped working…etc.

Byron