Coldfusion can't resolve domain names

We are recently going through some Active Directory changes out in our
centers.  We have Coldfusion MX 6.0 running on some servers that are
affected.  What has happened now twice, once yesterday and then again this
morning is that coldfusion doesn't seem to be able to resolve the MySQL
server.  I am going to try and explain the situation and please let me know
if you need any other information or if you have any information regarding
the root cause:

We have Coldfusion MX 6.0 running on a solaris server,
naoweb01.novusservices.com.  This server makes calls to a MySQL databases
that reside on the server naoweb02.  On the actual solaris
server, naoweb01, I was able to do run an nslookup on naoweb02 and
naoweb02.novusservices.  Both resolved properly.  I was also able to
connect to the MySQL port  from naoweb01, by running the following from
naoweb01: telnet naoweb02  or telnet naoweb02.novusservices.

But all of the datasources in the coldfusion failed when I tried to verify
them.  Also, it would work if the server was naoweb02, but it wouldn't work
if it was naoweb02.novusservices.com.  So if it was fully qualified it would
not work.  I restarted coldfusion once and it still didn't work. Then I
killed the coldfusion processes and started up coldfusion and it worked.

Is there any reason why coldfusion would not be able to resolve a fully
qualified domain name?  How does coldfusion resolve a domain name?  If this
happens again, is there a test page, some coldfusion code, or extra
troubleshooting we can do that could help us find the root cause?

Thanks,
veeroyAsked:
Who is Participating?
 
Tacobell777Commented:
I don't think this has to do with coldfusion...
More like a problem in your DNS which needs to be resolved..
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.