We have decided it is in our best interest to host a DNS service simultaneously on our Windows domain controller server. Our network needs to be configured to use this new DNS service.
Update our network settings to point to that server. Use MTECH's default DNS as an alternate server. We need to find a way to push our DHCP clients on our Wi-Fi and wired LAN to our internal DNS server. This change will need to take place on the Turris router.
K so here we go, now I am doing AD5. I have no idea what I'm doing. And as established with AD8 I think it was, I am not good at following directions.
But I understand that I need to access the Touris Router, which is a bit of a troublemaker in our class because its always going down while students are working on it because they don't know what they're doing so it has problems I guess. I think it also actually has non-student problems too but idk.
Did some research, said I need to access the router so I thought, oh simple, I just need to make sure I am on the student project network that the router is on, or creates or whatever. I typed in http:// just to research and discover that's unnecessary, then I thought, oh well the IP address is 192.168.3.239 for the Proxmox server, which means the router is the first address on the subnet. SO I typed 192.168.3.0 and it went nowhere. I tried to see if there was some other thing I needed to type after the IP address and nothing I did accessed the router.
Then I tried 192.168.3.1 and all of the sudden I got a page saying this address is unsafe, basically asking what I want to do now. I clicked advanced and it asked if I would like to proceed to said address, I clicked it and it went straight to the router. Since everything is Mtech123 for the password, I just typed that and it worked first try.
I struggled to wrap my head around what was going on after this. I worked out today and for some reason I just had no mental energy so it was like everyone was speaking gibberish to me the whole class.
But what I gathered from the instructions was that you need to set all DHCP clients on the active directory to a certain DNS server, but not on each computer individually, this needs to be a global setting for all DHCP active Directory clients.
I got into the Turris router, password was Mtech123, had to guess it because people were busy and it wasn't written down anywhere. I got in there and looked around for anything regarding DNS. I surfed for a while in what I would later discover was called Reforis, which was pretty watered down, had useful data and stuff like what DHCP clients were using the router, but it was just really watered down, no static IP info for example. It didn't even really look like you could configure very much from it. I discovered however that if you scroll down and go on the side panel to click Advanced Administration, it opened a new window for Turris, but this page is called Luci. And as a matter of fact its good to know that when you are logging into the router, it puts you on a page for 20 or 30 seconds where it lets you pick between Reforis and Luci. Luci actually has the toys to play with.
After much toil, I discovered that you don't want to go to the Network tab and select the DHCP and DNS option, instead you want to go Network tab > Interfaces > select the edit button for the black and green box that says LAN > DHCP server > a new set of tabs below the main set of tabs will appear, here you select Advanced > settings > and at the bottom of the screen I discovered that someone had already completed this ticket because the manually added DNS server IP address was already added and they never resolved the ticket.
In the DHCP-options field at the bottom of the page, "6,192.168.3.177" was entered. Doug saw this and instructed me to check a few things. We needed to know what the IP address of the DNS server was, and we needed to confirm that this manually added address was it.
Doug had me go turn off my VPN on my computer to my home network so the results of the next step wouldn't be confused. This is a thing that only applies to me in particular in class because my laptop and phone are using a VPN back to my home network for adblocking and access to a file server. But otherwise, this doesn't apply to any other students that may read this in class. I turned off my VPN in Wireguard, then went to the command prompt on my laptop and did "nslookup". We were trying to do a reverse lookup and it didn't work, said domain not found. So we went into the router and checked its list of connected devices, we went back to Reforis and checked the DHCP list and it wasn't there but I asked Doug, like, it's a server right? Shouldn't it have a static IP address and he was just waiting for me to figure it out, so we then went into Luci to check and we found the static reservation list, I think it was the bottom most listing on the page and it was called WIN-VM0756L6QJ0. It was a virtual machine. And its WIN, so its a windows server, so we logged into the one windows server that was installed on Proxmox by logging into the console and then we did an IP config in the cmd, and it confirmed that its address was 192.168.3.117.
Job done, piece of cake!
This has been Truncat3d 00000000111100010100110______________end of line
No comments:
Post a Comment