Several users may know about public
DNS servers and might experiment with them, but at the same time, they are not having enough capability to select the best suited DNS server for themselves,
in most cases. In such cases, if the chosen DNS server stops working, or the latency to it, increases, the overall user experience, degrades. Some users might even find this to be a problem on our (Excitel's) end.
This is why we prefer to take this burden and provide a DNS service that works all the time and with predictable parameters along with ensuring a high level of service quality. Of course, this comes with the risk that if our DNS servers stops, then users would suffer; but we're ready to take this risk because we believe that ultimately, this is better for our customers.
Furthermore, there's another, very important aspect to this. Many Content Delivery Networks (CDNs) rely on the use of a proper DNS server (which is a part of the ISPs IP pools) by the end users, to effectively determine the best delivery mechanism and shortest distance/latency node to serve traffic to our users. For example, Akamai, that serves local, Indian content from several platforms (including
Hotstar, live cricket) depends heavily on a proper DNS configuration and if the ISP doesn’t enforce their own DNS, and the customer configures some other public DNS server, the Akamai-zed content will be delivered from some NODE far away from the ISP (from ISP users) which will greatly spoil the user experience and furthermore, this will be accounted as Transit traffic, and therefore, would be delivered at the normal internet speed (based on the package) and not the peering speed. In such a situation, we would then be unable to guarantee a proper peering experience/speed to the end-users as promised by the plan that they are using.