grahamd22 Posted February 6, 2020 Posted February 6, 2020 Every network computer now has a dns issue as they are all coming up with 'there are no logon servers available' we can't even remove and reconnect as it can't then see the AD/DC. The only change has been transferring our domain details for 365 to RM. I've restarted the servers but no change and RM don't seem to know why this is happening. RM took control of our domain as this seemed the reason why our MX record had stopped some services from running. Could this be the issue or is it just coincidental and should I be speaking to Microsoft first?
psydii Posted February 6, 2020 Posted February 6, 2020 Can the DCs resolve each other? Can the clients ping the DCs by IP? What about by FQDN? Are the clients TCP/IP settings configured by DHCP? Is the scope configured to give the client DNS settings the IP address(es) of your DCs?
djm968 Posted February 7, 2020 Posted February 7, 2020 As above and check that the IP Address info on a client looks ok?
grahamd22 Posted February 7, 2020 Author Posted February 7, 2020 It looks like BT need to update the IPS TAG and Name servers and everything should start working again fingers crossed !
win Posted February 7, 2020 Posted February 7, 2020 Have you flushed the DNS on the workstations and cleared the cache on the DNS server? Workstation: open CMD and then do: ipconfig /flushdns On the server right click on the DNS server then Clear cache
mavhc Posted February 7, 2020 Posted February 7, 2020 Main question is why is your internal DNS being affected by changes to your external DNS, something's set up wrong. You internal DNS should point to your DC, and that's true for the DC themselves as well.
TwistedHelixis Posted February 7, 2020 Posted February 7, 2020 Main question is why is your internal DNS being affected by changes to your external DNS, something's set up wrong. You internal DNS should point to your DC, and that's true for the DC themselves as well. This. It sounds like (could be wrong) that your external DNS is getting sent out to your clients in place of your internal DNS.
Jawloms Posted February 7, 2020 Posted February 7, 2020 As above! I'd type ipconfig on a client and see what its DNS is. If it isn't your internal DNS server (probably your DC) then there's your problem.
grahamd22 Posted February 11, 2020 Author Posted February 11, 2020 The problem was the dns set on the NIC of the server was pointing to an external address rather than itself, thankyou for helping me think clearly but no thanks to the RM third party engineer.
mavhc Posted February 11, 2020 Posted February 11, 2020 They sound like people who should totally be selling a service where they get to do things on your servers
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now