Nav 2017 Server not found when using dns alias

(0) Share

Report

Posted on by mncomputerguy

I'm running into a weird error with a new nav 2017 install.

The service tier servers fqdn is servernavapp.contoso.com and the port is 7050 for client services. That works fine when connecting the nav client to servernavapp.constoso.com:7050/test. The server is also using a wildcard *.contoso.com ssl cert.

However we want to use a shorter url so we put a dns record in for nav.contoso.com. When using the url nav.contoso.com:7050/test we get the "a server was not found" error.

The dns alias works fine when connecting via nav web client (https://nav.contoso.com/test). I can also ping via the nav.contoso.com name and if i do a "telnet nav.contoso.com 7050" the port shows as responding. Its only the nav client that will not connect using this dns alias name.

I'm stumped, we have this setup for multiple customers with no issues.

*This post is locked for comments

All responses (1)

Answers (0)

mncomputerguy 46 on at

Like (0)

Report

RE: Nav 2017 Server not found when using dns alias

Well, the shortname works everywhere thankfully except when running the client on the service tier server itself. On the service tier we can only use fqdn, localhost or the ip address, the alias simply does not work.

not sure if this is a delegation issue or what.