Home > Paid Traffic Sources > Mobile

---

Mobile Lander Hosting (32)

---

Hey guys,

I've been going round in circles looking through heaps of past threads but can't seem to find a clear (newbie) answer for this.

What hosting should i use for my mobile landers?

I've currently got DNS Made Easy which is for Voluum and tracking, but i don't believe i can use this for landers right?

Can i use a CNS service for this or is that only good for storing files, not active landing pages?

If anyone could give me some clarity here that'd be great as i'm a bit confused.

---

http://stmforum.com/forum/showthread...iate-Marketing

Ok, just came across a thread that recommends a beyond hosting VPS for this, but it's almost 2 years old and not specific for international mobile landers...thoughts?

---

"Can i use a CNS service for this or is that only good for storing files, not active landing pages?"

If you mean a CDN, you can host a mobile lander on a CDN or a VPS.

The Mobile Cook book recommends a VPS too. In general, you'd use a VPS for hosting landers and a CDN for static content (like image files).

---

Are you confusing DNS and CDN?

Firstly, you should have a look at this - http://stmforum.com/forum/showthread...Needed-to-Know!

DNS Made Easy isn't useful with Voluum. Just use your raw tracking URL if you want the fastest redirect speeds possible. If you CNAME a domain to your tracking domain, you can use any DNS provider - really DNS Made Easy is not going to give much of an advantage here (DNS timings are of minimal consequence as long as you don't use a terrible provider).

DNS has nothing to do with storing of content or landing pages, for that you need a server or a CDN.

If you are running mobile internationally, hosting landers on a CDN is sensible.

---

@aushustler87 - I need to update that post. For US landers, Beyond will be fine, but for international mobile I'd go with a local server or a CDN.

---

Thanks for the clarification guys, and especially for that DNS guide Zeno, certainly cleared up a few things for me!

