As a system and Network Administrator , Troubleshooting DNS problems in Active Directory is a crucial skill to have. it requires a systematic approach to identify and resolve the issue.
PROBLEM STATEMENT
An IT Company has reported that users are experiencing difficulties accessing network resources due to DNS resolution FAILURES .The DNS server logs indicate that there are issues with DNS Query timeout and server error. the team needs to identify the root cause of the problems and to resolve it.
CODE: No code is required for this project, as it involves troubleshooting and Configuration of DNS settings.
TO RESOLVE THIS ISSUE:
Step1: Open network and internet settings, click on Network sharing Centre, then click on change adapter settings, choose the network that lit up, right click and go to properties, you will see multiple list of network then you will have to chose the one that have the main ip address on it, chose the IP Version 4 (IPV4) and double click on it and uncheck ipv6. click on 1pv4 properties and input your Ip address.
under DNS ,
There you will see preferred and Alternative DNS. please do not input public dns here, if you put in public dns server you are not going to resolve or replicate anything inside your network, it will also be difficult to find other server, instead add in your ip address.
Now to set this properly go to server manager, go to tools, scroll down to DNS INSIDE the dns right click the server, go properties, if you are using ipv6 leave the box checked for ipv6 but you can uncheck the ip. . but if you are using TCP/IPV4 only check the one ip address you use for TCP/PIV4, Uncheck them with the exception of your main ip address . Next open forwarders, add DNS, Here you can add public DNS, I added 8.8.8.8 which is Google dns and, 4.2.2.2 and 9.9.9.9
Now to know which server I'm to use I will choose the one with the quickest amount of Hops. I will open my command prompt and type tracert -d 8.8.8.8
, same with the other dns.
TO VERIFY RESOLUTION
Monitor DNS Server logs to ensure there are no further errors or warnings.
Top comments (0)