Instant Infrastructure
Registration failure using internal DNS ServerSubmitted by bveenstra on Fri, 06/08/2007 - 9:30pm.Registration failure using internal DNS Server |
Search |
Registration failure using internal DNS ServerSubmitted by bveenstra on Fri, 06/08/2007 - 9:30pm.Registration failure using internal DNS Server |
Search |
the registration need the ip address for register this connect
suffix in dns registration
Registration failure using internal DNS Server
If your DHCP server provides a DNS server it will use it regardless of its IP address. It sounds like it didn't get an IP to a valid DNS server or something else was preventing name resolution.
There is an Info page in the JumpBox administration interface that shows the DNS servers it is using, you could use those and test manually to see that what it is given works. But it seems your issue is resolved in any case.
Good luck
Austin
Registration failure using internal DNS Server
I just tried registering with network settings that my workstations use behind the firewall.
I was unable to register with the error message “Unable to connect to JumpBox update server: getaddrinfo: Name or service not knownâ€.
Once I plugged in my cable modem's DNS server, I registered just fine. Why doesn't the JumpBox registration process support the private (e.g. 192.168.x.x) IPs for DNS server?