2

Is it possible? Does somebody know, how is it technically possible to setup a CDN without nameserver and cname manipulation?

Improve this question
3
  • 1
    What do you mean "without nameserver and cname manipulation?" Do you mean that you don't want to change NS or CNAME DNS entries? Are you open to changing A records? CDNs use DNS tricks to route traffic to the closest edge node, so there is no way to use them without allowing some sort of DNS changes.
    – Stephen Ostermiller ♦
    Commented Feb 6, 2018 at 14:15
  • i'm comfortable with both of dns and cname, no prob - just was asked by a client, is there a kind of such simple possibility to setup a CDN, like to input domain name, and the CDN provider does the rest...
    – Evgeniy
    Commented Feb 6, 2018 at 14:48
  • Your website could resolve to one IP that is anycasted (so hopefully the closer endpoint would answer requests). Or it can resolve to different IPs because the authoritative nameservers would have some logic to reply differently based on the source, and with the help of the Client Subnet EDNS option. This means "magic" in the implementation but the content of the zone would be simple and no CNAMEs nor NS changes. So you will need to make your question clearer.
    – Patrick Mevzek
    Commented Feb 6, 2018 at 16:27

1 Answer 1

Reset to default
1

Not supported by all Registrars

If you want the ability to create additional sites or content delivery networks without having to edit any DNS entries then you can adopt a wildcard setup. Sadly not all registrars allow you to do this but a example of a wild card A record looks like this: *.cdn.

Virtual Host

This allows you to create sites, apps and content delivery networks by just editing the virtual host on your server, for example *.cdn.example.com becomes uniquestring.cdn.example.com, this is how Rackspace, Azure and Amazon issue CDN for their customers.

Amazon Route 53

If your current domain registrar does not allow wildcards then take a look at Amazon Route 53

Improve this answer
3
  • Wildcards create more problems than solutions (and even more so with DNSSEC), specially in the hand of beginners, so when possible it is better to try not using them.
    – Patrick Mevzek
    Commented Feb 6, 2018 at 16:24
  • Doesn't make it a invalid solution...
    – Simon Hayter
    Commented Feb 6, 2018 at 22:25
  • I never said it is invalid. I said that wildcards in the hands of beginners are dangerous so it is not a recommended one, but it is one among others, yes...
    – Patrick Mevzek
    Commented Feb 6, 2018 at 22:26

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.