AD DNS What's your flavor?
-
Assuming the clients are all windows machines - definitely have AD do DNS, and probably DHCP too.
If there is a server, I always have the server do DNS/DHCP, and the router just routes/firewalls.
-
If you have nothing but an all in one router/firewall unit, then it's okay to have DHCP there. Otherwise, DHCP, DNS, etc. should always be on a server. Never use a network device as a server unless there is just no other option.
-
Active Directory should always have DNS integrated. AD/DNS is finicky enough without introducing another layer of complexity and potential point of failure.
-
Keep DNS with AD. Keeping DHCP there makes sense too. You want as much integration as possible and the robustness of server-side DNS and DHCP should be far in excess of that from a router.
-
FYI, i'm not asking for advice. just seeing what folks prefer.
-
I tend to agree with @Reid-Cooper
I believe both DHCP and DNS are much easier to scale and mange on Windows.
-
@IRJ said:
I believe both DHCP and DNS are much easier to scale and mange on Windows.
Bwhahahahaha.
Say hello to bind and dhcpd. Bind will scale DNS faster and respond quicker than anything Windows can throw out. I've seen dhcpd hand out class A blocks and exhaust them and ask for more.
The tight integration into AD makes using it on Windows a convenience. Using it on anything else is always available.
-
@PSX_Defector said:
@IRJ said:
I believe both DHCP and DNS are much easier to scale and mange on Windows.
Bwhahahahaha.
Say hello to bind and dhcpd. Bind will scale DNS faster and respond quicker than anything Windows can throw out. I've seen dhcpd hand out class A blocks and exhaust them and ask for more.
The tight integration into AD makes using it on Windows a convenience. Using it on anything else is always available.
I am not familiar with either, but the OP was talking about using DNS and DHCP on his router. Neither Bind or DHCPD.
-
@IRJ said:
@PSX_Defector said:
@IRJ said:
I believe both DHCP and DNS are much easier to scale and mange on Windows.
Bwhahahahaha.
Say hello to bind and dhcpd. Bind will scale DNS faster and respond quicker than anything Windows can throw out. I've seen dhcpd hand out class A blocks and exhaust them and ask for more.
The tight integration into AD makes using it on Windows a convenience. Using it on anything else is always available.
I am not familiar with either, but the OP was talking about using DNS and DHCP on his router. Neither Bind or DHCPD.
What do you think every firmware uses?
Busybox, FreeBSD, WRT, even Cisco and Juniper use custom versions of this on their boxes. The class A DHCP server I've seen? On a Juniper.
Always be familiar with bind and dhcpd, never know when it might be necessary to fix it.
-
@PSX_Defector said:
@IRJ said:
@PSX_Defector said:
@IRJ said:
I believe both DHCP and DNS are much easier to scale and mange on Windows.
Bwhahahahaha.
Say hello to bind and dhcpd. Bind will scale DNS faster and respond quicker than anything Windows can throw out. I've seen dhcpd hand out class A blocks and exhaust them and ask for more.
The tight integration into AD makes using it on Windows a convenience. Using it on anything else is always available.
I am not familiar with either, but the OP was talking about using DNS and DHCP on his router. Neither Bind or DHCPD.
What do you think every firmware uses?
Busybox, FreeBSD, WRT, even Cisco and Juniper use custom versions of this on their boxes. The class A DHCP server I've seen? On a Juniper.
Always be familiar with bind and dhcpd, never know when it might be necessary to fix it.
I had no idea. Networking isnt my area of expertise. I am a Microsoft Server guy
I probably learned it way back when I did networking and Cisco courses, but that was a looong time ago. I haven't done much networking since then.
-
@IRJ said:
I had no idea. Networking isnt my area of expertise. I am a Microsoft Server guy
I was just saying this to my "peers" in a certain subcontinent. insert dripping sarcasm
Knowing the fundamentals of networking allows all of us to be better engineers. Use the OSI model Luke!
Nothing stopping you from understanding bind or dhcpd. Grab a pfSense box and go nuts. It's when you start getting into the fun of deeper networking protocols, like NAT tables and BGP routing, is when you need to be much more dedicated to that discipline. Getting the fundamentals of bind down lets you really know how to troubleshoot a DNS issue. I'm called upon at work for being the "DNS guy". Even moreso than our DNS admins. dhcpd does lots of things and you can learn plenty by using it, even with regards to Windows DHCP services.
Never be afraid to grab something and f[moderated] around with it. Hell, I picked up a Mikrotik router a month ago, haven't touched the OS in a decade or more. After a bit of re-education, I think I can hold my own with it. Although it does load balancing very different than others do, much more traditional.
-
@PSX_Defector said:
@IRJ said:
Never be afraid to grab something and f[moderated] around with it. Hell, I picked up a Mikrotik router a month ago, haven't touched the OS in a decade or more. After a bit of re-education, I think I can hold my own with it. Although it does load balancing very different than others do, much more traditional.
I am not disagreeing with you at all. I have been using exclusively Ubuntu at home to understand linux better. Sure I have to use google alot, but in the last few months I have learned quite a bit
-
I am very strong about using Windows Server for DHCP and DNS. I just like the management features of it better.
-
@IRJ said:
@PSX_Defector said:
@IRJ said:
I believe both DHCP and DNS are much easier to scale and mange on Windows.
Bwhahahahaha.
Say hello to bind and dhcpd. Bind will scale DNS faster and respond quicker than anything Windows can throw out. I've seen dhcpd hand out class A blocks and exhaust them and ask for more.
The tight integration into AD makes using it on Windows a convenience. Using it on anything else is always available.
I am not familiar with either, but the OP was talking about using DNS and DHCP on his router. Neither Bind or DHCPD.
What router would use anything else?
-
I'm not saying Windows over UNIX. I'm just saying servers over network devices.
