0

I have set up an Active Directory with DNS Servers on the Domain Controller. I have already joined Computers and DNS works for all machines, even those that are not in the domain. I wanted to setup another Server, a Windows Server 2019 Core, and join it into the Domain. But it cant resolve the Domain name, even tho it can ping all DNS Servers and there are no additional firewall rules in place. Has anyone an idea what the problem is, or what i can do to fix this?

Maleavi Tohl
  • 1
  • 1
  • What is your DNS server set to in the settings of the network adapter? Try doing `nslookup` from the core server to the AD DC – josibu Apr 18 '20 at 19:57
  • it is set to the ip address of the dc. it also says so when is try the command `nslookup corp.example.com` – Maleavi Tohl Apr 18 '20 at 20:05
  • what is the output of the `nslookup` command? – josibu Apr 18 '20 at 20:06
  • ´Server: [192.168.1.1] Address: 192.168.1.1 DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds.` it works on every other machine: > server 192.168.1.1 Standardserver: [192.168.1.1] Address: 192.168.1.1 > corp.example.com Server: [192.168.1.1] Address: 192.168.1.1 Name: corp.example.com Addresses: 192.168.1.1 192.168.1.2 > exit – Maleavi Tohl Apr 18 '20 at 20:13
  • You do not accidentally have an IP address conflict? Did you try doing `nslookup` to a different DNS server? What's the output there? Also, if your DNS server is connected to more than 1 network card, if I remember right, there is setting in the dns server or zone where you can specify on which network the DNS server listens and anwers. – josibu Apr 18 '20 at 20:25
  • seems like the problem was, that the centos router was blocking dns traffic.... what a rookie error D: Thanks for the help anyways :) – Maleavi Tohl Apr 19 '20 at 11:56

0 Answers0