Rik Goldman - Fri, 2011/07/22 - 00:26
For a month or so - perhaps two months, I've been running a LAMP stack on the hub with the audibleleft.tklapp.com. I had to restart -r now today for a silly reason, and now the hostname isn't associated with the IP address it's getting assigned (50.19.73.87), How do I proceed? If it's helpful, I was having this problem during the last two weeks on prototype servers - having to use the IPs rather than the tklapp.com hostnames I felt sure I was assigning. Need more info?
Forum: 
Support

Rik Goldman - Fri, 2011/07/22 - 02:10

Tried the hopeful/helpful docs here (http://www.turnkeylinux.org/blog/hub-domains) and while I hoped very hard, it didn't resolve the issue. I'd have no problem, except Chamilo is one of those apps that wants to know it's hostname.

$ hubdns-update

updated audibleleft.tklapp.com. with 50.19.73.87

 

for example. restart, still no luck

Alon Swartz's picture

Alon Swartz - Sun, 2011/07/24 - 14:11

Is it possible you have more than one machine configured with audibleleft.tklapp.com? They might be fighting for the IP.

If not, then this is really bizarre. Could you try executing the following:

hubdns-info
hubdns-update
hubdns-info

BTW, I just checked and it seems audibleleft.tklapp.com is "released". Performing the update will re-associate it with your server.

Add new comment