SCCM cient DNS issue RRS feed

  • Question

  • I am doing sccm client installation manually issue is below 

    DNS: hostname to IP address is resolving correct but IP address to hostname is not resolving it will impact SCCM client installations and SCCM software update, software distribution will work?

    Friday, September 7, 2018 3:29 AM

All replies

  • Hello

    When ConfigMgr or any process attempts to connect to a resource, it must *always* resolve the hostname to an IP Address. This is basic networking and cannot be avoided. If your DNS does not accurately reflect the IP address of a hostname, that is a DNS issue and will/could affect any application/service/process attempting to communicate with that system by hostname. There are times when ConfigMgr will explicitly create a DDR for an IP Address, but this has nothing to do with a failure to communicate with the host via hostname

    Regards, Regin Ravi

    Friday, September 7, 2018 7:22 AM
  • > " IP address to hostname is not resolving"

    That's a reverse DNS lookup and is irrelevant for ConfigMgr operations (as well as most network operations).

    Jason | https://home.configmgrftw.com | @jasonsandys

    • Proposed as answer by Dan Padgett Sunday, September 9, 2018 6:33 PM
    Friday, September 7, 2018 2:17 PM
  • Ok means SCCM client installation or SCCM client and server communication should work?
    Saturday, September 8, 2018 7:58 AM
  • Both.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Saturday, September 8, 2018 7:23 PM
  • Its very old thread but for my knowledge, can you explain the need/important of DNS Reverse and Forward lookup zone in SCCM client communication or any SCCM activities?

    We appreciate your answer.

    Friday, April 17, 2020 7:05 AM
  • It's the same as any other application running on any network and implemented in the last 25 years: https://en.wikipedia.org/wiki/Domain_Name_System

    Jason | https://home.configmgrftw.com | @jasonsandys

    Friday, April 17, 2020 1:37 PM
  • Hi Smith, 

    Yes this will definitely impact any SCCM related activities, first you need to get the SCCM client to be healthy to be able to do any activity related to SCCM. I had the same issue and i followed below basic steps and it worked for me in 99% percent cases, in this particular scenario:

    1. Delete the entry (MachineName/Hostname) from DNS records. ie DNS server.

    2. After deleting it from DNS, delete the entry from SCCM console (Which has NO client on it, this i am saying based on you current scenario of the host).

    3. Now discover the client is SCCM and check the IPaddress/hsotname resolution it should show healthy to you, and you are good to start your deployments of software updates/Software Distribution.


    Naren Nadh

    • Proposed as answer by Naren.nadh Saturday, May 23, 2020 10:05 AM
    Wednesday, May 20, 2020 9:19 PM