Adding IP problem

P

perrera

Verified User
Joined
Jul 8, 2008
Messages
34
Ok, here is my drama.
A client wants a SSL certified so, have to assign a new ip for him, but after make the ip change in te reseller panel, the site only shows "Apache is functioning normally" :confused:

Whats I'm doing wrong?
Have to make any changes in dns?
 
Of course you do... and do a rewrite of the apache configs.

echo "action=rewrite&value=named" >> /usr/local/directadmin/data/task.queue
echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue
 
If you change the IP# in the control panel, and if you host your DNS on your DirectAdmin server, you do NOT need to change DNS; DirectAdmin will change it for you, usually within the next minute. It is not necessary to use the commands mr.applesauce posted, as DirectAdmin will handle them.

Your problem is/was most likely that your system was still using old cached DNS.

Jeff
 
Hi Jeff,
Thanks for the response.
Can you tell what can I do to get this domain resolved with new IP?
Have to add the ip to the /etc/hosts with the same hostname?

pd.:sorry for my bad english
 
Last edited:
The change is made. The problem is that you are seeing the old web site. Try look that web site with a web site as http://www.anonymouse.org

Try to delete cache or use other DNS, for example OpenDNS:
208.67.222.222
208.68.220.220
 
Mmm, if I went back to the shared IP, all seems to works in seconds.
I missing something here?

  1. Have the new ip in network-scripts, I can ping, no problem.
  2. Add the new IP to directadmin IP Managment.
  3. Asign the ip to admin
  4. Then to the user/domain
  5. Wait several hours, 4,6,8
  6. "Apache is function normally" :confused:
 
Last edited:
Yes, it is common. you will see that all is ok if you back to shared ip because your ISP has a cache with that IP.
If you change the IP it is common see that error message... You have to wait until the DNS will be refreshed.

Did you try the proxy that I said you? Did you try change the DNS of your computer?
 
perrera said:
Mmm, if I went back to the shared IP, all seems to works in seconds.
Click to expand...


The problem is only affecting you because you have recently viewed your web site. If you change ip addresses and you are using the default TTL then it could be a minimum of 4 hours before you see the web site on the new ip address.

Do some research on isp DNS caching.
 
You must log in or register to reply here.
Back
Top