We are running two processes to test our application. It uses a TCP socket to listen (in one process) and dynamically discovers the fully-qualified host name as "appveyor-vm.c.appveyor-ci.internal." (in the second process) but using this host name to connect to the first process fails, as does a ping
Output from ipconfig and ping from test run:
ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : appveyor-vm
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : c.appveyor-ci.internal.
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . : c.appveyor-ci.internal.
Description . . . . . . . . . . . : Red Hat VirtIO Ethernet Adapter
Physical Address. . . . . . . . . : 42-01-0A-F0-00-33
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.240.0.51(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Lease Obtained. . . . . . . . . . : Thursday, December 3, 2015 10:28:20 PM
Lease Expires . . . . . . . . . . : Monday, January 10, 2152 4:58:38 AM
Default Gateway . . . . . . . . . : 10.240.0.1
DHCP Server . . . . . . . . . . . : 169.254.169.254
DNS Servers . . . . . . . . . . . : 169.254.169.254
10.240.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
ping appveyor-vm.c.appveyor-ci.internal.
Ping request could not find host appveyor-vm.c.appveyor-ci.internal.. Please check the name and try again.
Command exited with code 1

#1 Posted by Feodor Fitsner Support staff on 04 Dec, 2015 07:24 PM
I guess this FQDN is the same for all instances. It's a virtual Google Compute Engine network - I'm not sure if we can control that.
#2 Posted by Peter Oschwald on 04 Dec, 2015 08:29 PM
Hi Feodor,
Thanks for your note.
It doesn't seem like it should matter, for our purposes, if all instances
share the same FQDN (the test is contained in one instance). All that
matters is that the FQDN resolves to some valid IP address for the host,
which doesn't seem to be happening. It may be helpful to note that this
was working before (~ a month ago), but recently has stopped.
#3 Posted by Feodor Fitsner Support staff on 04 Dec, 2015 09:01 PM
It was Hyper-V, but now it's GCE - something is different. I will take a look.
- Feodor
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:02 AM.