# Specify node using header **URL:** \ **Category:** General\ **Created:** [February 15, 2021, 11:53am UTC](https://discuss.konghq.com/t/specify-node-using-header/7897 "2021-02-15T11:53:53Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![markgargan1](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/markgargan1/32/2557_2.png) [@markgargan1](https://discuss.konghq.com/u/markgargan1)\ **Post date:** [February 15, 2021, 11:53am UTC](https://discuss.konghq.com/t/specify-node-using-header/7897/1 "2021-02-15T11:53:53Z")
Hi folks, We’ve a service and route that sits in front of four nodes. Two in the cloud and two on prem. Would you know if it’s possible to configure the kong route in such a way that we could include a custom header, say target: CLOUD or target: PREM that would allow us to specify that the request gets either routed to a node in either the cloud or on-prem? Creating their own routes isn’t really an option at the minute. Thanks, Mark. ---
**Author:** ![narate](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/narate/32/1778_2.png) [@narate](https://discuss.konghq.com/u/narate)\ **Post date:** [February 15, 2021, 1:36pm UTC](https://discuss.konghq.com/t/specify-node-using-header/7897/2 "2021-02-15T13:36:54Z")
we can use route by header to route to service by custom header [Admin API - v2.3.x | Kong - Open-Source API Management and Microservice Management](https://docs.konghq.com/gateway-oss/2.3.x/admin-api/#route-object) ---
**Author:** ![markgargan1](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/markgargan1/32/2557_2.png) [@markgargan1](https://discuss.konghq.com/u/markgargan1)\ **Post date:** [February 16, 2021, 8:06pm UTC](https://discuss.konghq.com/t/specify-node-using-header/7897/3 "2021-02-16T20:06:53Z")
Thanks Narate but that just seems to be an alternative way to specify a service/route combination as opposed to isolating out a particular node behind a service.