I set up discourse via the documents and I installed discourse on DigitalOcean VPS. I changed all the nameservers to DigitalOcean and added my web domain URL to the project in DigitalOcean.
For some reason it stills shows Godaddy Lander page??
How do I fix this issue and start setting up Discourse?
Hello and welcome @Preeminence 
I think moving name servers can take a while to work through the system. There’s a chance you may just need to wait a bit. 
(Just as an FYI, though possibly a little late, but there’s no need to move the name servers to install Discourse)
I had it on Godaddy default nameservers and waited 48 hours, the webpage still displayed the Godaddy Lander page after installing discourse on DigitalOcean VPS (followed all steps in installation document..)
Is there still something live on the godaddy side?
The website is bidsturf.com, it keeps redirecting to bidsturf.com/lander
It sounds like you have a stray DNS record somewhere. When I use https://dnschecker.org/ to have a look at http://bidsturf.com/ it does seem that it’s pointing at two places.
You may need to contact godaddy and see if they can remove the redirect if you no longer have access.
Ok, I will contact them tomorrow.
No need to wait.
Add entry in your /etc/hosts file pointing domain to the GoDaddy IP address and you will see your site.
Tried that, still points to lander page.
From the screenshot you edited out, it looks like you are trying to access the file in your own Windows computer. To be sure, are you running Discourse in development or production?
Dev mode
In that case, you will be running it on localhost, not on a domain. When you run the dev server, go to https://localhost:4200 to see the forum.
Nevermind, just checked. It’s in Production mode, how can I switch it between Prod and Dev mode?
You will have to install a separate forum for development.
I guess since you’re running in production, you can ignore my advice above.
So should I run this on DigitalOcean VPS or is that outdated?
Nope, AFAIK DO is fine to run your forum on.
I think you should only have the one A record, but apart from that your dns is resolving nicely when I check https://dnschecker.org/. 
I’m not sure what the bottom two A records are for, but I think the www should be a redirect or a cname rather than an A. There’s also some advice on getting a certificate for the second domain as well Set up Let’s Encrypt with multiple domains / redirects
However, you may find it simpler to concentrate on getting your site set up on one first and sort out the second address later.
I went to Godaddy support for the two bottom A Records. I put two because I didn’t know what IP to use.
I opened CMD and pinged the website and got the 143.244… IP address as hostname and added it as A record. The 142.93… one is the VPS IP address.
I don’t which one will work, just trying to display the forum at bidsturf.com ( which still doesnt display at the moment).
But I will perhaps try to remove the 2 bottom A records and add the www as a CNAME.
If they’re added on the advice of godaddy to help sort out the original issue then double check the advice just to make sure it’s entered correctly and leave them in for now. 
Just to confirm, the IP the ‘main’ A record is pointing to is the one of your DO droplet?
If so, I’d try running ./discourse-setup again to see if that brings things to life. 
