Open sea1jxr opened 6 years ago
Hi @sea1jxr, this is a bug in ServiceFabric. DnsService is not handling properly scenarios where there is an IPv6 address in the DNS chain. Essentially, IPv6 is preferred over IPv4 so the IPv4 address of the node is not the first IP address in the DNS chain. To work around the issue, you can try disabling TCP/IPv6 on the adapter in question (uncheck the "Internet Protocol Version 6 (TCP/IPv6)" box in the adapter properties. That should remove all IPv6 addresses from the DNS chain, which will result in IPv4 address of the node being the first address in the DNS chain.
Thanks, I am only running IPv6 in my development environment so I workaround it there by using "localhost" for the host name. I use dns in production. It would be great to get a fix so I can clean up this code.
Hi @sea1jxr, I am in process of validating a mitigation [using IPv6 address of the host machine and adding that to the DNS server chain of the preferred adapter at index 0 instead]. Based on the testing results we might consider adding to our product logic also.
I have a local 1 node service fabric cluster running ver 6.0.219.9494. When my service is up and running the relevent parts of my ipconfig /all looks like
As you can see that my machine address is 10.125.148.62, and is added as the third entry on the DNS Servers list after the IPv6 DNS servers. a lookup on the machine can't find the domain
A lookup directly to my machine works
Is there a way to get the DNSService to add the self address to the DNS list before the IPv6 DNS Servers? Is there another solution?