Odd questions, what I am missing? [RPC call]

[DaveF]

When using the bitcoin-cli I can use the -rpcconnect to get to an ip of another bitcoind server on the network (192.168.1.50) and it works. When I change that to node50.davetest.local it fails.
If I do a nslookup from exact same prompt for node50.davetest.local I get the correct answer so the machine is querying the correct local DNS server and it is getting the correct answer.

1) As far as I know and can see it should do name resolution, but since this is the 1st time I am actually doing it this way does it, or am I just assuming that it does?

2) If yes are there any limitations to what I can call it? (some things do fail on .local domains but very few) Does it use the system DNS servers or do I have to specify? If so how?

3) Is there anything else I am missing or can check.

For now it's working with IPs so no big deal, I was just trying to keep it a bit cleaner.

Thanks,
Dave

[1714935168]

1714935168

[achow101]

1) As far as I know and can see it should do name resolution, but since this is the 1st time I am actually doing it this way does it, or am I just assuming that it does?

[
You are assuming that it does name resolution, but AFAIK, it does not. Just because a different software does name resolution (indicating that the machine is capable of doing so) does not mean that bitcoin-cli will do name resolution.

[DaveF]

1) As far as I know and can see it should do name resolution, but since this is the 1st time I am actually doing it this way does it, or am I just assuming that it does?

[
You are assuming that it does name resolution, but AFAIK, it does not. Just because a different software does name resolution (indicating that the machine is capable of doing so) does not mean that bitcoin-cli will do name resolution.

Well that is annoying. I was trying to do some load balancing using DNS, since I can set it to spit out IPs in a round-robin.
Guess I just have to code it slightly differently.

Thanks,
Dave