Ugh, I did it again. I didn’t add the new server aliases when servers were added. Now, I’ve added a new client account, the site was put on the new server (web15), and the site won’t work. You’d think I’d learn! :rolleyes:
At this point, I’m trying to use the instant domain alias. We were hoping to do the DNS transfer tomorrow or over the weekend. But, I want to do a final almost-live test before we make that jump.
I added the server alias after creating the account. It’s been 6 hours and I can now access FTP using the web15.myservicedomain. com name. But, the instant alias isn’t working. I tried disabling and re-enabling the instant alias.
I’m getting Directory Listing Denied errors. Is that just a sign that DNS is taking longer to propagate WWW changes than FTP? How much longer should I expect?
Probably by the time you read this it will be working…
Besides adding server alias, you need also add dns record for working on instant alias. After logging in your administrative account, go to dns manager, click to on edit icon and there go to view dns records for instant alias. There make sure you have added instant dns record for new server.
Oh! Now I see where I’m supposed to add those. I just did. Still not seeing the site. But, maybe it will show up in a few minutes.
Is this new? I mean, after hosting here for years, there were four instant aliases not added according to that screen. I’ve never gone into this part of the CP to add these before. The rest must have been added automatically.
Or maybe this is only an issue when I don’t add the server alias before creating an account that gets put on the new server…?
you are using custom created nameservers for this domain right? and you have those nameservers assigned on the new domain? (btw instant alias working here now, nice site, and good to compete with that ripoff company that puts ads on tv!)
“custom created nameservers” ?? Not sure what you mean. I will use the dns.myservicedomain. com when we go live. But I haven’t made those changes yet. I didn’t plan anything more custom than that for DNS.
It’s good to know the instant alias is working for you now. It’s not for me (I tried flushing my DNS cache) but I guess I just have to wait for the propagation time to elapse.
Thanks for the kind comments on the site. I’m pretty happy with how it turned out and most importantly, so is the client!
yes i mean using your service domain, i figured you were but wanted to make sure.
instant aliases should NOT have a DNS propgation delay in most cases, my tihnking on it was more that it was visited before the DNS sync was done (every 5 min or so) and then went to cache, however DNS can also cache at the ISP side.
one possible suggestion to you would be to change over to opendns servers and after you make the switch, do the ipconfig /flushdns again, then visit the site(close browser before dns server as well)
