LEMP stack - DNS domain zone
-
The LEMP stackscript walkthrough states that step 2 (Point domain to nameservers), should be done on moving day for migrating sites. Should step 3 be done on moving day as well, or should I go ahead but leave the Domain Status as Disabled?
Also, in the commented version of the script, you have a 404 link to http://vpsbible.com/security/keys
Thanks,
Nick
Posted 2 years ago # -
Never mind about the DNS, guvnr. I figured that out.
The script seems to have run OK, but I'm just getting "Welcome to nginx" when I visit the site using the ip address. I still have set up the reverse DNS yet. Could that be the cause?
Posted 2 years ago # -
hey Nicholas .. you did double-check your values, huh, cos that's more likely?
.. you may, well, will, have to wait for some DNS propagation .. and that is the most likely issue .. and it may be necessary to restart nginx after propagation .. the only issue there being that we can never tell for sure how long propagation of the DNS records will take all the way across this merry old planet of ours.
...
/etc/init.d/nginx restart
Posted 2 years ago # -
I haven't set my registrar to point to my Linode nameservers yet. I see the "Welcome to nginx message" (/usr/local/nginx/html/index.html) when I navigate to my IP address, http://97.107.135.149/
I have not set up my reverse DNS on Linode either. Is this something I do now or when I'm ready for the site to go live?
I don't think it's the script. I saved the stackscript and the commented stackscript into two separate files and diff'ed them with WinMerge. With the commented version next to the script it was really straightforward to edit. I double checked and here are the entries I changed:
export USER="XXX"
export PASSWORD="XXX"
export LOCALE="en_US"
export PORT="XXX"
export PUBLIC_KEY="ssh-rsa BLAH_BLAH_BLAH"
export HOSTNAME="mail.breezetree.com"
export DOMAIN="breezetree.com"
export POSTFIX_FIX="\$breezetree"
export DATE_TIMEZONE="America/Los_Angeles"
export MYSQL_PASSWORD="XXX"I've uploaded my files to /home/public_html/breezetree.com/public. So my main question is, what do I need to do in order to preview my site and make sure everything is working before I set my registrar's DNS to point to the new nameservers?
Posted 2 years ago # -
ok, then everything's working as it should.
you'll have to change the nameservers - as explained in the tutorial ;) before you can set the site live.
the rdns you can change now as that won't effect your existing site.
tip ..
to test your new site without changing the nameservers - and this is good practice - edit your local file to redirect http://yourdomian.com to the new VPS. for instructions on that read:-
» tutorial » Safe Site & Blog Relocation Guide
.. (editing your hosts file)
Posted 2 years ago # -
The server is currently serving up this file as the home page (when I enter the http://IP_ADDRESS):
/usr/local/nginx/html/index.html
Shouldn't it be serving up this page:
/home/public_html/breezetree.com/public/index.php
Posted 2 years ago # -
Well, hot damn, it worked!
:-)
Posted 2 years ago # -
One more thing...
How do I raise the priority of default.htm over index.php?
EDIT: found it in the /usr/local/nginx/sites-available/mydomain.com file.
Posted 2 years ago # -
Owen Hawkridge
MemberHaving the same problem - fresh install of Ubuntu on a node vps.net. Stackscript was flawless - "Welcome to NGINX" at server IP but mydomain.com does not resolve anywhere. Being patient as only been about 12 hours, hopefully DNS will sort itself out but I'm desperate to get to work with my box!
Posted 1 year ago # -
Bear in mind, folks ..
You generally have to wait anything up to a day (sometimes longer, depends on the host) for DNS to propagate to all those servers around the rock.
It's the same deal when you change the nameservers.
Posted 1 year ago #
Reply
You must log in to post.
Want HTML?
a blockquote code em strong ul ol liPlace code between backticks `codeHere`
You've got it.