Alexander7088

In KeeneticOS 5.0+ a very useful feature was added — domain name based routing (DNS-based routes). However, there is a fundamental issue: the first packet is always sent via the default route. Current behavior: • a client starts a connection • the first TCP SYN is sent via the default interface • only after the DNS response Keenetic adds the routing entry • the second attempt goes through the correct interface As a result: • the first request is often slow or times out • many websites and apps “open on the second try” • network behavior becomes unpredictable Expected behavior: If a domain is listed in domain name routing rules, the very first packet should be routed via the correct interface, not the default one. Suggestion: Implement a mechanism where Keenetic waits for the DNS response and applies the route before sending the first packet, so the connection is correct from the beginning.