Strange issue with DNS and Trunks

1

I have one trunk, and it uses voip.ms and IAX. Originally, it was pointing to the hostname “tampa.voip.ms”. A week ago, I edited the Trunk to “tampa2.voip.ms” which is a newer server. All seems to work well, but I am still seeing references to “tampa.voip.ms” in my Full log, and I don’t know why. Worse, those logs seem like something is broken:

[2017-12-04 10:04:55] NOTICE[1844] dnsmgr.c: dnssrv: host ‘tampa2.voip.ms’ changed from 162.254.144.173:4569 to 162.254.144.176:4569
[2017-12-04 10:04:55] NOTICE[1844] dnsmgr.c: dnssrv: host ‘tampa.voip.ms’ changed from 162.254.144.176:4569 to 162.254.144.173:4569

Notice that the two hostnames swapped IPs. That doesn’t seem right. It may be a coincidence, but that swap happened during a call where the user reported that they never heard hold music and nobody could hear each other.

How can I find the old reference to tampa.voip.ms?

2

There are (at least) two places where the host is used when setting up a trunk, the peer details as well as the registration string. Did you update both? When making host changes to existing trunks, experience tells me that Asterisk needs a restart.

3

Hi!

Did you change the server name both in the outgoing settings (the host line) and registration?

(ie YourAcountNumber:[email protected]:5060…)

voip.ms has occasionally changed IP on their servers but they normally warn people when they do since some people use IP instead of hostnames…

I checked, no switch of IP on their part has been documented…

In this case however it’s a switch of IP between two of their servers and at the same time, something I don’t expect they will ever do…

My guess this is just a weird symptom on a misconfiguration on your system and not actually a change of IP address on their part…

Good luck and have a nice day!

Nick

1 Like
4

Thanks for the quick answers. Yes, I changed the hostname in both the Incoming Peer Details and Outgoing Registration String. I have not done a full reboot in 2 weeks though, so I’ll try that and see if the old reference comes back.

Do you all typically reboot on a schedule, or do you leave your system running for months?

5

I haven’t rebooted yet, but I searched the Full log for instances of “dnsmgr” and it looks like that weird swap happens over and over, except it’s always identical. This is every instance of “dnsmgr”:

[2017-12-04 10:39:55] NOTICE[1844] dnsmgr.c: dnssrv: host ‘tampa2.voip.ms’ changed from 162.254.144.173:4569 to 162.254.144.176:4569
[2017-12-04 10:39:55] NOTICE[1844] dnsmgr.c: dnssrv: host ‘tampa.voip.ms’ changed from 162.254.144.176:4569 to 162.254.144.173:4569

[2017-12-04 10:44:55] NOTICE[1844] dnsmgr.c: dnssrv: host ‘tampa2.voip.ms’ changed from 162.254.144.173:4569 to 162.254.144.176:4569
[2017-12-04 10:44:55] NOTICE[1844] dnsmgr.c: dnssrv: host ‘tampa.voip.ms’ changed from 162.254.144.176:4569 to 162.254.144.173:4569

[2017-12-04 10:49:55] NOTICE[1844] dnsmgr.c: dnssrv: host ‘tampa2.voip.ms’ changed from 162.254.144.173:4569 to 162.254.144.176:4569
[2017-12-04 10:49:55] NOTICE[1844] dnsmgr.c: dnssrv: host ‘tampa.voip.ms’ changed from 162.254.144.176:4569 to 162.254.144.173:4569

[2017-12-04 10:54:55] NOTICE[1844] dnsmgr.c: dnssrv: host ‘tampa2.voip.ms’ changed from 162.254.144.173:4569 to 162.254.144.176:4569
[2017-12-04 10:54:55] NOTICE[1844] dnsmgr.c: dnssrv: host ‘tampa.voip.ms’ changed from 162.254.144.176:4569 to 162.254.144.173:4569

[2017-12-04 10:59:55] NOTICE[1844] dnsmgr.c: dnssrv: host ‘tampa2.voip.ms’ changed from 162.254.144.173:4569 to 162.254.144.176:4569
[2017-12-04 10:59:55] NOTICE[1844] dnsmgr.c: dnssrv: host ‘tampa.voip.ms’ changed from 162.254.144.176:4569 to 162.254.144.173:4569

[2017-12-04 11:04:55] NOTICE[1844] dnsmgr.c: dnssrv: host ‘tampa2.voip.ms’ changed from 162.254.144.173:4569 to 162.254.144.176:4569
[2017-12-04 11:04:55] NOTICE[1844] dnsmgr.c: dnssrv: host ‘tampa.voip.ms’ changed from 162.254.144.176:4569 to 162.254.144.173:4569

[2017-12-04 11:09:55] NOTICE[1844] dnsmgr.c: dnssrv: host ‘tampa2.voip.ms’ changed from 162.254.144.173:4569 to 162.254.144.176:4569
[2017-12-04 11:09:55] NOTICE[1844] dnsmgr.c: dnssrv: host ‘tampa.voip.ms’ changed from 162.254.144.176:4569 to 162.254.144.173:4569

etc. Weird, huh? I’m rebooting right now…

EDIT: Rebooting seems to have fixed it. The message has not come back. Thanks!

6

Log into the console as root and use the following command to check for possible corruption in your /etc/files:

grep tampa2 `find /etc -type f’

Those are 'backticks" (next to the ‘1’ key) around the find command.

It’s possible (if unlikely) that you have the “old” tampa2 address in your /etc/hosts file (for example).

7

Dave Burgess:
Log into the console as root and use the following command to check for possible corruption in your /etc/files:
grep tampa2 `find /etc -type f’

I SSH’d into it, cd to /etc, then ran: grep -r ‘tampa’

It found 2 results, and both were “tampa2” and were the IAX Trunk settings. So no luck there. Since I rebooted a few hours ago, the references to “tampa” in the log have not come back, so I think the reboot fixed it. Thank you though!