A method executed in a content distribution system, wherein - the content distribution system includes - a host server including a route program module, - a switch with two or more egress interfaces, - a route collection service module, and a traffic engineering service module, both modules not belonging to the switch, wherein - the host server - stores and executes a content service application and - is connected to the switch, and wherein - the switch is connected to two or more autonomous systems, wherein each of the two or more egress interfaces is connected to a different autonomous system, the method comprising: - the route collection service module collecting through the switch prefix entries from each of the at least two autonomous systems and associating the prefix entries with each of the at least two autonomous systems; - the route collection service module associating each autonomous system to a particular egress interface; - the traffic engineering module associating egress interfaces with prefixes and updating this information to the host servers; - receiving at the host server a content request from a client device to send digital content to a prefix; - in the route program module, associating opaque labels to prefixes, the opaque label corresponding to an egress interface of the switch connected to the one autonomous system associated with the prefix, wherein the content distribution system enabling the routing decisions to be shifted to the host server; - providing in the host server an IP packet designated for the prefix with the opaque label; - sending the IP packet to the switch, the switch forwarding the received packet based on the opaque label to the egress interface. - the content distribution system includes - a host server including a route program module, - a switch with two or more egress interfaces, - a route collection service module, and a traffic engineering service module, both modules not belonging to the switch, wherein - a host server including a route program module, - a switch with two or more egress interfaces, - a route collection service module, and a traffic engineering service module, both modules not belonging to the switch, wherein - the host server - stores and executes a content service application and - is connected to the switch, and wherein - stores and executes a content service application and - is connected to the switch, and wherein - the switch is connected to two or more autonomous systems, wherein each of the two or more egress interfaces is connected to a different autonomous system, - the route collection service module collecting through the switch prefix entries from each of the at least two autonomous systems and associating the prefix entries with each of the at least two autonomous systems; - the route collection service module associating each autonomous system to a particular egress interface; - the traffic engineering module associating egress interfaces with prefixes and updating this information to the host servers; - receiving at the host server a content request from a client device to send digital content to a prefix; - in the route program module, associating opaque labels to prefixes, the opaque label corresponding to an egress interface of the switch connected to the one autonomous system associated with the prefix, wherein the content distribution system enabling the routing decisions to be shifted to the host server; - providing in the host server an IP packet designated for the prefix with the opaque label; - sending the IP packet to the switch, the switch forwarding the received packet based on the opaque label to the egress interface.