@scottalanmiller said in Handling DNS in a Single Active Directory Domain Controller Environment:

@jmoore said in Handling DNS in a Single Active Directory Domain Controller Environment:

We are still a long ways from this being universal. Is that kind of what you meant?

Good design will never be universal. Most networks, most admins, most software will always be bad. Nothing good becomes the norm, not how the world works.

the law of averages apply.

I am also a firm believer in the idea that I am being paid to solve problems. If the company really thinks that I need to be the one fixing the sink, they may have me do that. But in the end, I am valuable for way more than just IT. I get involved in high level business decisions because they value my input.

@dustinb3403 said in User Training Who is responsible:

@scottalanmiller So let me ask you this than.

In the world of not outsourced IT, do you believe that the IT personal should know how to use and operate every piece of software or hardware that a business has?

I believe that I should know everything about everything that is in my environment. This has a lot to do with my lack of trust in people, and that I need to know and understand it for myself. But I also believe that this is just an example of me going above and beyond and taking pride in my work. That being said, I do not know everything about all my things yet, nor is that really physically possible.

@scottalanmiller a few years ago we had a bolt strike the neighbors tree. You could taste the ozone in my house.

I havent watched any MCU or starwars movies since the first avengers. I plan on binge watching them in about a decade.

@scottalanmiller said in Handling DNS in a Single Active Directory Domain Controller Environment:

@donahue said in Handling DNS in a Single Active Directory Domain Controller Environment:

@phlipelder yes, that is probably the last piece I would need before I would switch to using reservations more. I have just never looked it up to make sure it was doable. I like the idea of reservations, but I would also want similar devices in similar parts of the scope for organizational purposes.

Basically, other than for your router and DHCP server, you never need static.

that's basically how I feel now. Now I've just got to change the 40 or so static that I currently have.

@phlipelder yes, that is probably the last piece I would need before I would switch to using reservations more. I have just never looked it up to make sure it was doable. I like the idea of reservations, but I would also want similar devices in similar parts of the scope for organizational purposes.

This is a tangent, but can you tell a DHCP reservation to use a particular IP in the scope? Like if it comes in with something random, you can make a reservation for that mac and then change the IP to something else and restart the device?

@scottalanmiller said in Handling DNS in a Single Active Directory Domain Controller Environment:

@donahue said in Handling DNS in a Single Active Directory Domain Controller Environment:

@dashrender said in Handling DNS in a Single Active Directory Domain Controller Environment:

@donahue said in Handling DNS in a Single Active Directory Domain Controller Environment:

It's anecdotal, but I just had this happen a few weeks ago. In my case I had a host go down that had my AD VM on it. It took me while to get it all resolved, but that is because I had to physically remove my server from the rack to get access to the usb drive where ESXi was installed (we will be getting a new rack soon). DNS was probably the biggest hit because a lot of our internal services use the DNS name.

I'm guessing you'll be like me and updating DHCP to include the router's IP as DNS (assuming yours supports DNS) and having the router point to internal DNS before external. I'm really loving this idea.

So using this example, If the DHCP server (mine is on the AD VM) points first to the router, outside DNS still works if AD goes out. If the router goes down though, internal DNS wont work unless the internal DNS was listed second under DHCP. Does this make sense?

You point to AD first, router second. If the router goes down, you are down either way.

Then the router points to AD first, public second.

We recently had a router outage. I would still want internal DNS so we can still work from internal resources.

@dashrender said in Handling DNS in a Single Active Directory Domain Controller Environment:

@donahue said in Handling DNS in a Single Active Directory Domain Controller Environment:

It's anecdotal, but I just had this happen a few weeks ago. In my case I had a host go down that had my AD VM on it. It took me while to get it all resolved, but that is because I had to physically remove my server from the rack to get access to the usb drive where ESXi was installed (we will be getting a new rack soon). DNS was probably the biggest hit because a lot of our internal services use the DNS name.

I'm guessing you'll be like me and updating DHCP to include the router's IP as DNS (assuming yours supports DNS) and having the router point to internal DNS before external. I'm really loving this idea.

So using this example, If the DHCP server (mine is on the AD VM) points first to the router, outside DNS still works if AD goes out. If the router goes down though, internal DNS wont work unless the internal DNS was listed second under DHCP. Does this make sense?