Yep, ill be running offers internationally so a CDN will be the way to go, could you recommend a good CDN provider and which would be the best package to signup for (i'm not running much traffic...yet).

Also, my understanding is that CDN's are only for storing static files or images (thanks Vision!), so my mobile landers would be like a screenshot image of a normal(non CDN stored) mobile lander (as opposed to having seperate images, buttons, text, etc) where you can just click anywhere on the page and it will then send you further down the funnel to the offer?

---

It would actually be a web page, so you could click on an individual button. Let me explain further...

A Content Delivery Network (CDN) is a way of serving static files from locations physically closer to the target user. You could use a CDN if targeting multiple geos, for example, anything from New Zealand to Russia to Chile.

For example: For a large dynamic php/mysql website targeting the USA and Australia, you could use a VPS for the dynamic content (php/mysql) and store the static content, i.e. your images, JavaScript and CSS files on a CDN so that a user from Brisbane will get their files from a Sydney server, or a user in New York will get their files from a server in New Jersey.

For a small site, for example, a simple mobile lander, it could be hosted entirely on a CDN, but it would need to be static, i.e. it's content will not change frequently. For example, a simple html/css/javascipt page (which would not use server-side scripting like php or asp.net).

CDN Examples:
Max CDN
Rackspace Cloud Files
Amazon s3

---

Vision nailed it.

For an entry-level CDN I'd recommend Rackspace Cloud Files - it's pay as you go so virtually free when starting out, and is easier to use than Amazon CloudFront.

---

Thanks a lot for the write-up Vision, and thanks Zeno, ill get onto Rackspace asap!

---

Just some follow up questions guys, i've been following iamattilla's guide (http://iamattila.com/media-buying-10...ding-pages.php) to getting this all setup, i've had some trouble getting the CNAME on godaddy to point to the link that i got from rackspace.



Do i need to direct this through a DNS first and then give the DNS nameserver address as the "points to" location at godaddy, or is there a built in DNS at Rackspace?

Cheers

---

The DNS system does not involve a connection protocol like http, https, ftp, etc.

Remove the http:// from your record (the Points to entry) and it should work fine.

---

Thanks man, i made those changes and my URL still wasn't linking to my container at rackspace, i've actually just realised that i don't have my 'A Record' at my DNS server setup. I've tried to set this up but Rackspace doesn't provide a server IP address for cloud file storage, just the URL in my previous post which can't be accepted as an A Record. I spoke to their tech support and had this conversation, which didn't really help me

[Chris] Can you tell me where i can find my server IP address? I'm only planning to use cloud files, do i need to create a server?
[Brandon C] You do not need to create a server for Cloud Files, and if you have a sevrer the ip can be found next to the server name under servers at mycloud.rackspace.com
[Chris] Oh ok, when i go to mycloud.rackspace.com and click on files it just has my container name, region and files, so there is no IP address that i can feedback to my DNS service?
[Brandon C] No there is not, you can use a cname record and the public links. First go to the containers page and make sure the container is public, then click the gear next to the container name and view all links. These links are used to access the container. So lets pretend the container link was example.com, to access any object in the container you would refrence it by filename. So if you wanted to view cat.jpg in the container you would browse to example.com/cat.jpg
[Chris] Ok cool, i think i understand, my only problem is i can't add my A record in without an IP address (i believe an A record essential? forgive my newbie-ness, im still learning)
[Brandon C] Not necessarily. It depends on your dns provider. The A record is essential for linking the main doamin to an IP, however if you are using a dns provider with naked cname support you can link *.yourdomain.com to another url, so while yourdomain.com would not load, www.yourdomain.com, and any other prefix would load the other url.
[Chris] Hmmm ok ill have a look into and have another go

So without an IP address, only a link to my cloud files page, how can i set this up to work?

Btw, thanks for your patience with all my newbie questions Zeno (in here and in the other thread), you're a massive credit to the STM team!

---

You create a container at the CDN, not a server - so I don't think an IP address is needed.
http://docs.rackspace.com/files/api/...e-dle4000.html

I think you just need to set the CNAME, not the A record at the domain registrar.
https://support.godaddy.com/help/art...r-domain-names

DNS changes can take upto 48 hours to propogate (but usually show up within an hour of the TTL).

If you've not done so already, you could contact GoDaddy support to ask for the correct settings to point your domain to your Rackspace Cloud files container.

---

You don't need an A-record for this, you need a CNAME record.

Put cdn.domain.com as your alias and then the container URL (minus any http://) as your Cloud Files container.

It should work just fine. If GoDaddy demands an IP address, just add a separate A-record for domain.com that goes to IP 123.123.123.123 - you won't even use it so...

Do note your CNAME entry will probably have to be "something.domain.com", not just "domain.com".

---

GOT IT!!

I don't know why its taken me 5 days (probably about 12-15 hours) worth of trial and error, following (and maybe miss-understanding) instructions from Zeno, Visions, DNS support, Rackspace support, and various other forum threads but i finally got it all working!!

I'll contribute back and make a quick "how to" guide for ultra ultra new newbies on setting up rackspace hosting with lots of screenshots and spoonfeeding, it was quite simple in the end, Zenos post just above is the correct answer to it.

Big thanks to Zeno and Visions for your advice, now to finally make some landers!

---

Question - is it possible to have multiple landers on the same domain using a CDN like above? Or do a need a new domain for each lander? Or can i create sub domains and use those somehow?
thx

---

Absolutely! You can have as many landers as you want on the same domain, i'd suggest you make it something generic like "uzzz00media.com" and then you're different landers could be

- uzzz00media.com/browseroffer4
- uzzz00media.com/walmartoffer7
- uzzz00media.com/adultoffer2
etc.

---

So i'm just trying to use a CDN for these pages (no server). Here is what i have -

This is the setup in rackspace.



My initial index file works fine. I'm getting confused when i want to add multiple landing pages to the same domain. How do i target each one differently?

Here is namecheap setup -



namecheap tells me "You will be able to set only one CNAME record for each hostname/subdomain. Also, CNAME record should point *only* to subdomain."
So whenever i grab the 'links' from rackspace, namecheap wont accept any of the nested folders.

me confuse.

---

CNAME your 'landers' container in namecheap. i.e. lps.yourdomain.com CNAMEs to that big rackspace URL.

Create folders in your container and put an index.html in each of these, so it might be lp1/index.html, lp2/index.html etc.

now you can go to lps.yourdomain.com/lp1/index.html and it'll work.

Also, use Cyberduck, it's a much better way of managing files on rackspace, you just have to grab your API key from 'Account Settings' on rackspace and use it when logging in along with your username.

---

thanks dude, was so close, just thought i needed 1 new subdomain for each lander!
Cheers

---

Yeh, i think craigm described the same way i currently use.

As long as you can get your first lander working then you can get all of them working, just have a different html file for each lander, and lump all your html files and jpg's into the one container, bon appetite!

---

Hey guys,

sorry for the noob question, but I'm getting a little confused on what mobile landers are.
Is a mobile lander:

1. the 320x50 banner I created?
or
2. another page where the traffic goes when they click on my banner?

If the second option is right, then would this mean that I have to design a landing page with call to action etc.?

Cheers

---

#2 my son. We're talking about Landing Pages (but on mobile). Landers for short.

And you are correct - you have to design/code a page with a CTA. If you're new to making landing pages, i would search this place around for some good templates, also 'spy' on other peoples landing pages and use as a starting point.

But of course you only need Landers if you're not Direct Linking straight to the offer.

Cheers

---

Wow, thanks for the fast reply and the clarification.

---

hmm, interesting. I decided to run a test between rackspace CDN and my VPS. oddly enough, the CDN was much slower

---

The long wait times suggest it's because the content hasn't yet been cached to the edge.

You can force it by testing many times, sometimes it takes more attempts than usual. Real traffic is highly effective at getting the content cached though.

---

I have another to question to my lander.

I tried several times to upload my updated lander to my rackspace container but when I open it by clicking on the index file in my container it shows different then the one I updated. Even when I load the lander on browserstack it doesn't show up updated. Only when I open the index file from my desktop I see the updated version on my browser.

Why is this?

---

Change the 'Modify Time to Live' setting to 900 seconds... although it still might take up to 3 days to change if your previous TTL was set at 3days. If you want to change it asap, rackspace support can help you out. Or you can just create new pages with new links.

---

Of course, because it's cached. The entire point of a CDN is global delivery + caching.

The easiest way to get around this is to rename it to index2.html for example or add a query string e.g. index.html?rev=2 but the latter only works if the CDN is set to not ignore query strings when caching.

---

Okay this makes sense. Thanks for the answers guys.

---

Nice thread !

I was wondering some questions though:

1- Which type of files can you host exactly on a CDN: I know images and html are static, but what about css/jquery/javascript ?
2- Depending on the answer on Q1 do you actually use a CDN to host the whole landers or you need to use both a vps/dedicated for some element + a CDN, that setup would be more complicated DNS wise I assume..
3- What structure you usually use for organisational purposes ?

Since we need to absolutely use a subdomain for cname (thats what I guess reading that stuff) the domain.com cannot be used as is but more like this:

sub1.domain.com
sub2.domain.com

and so on ? and if so what do you put on domain.com since it cannot be hosted on the cdn ? I thought about an offer wall but then it would serve from my dedicated server in the usa and not be global like a cdn.

Ahh sorry for so many questions

---

html/css/javascript/image files are Ok (server-side scripting like php or asp.net are not)
CDN for whole landers if simple html/css/javascript website. CDN's could easily host small mobile landers, for example.
VPS for more complex landers that may need php/mysql, for example.
VPS/CDN combination. Use VPS for hosting php landers. Use CDN for hosting static files, example: image files.
Use the folder [container] structure at the CDN. For example:
[landing-page1]/index.html
[landing-page2]/index.html

Then at the domain registrar or DNS provider, CNAME your landing pages container to the CDN container URL.

---

Home > Paid Traffic Sources > Mobile