Named Data Networking (NDN) has been recently added to the future Internet family. NDN is basically an extension to the Content Centric Network (CCN) and is expected to support various applications. Those applications are to be supported by the future internet architectures. NDN believes in naming the content rather than using end-to-end device names. Recently, NDN has been adapted into Vehicular Ad hoc Networks (VANETs) and hence, we name it Vehicular NDN (VNDN). At it's early stage, VNDN faces several challenges such as consumer/provider mobility, Interest/Data forwarding, content caching and so on. Mostly, VNDN relies on the fact that Data is sent back to the consumer via same path the Interest packet was received from. However, we analyzed that it's not true in a VANET and there is lack of discussion about managing the Data flow back to the consumers in the current literature of VNDN. In this paper, we therefore, pursue to control the data flooding/broadcast storm of the conventional VNDN by proposing our scheme “CONET”. The main idea of CONET is to allow the consumer vehicle to start hop counter in the Interest message and upon receiving that interest by any potential provider, to include Time To Live (TTL) value with data messages. The TTL value includes the number of hops, Data packets should travel on its way back to the consumer. Simulation results show that CONET forwards less Copies of Data Messages Processed (CDMP) while achieving similar Interest Satisfaction Rate (ISR) as the basic VNDN. In addition, CONET also minimizes the overall Interest Satisfaction Delay (ISD), respectively.