none
DNS resolves but doesn't resolve RRS feed

  • Question

  • We have an internal server that one of our applications connects to to retrieve images. This server is not joined to any AD domain.  

    Within the application when a user tries to access an image the application attempts to retrieve the image from http://server. This has worked in the past but now it is not working now.

    We have static internal DNS setup for http://server .

    I am able to ping "server" and it resolves to the correct IP. Also if I ping "server.domain.com" it correctly resolves as well.

    The only way I am able to retrieve images is if I open a web browser and enter the http://server.domain.com. 

    When users try to open images within the application they receive the attached error message.

    We have contacted the vendor to try to make changes to the link used within the application but they have been VERY slow to respond.


    • Edited by sapper12 Friday, December 23, 2016 3:36 PM
    Friday, December 23, 2016 3:35 PM

All replies

  • add domain.com suffix in nic properties
    Friday, December 23, 2016 3:50 PM
  • On the server hosting the images or the users computer?

    Already tried it on the users computer with the same results.

    Friday, December 23, 2016 3:56 PM
  • use host file and add the server entry like below "IP FQDN SERVERNAME"  this is will check the ip with server full name & host name aswell

    10.1.1.1 server.domain.com server 

    Saturday, December 24, 2016 12:36 AM
  • Hi Sapper,

    >>This has worked in the past but now it is not working now.

    Have you perform any operation before it did not work?

    >>When users try to open images within the application they receive the attached error message.

    You could catch traffic of application and check if which steps occurred issue.

    Best Regards

    John


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, December 26, 2016 2:31 AM
  • Hello.

    Instead of using PING to test name resolution, you should use NSLOOKUP. PING can resort to using any of a number of name resolution methods but NSLOOKUP will only use DNS.

    I do not recommend using the hosts file for a number of reasons.

    If you could share the output of IPCONFIG /ALL and NSLOOKUP from one of the clients, that might help with diagnosing the issue.

    Thanks

    Ed

    Monday, December 26, 2016 10:35 PM
  • Information has been edited for security.

    NSLOOKUP:

    C:\Users\>nslookup server
    Server:  dc01.domain.com
    Address:  192.168.1.2

    Name:    server.domain.com
    Address:  192.168.1.5

    IPCONFIG /All:

    C:\Users\>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : client
       Primary Dns Suffix  . . . . . . . : domain.com
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : domain.com

    Ethernet adapter:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection #2
       Physical Address. . . . . . . . . : 
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.1.18(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.1
       DNS Servers . . . . . . . . . . . : 192.168.1.2
                                                   192.168.1.3
       NetBIOS over Tcpip. . . . . . . . : Enabled


    • Edited by sapper12 Tuesday, December 27, 2016 4:05 PM
    Tuesday, December 27, 2016 4:00 PM
  • I assume that 192.168.1.5 is the correct IP address for the server.

    Is the application locally installed on the clients or is it a web app running on the server that users connect to with a browser?

    Are the images stored on the server with the 192.168.1.5 IP address?

    What OS is the server running and what is it using for a web service?

    Thanks

    Ed


    • Edited by Ed GallagherMVP Wednesday, December 28, 2016 9:55 PM punctuation
    Wednesday, December 28, 2016 9:53 PM
  • Okay, so somehow, and I am still not clear how, but our content filter was the culprit. Once our security person made adjustments we are able to access it.
    Wednesday, December 28, 2016 10:02 PM
  • Good to hear.

    Happy new year.

    Ed

    Wednesday, December 28, 2016 10:07 PM