Adding second domain to API endpoint


James Bayer
 

guillaume, you're right. the CNAME approach won't work if the host header
doesn't match the route advertised from the CCs.

On Mon, Jun 8, 2015 at 2:08 PM, Guillaume Berche <bercheg(a)gmail.com> wrote:

James, would'nt a second domain (even if resolving to the same IP than the
primary domain, thanks to a CNAME), still be mentionned in http requests in
their original "Host:", header and would therefore be unknown to the CF
gorouter, returning a 404 as a response ?

I wonder whether the routing-api [1] indeed currently returns a wildcard
route to the CC IP/port, and could then be used to advertise a new wildcard
route in a second domain. This would require custom development into a
distinct bosh jobs (that would periodically renew the new domain before its
TTL expires)

Guillaume.

[1] https://github.com/cloudfoundry-incubator/routing-api#usage

On Sat, Jun 6, 2015 at 6:38 PM, James Bayer <jbayer(a)pivotal.io> wrote:

it appears as though the cloud controller only supports advertising a
single domain:


https://github.com/cloudfoundry/cf-release/blob/master/jobs/cloud_controller_ng/spec#L62-L63

i wonder if a CNAME would work for this as a work-around?

On Sat, Jun 6, 2015 at 9:19 AM, Vinicius Carvalho <
viniciusccarvalho(a)gmail.com> wrote:

Hi there, how can I add a second domain to my API endpoint? I know how
to add a shared domain for apps. But looking at the router /routes, the
api.<domain> maps directly to the cloudcontroller. How can I add a second
route using a different domain already mapped on my DNS?

Regards

--
The intuitive mind is a sacred gift and the
rational mind is a faithful servant. We have
created a society that honors the servant and
has forgotten the gift.

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


--
Thank you,

James Bayer

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

--
Thank you,

James Bayer


Guillaume Berche
 

James, would'nt a second domain (even if resolving to the same IP than the
primary domain, thanks to a CNAME), still be mentionned in http requests in
their original "Host:", header and would therefore be unknown to the CF
gorouter, returning a 404 as a response ?

I wonder whether the routing-api [1] indeed currently returns a wildcard
route to the CC IP/port, and could then be used to advertise a new wildcard
route in a second domain. This would require custom development into a
distinct bosh jobs (that would periodically renew the new domain before its
TTL expires)

Guillaume.

[1] https://github.com/cloudfoundry-incubator/routing-api#usage

On Sat, Jun 6, 2015 at 6:38 PM, James Bayer <jbayer(a)pivotal.io> wrote:

it appears as though the cloud controller only supports advertising a
single domain:


https://github.com/cloudfoundry/cf-release/blob/master/jobs/cloud_controller_ng/spec#L62-L63

i wonder if a CNAME would work for this as a work-around?

On Sat, Jun 6, 2015 at 9:19 AM, Vinicius Carvalho <
viniciusccarvalho(a)gmail.com> wrote:

Hi there, how can I add a second domain to my API endpoint? I know how to
add a shared domain for apps. But looking at the router /routes, the
api.<domain> maps directly to the cloudcontroller. How can I add a second
route using a different domain already mapped on my DNS?

Regards

--
The intuitive mind is a sacred gift and the
rational mind is a faithful servant. We have
created a society that honors the servant and
has forgotten the gift.

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


--
Thank you,

James Bayer

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


James Bayer
 

it appears as though the cloud controller only supports advertising a
single domain:

https://github.com/cloudfoundry/cf-release/blob/master/jobs/cloud_controller_ng/spec#L62-L63

i wonder if a CNAME would work for this as a work-around?

On Sat, Jun 6, 2015 at 9:19 AM, Vinicius Carvalho <
viniciusccarvalho(a)gmail.com> wrote:

Hi there, how can I add a second domain to my API endpoint? I know how to
add a shared domain for apps. But looking at the router /routes, the
api.<domain> maps directly to the cloudcontroller. How can I add a second
route using a different domain already mapped on my DNS?

Regards

--
The intuitive mind is a sacred gift and the
rational mind is a faithful servant. We have
created a society that honors the servant and
has forgotten the gift.

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


--
Thank you,

James Bayer


Vinicius Carvalho <viniciusccarvalho@...>
 

Hi there, how can I add a second domain to my API endpoint? I know how to
add a shared domain for apps. But looking at the router /routes, the
api.<domain> maps directly to the cloudcontroller. How can I add a second
route using a different domain already mapped on my DNS?

Regards

--
The intuitive mind is a sacred gift and the
rational mind is a faithful servant. We have
created a society that honors the servant and
has forgotten the gift.