Assume we have foo.example.com, whose value changes unpredictably. 1. Initially, the A record of foo.example.com points to, say 1.2.3.4. 2. Start a grpc client, with the server pointed at foo.example.com:10000. The client fails to connect since there's nothing running at 1.2.3.4:10000. 3. Start a grpc server at an IP address 1.2.3.5:10000. 4. Update the DNS server so that foo.example.com points to 1.2.3.5.
In this situation, the grpc client never seems to discover the server at 1.2.3.5, even when I set the DNS TTL very short. Am I diagnosing the problem correct? And if so, is there a way to work around? -- yaz -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CALsnwnJr7EqEkMfNkyXiu23hRvpy9XbZxgQ55089dJpNaJe6RQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
