Home Network Setup
-
@dashrender said in Home Network Setup:
@scottalanmiller said in Home Network Setup:
@dashrender said in Home Network Setup:
@scottalanmiller said in Home Network Setup:
@dashrender said in Home Network Setup:
@scottalanmiller said in Home Network Setup:
@dashrender said in Home Network Setup:
If so, does UBNT based gear support dynamic DNS?
DDNS? Like for external use?
So now that we know that Windows can self register with DDNS, thoughts on moving away from Windows based DHCP and DNS for internal networks? Any chance UNBT gear can or ever would support this?
Let's back up. Why would you want this? What's the goal here?
to have a single DHCP/DNS setup for all network devices without paying Windows CALs for non Windows devices (devices that won't be accessing windows services/servers)
That's not a goal, that's a solution. What's the REASON you want any of that?
Seriously? why would I not want to have to buy Windows CALs? really?
What does that have to do with the question?
-
@scottalanmiller said in Home Network Setup:
@dashrender said in Home Network Setup:
@scottalanmiller said in Home Network Setup:
@dashrender said in Home Network Setup:
@scottalanmiller said in Home Network Setup:
@dashrender said in Home Network Setup:
@scottalanmiller said in Home Network Setup:
@dashrender said in Home Network Setup:
If so, does UBNT based gear support dynamic DNS?
DDNS? Like for external use?
So now that we know that Windows can self register with DDNS, thoughts on moving away from Windows based DHCP and DNS for internal networks? Any chance UNBT gear can or ever would support this?
Let's back up. Why would you want this? What's the goal here?
to have a single DHCP/DNS setup for all network devices without paying Windows CALs for non Windows devices (devices that won't be accessing windows services/servers)
That's not a goal, that's a solution. What's the REASON you want any of that?
Seriously? why would I not want to have to buy Windows CALs? really?
What does that have to do with the question?
The question is - how do I provide DHCP/DNS services to devices that will never otherwise talk to a Windows system hence requiring a Windows CAL license.
-
@dashrender said in Home Network Setup:
@dashrender said in Home Network Setup:
@scottalanmiller said in Home Network Setup:
@dashrender said in Home Network Setup:
@scottalanmiller said in Home Network Setup:
@dashrender said in Home Network Setup:
@scottalanmiller said in Home Network Setup:
@dashrender said in Home Network Setup:
If so, does UBNT based gear support dynamic DNS?
DDNS? Like for external use?
So now that we know that Windows can self register with DDNS, thoughts on moving away from Windows based DHCP and DNS for internal networks? Any chance UNBT gear can or ever would support this?
Let's back up. Why would you want this? What's the goal here?
to have a single DHCP/DNS setup for all network devices without paying Windows CALs for non Windows devices (devices that won't be accessing windows services/servers)
That's not a goal, that's a solution. What's the REASON you want any of that?
Seriously? why would I not want to have to buy Windows CALs? really?
Perhaps it's a non issue - I have user based CALs, and assuming I only allow users on my network, they would already be covered. So I perhaps don't have a real need for this??
The question is only this....
Why do you want dynamically updated DNS on your network?
If your goal is to replace Windows, ask how to do that, not how to do this thing. This is in the weeds. This is a technical piece, not a goal itself. Who cares about this if you don't need it?
-
@dashrender said in Home Network Setup:
@scottalanmiller said in Home Network Setup:
@dashrender said in Home Network Setup:
@scottalanmiller said in Home Network Setup:
@dashrender said in Home Network Setup:
@scottalanmiller said in Home Network Setup:
@dashrender said in Home Network Setup:
If so, does UBNT based gear support dynamic DNS?
DDNS? Like for external use?
So now that we know that Windows can self register with DDNS, thoughts on moving away from Windows based DHCP and DNS for internal networks? Any chance UNBT gear can or ever would support this?
Let's back up. Why would you want this? What's the goal here?
to have a single DHCP/DNS setup for all network devices without paying Windows CALs for non Windows devices (devices that won't be accessing windows services/servers)
That's not a goal, that's a solution. What's the REASON you want any of that?
Seriously? why would I not want to have to buy Windows CALs? really?
The reason is to be able to use hostnames as opposed to IP addresses. Windows accomplishes this via their Dynamic Updates (which is not DDNS that's something completely different) so machines will auto-update their own DNS entries like they currently do with Windows DNS and Windows DHCP. As far as I'm aware the DHCP server doesn't actually do updates to the DNS records the clients do the updates.
-
@dashrender said in Home Network Setup:
@scottalanmiller said in Home Network Setup:
@dashrender said in Home Network Setup:
@scottalanmiller said in Home Network Setup:
@dashrender said in Home Network Setup:
@scottalanmiller said in Home Network Setup:
@dashrender said in Home Network Setup:
@scottalanmiller said in Home Network Setup:
@dashrender said in Home Network Setup:
If so, does UBNT based gear support dynamic DNS?
DDNS? Like for external use?
So now that we know that Windows can self register with DDNS, thoughts on moving away from Windows based DHCP and DNS for internal networks? Any chance UNBT gear can or ever would support this?
Let's back up. Why would you want this? What's the goal here?
to have a single DHCP/DNS setup for all network devices without paying Windows CALs for non Windows devices (devices that won't be accessing windows services/servers)
That's not a goal, that's a solution. What's the REASON you want any of that?
Seriously? why would I not want to have to buy Windows CALs? really?
What does that have to do with the question?
The question is - how do I provide DHCP/DNS services to devices that will never otherwise talk to a Windows system hence requiring a Windows CAL license.
And my question is going to keep being "Why do you care?"
-
@coliver said in Home Network Setup:
The reason is to be able to use hostnames as opposed to IP addresses.
Still not a goal. Why does your CEO want this?
-
@scottalanmiller I’m confused also
-
@scottalanmiller said in Home Network Setup:
@coliver said in Home Network Setup:
The reason is to be able to use hostnames as opposed to IP addresses.
Still not a goal. Why does your CEO want this?
Scott - please don't inject someone else into this conversation. This is a theoretical question, nothing more.
If you need a real situation here you go.
You have a warehouse, you have warehouse people and office people. The warehouse people use hand scanners that get DHCP assigned addresses, but otherwise do not use and Windows services (nor do the users). These devices are on the same network as laptops for the office workers.
Assuming Windows Server is providing DHCP/DNS to those hand held device, you need a Windows Server CAL for each and every one. Solve for x.
-
@dashrender said in Home Network Setup:
@scottalanmiller said in Home Network Setup:
@coliver said in Home Network Setup:
The reason is to be able to use hostnames as opposed to IP addresses.
Still not a goal. Why does your CEO want this?
Scott - please don't inject someone else into this conversation. This is a theoretical question, nothing more.
If you need a real situation here you go.
You have a warehouse, you have warehouse people and office people. The warehouse people use hand scanners that get DHCP assigned addresses, but otherwise do not use and Windows services (nor do the users). These devices are on the same network as laptops for the office workers.
Assuming Windows Server is providing DHCP/DNS to those hand held device, you need a Windows Server CAL for each and every one. Solve for x.
Nah, that breaks what you're after. DHCP can hand out IP addresses. That's not in question right?
-
@dashrender said in Home Network Setup:
@scottalanmiller said in Home Network Setup:
@coliver said in Home Network Setup:
The reason is to be able to use hostnames as opposed to IP addresses.
Still not a goal. Why does your CEO want this?
Scott - please don't inject someone else into this conversation. This is a theoretical question, nothing more.
And in any theoretical IT discussion, there needs to be a business goal (e.g. it matters to your CEO.) And in your question, there is none. The question doesn't make sense because you are asking "how do I do a technical thing" that doesn't make sense to want to do in the way you are asking it.
Can it be done? Sure. Would you ever want it? Not the way you are asking, no.
-
@dashrender said in Home Network Setup:
You have a warehouse, you have warehouse people and office people. The warehouse people use hand scanners that get DHCP assigned addresses, but otherwise do not use and Windows services (nor do the users). These devices are on the same network as laptops for the office workers.
Assuming Windows Server is providing DHCP/DNS to those hand held device, you need a Windows Server CAL for each and every one. Solve for x.
I already did. Stop using DNS for this. There is no purpose to DNS. Period. That's the issue. Again, a false assumption. You assume DNS plays a role here, it does not. Plain and simple.
So you are scratching an itch that doesn't exist. Hence why I keep harping about the goal. Since you simple fix the problem by not trying to do this, what am I missing?
-
Patient: "It hurts when I hit myself in the head."
Doctor: "Stop hitting yourself in the head." -
In a normal network, with scanners on DHCP, that isn't a Windows network, there is no such need as this, the very idea sounds so silly. Given that avoiding the Windows CALs here is automatic and the default, do you see why it's confusing that there is nothing to answer other than "don't do that?"
-
@scottalanmiller said in Home Network Setup:
Patient: "It hurts when I hit myself in the head."
Doctor: "Stop hitting yourself in the head."Just becomes a problem, if someone hits you in the head lol...
-
I know what is going on here. There is a false assumption being added, and totally unstated, and it is the bases for all of the conclusions. Ready...
A few people are assuming Active Directory here, and have never mentioned it.
-
Problem with the AD assumption:
- It is never mentioned, at all. Not even hinted at.
- Replacing DNS and DHCP alone don't fix the need to replace AD, so don't solve the CAL issue as asked.
-
@scottalanmiller said in Home Network Setup:
In a normal network, with scanners on DHCP, that isn't a Windows network, there is no such need as this, the very idea sounds so silly. Given that avoiding the Windows CALs here is automatic and the default, do you see why it's confusing that there is nothing to answer other than "don't do that?"
So you're saying the scanners go on their own network, and the windows laptop is on a separate network - so non issue, since the scanner network can use some other DHCP/DNS service that has no licensing fee?
-
@scottalanmiller said in Home Network Setup:
Here is the alternate.... on a non-Windows network, I don't want DNS listing random dynamic guests. That's the simplest solution. Windows does something I have no desire to have. Given that I don't know what purpose it serves, it's hard to figure out what you are actually looking to accomplish.
Windows DNS can be set to only allow secure dynamic updates, non secure dynamic updates, none. I think the default is secure dynamic updates.
-
@scottalanmiller said in Home Network Setup:
Problem with the AD assumption:
- It is never mentioned, at all. Not even hinted at.
- Replacing DNS and DHCP alone don't fix the need to replace AD, so don't solve the CAL issue as asked.
NO - that is an assumption now on your part - I'm talking about using Windows Server to provide DHCP and DNS. Now granted - why in the world would you do this if you don't have AD, you wouldn't, so the chances are great that AD is being used for the Windows machines, but still not really relevant to the question.
-
So, in the real world, where we work from business goals, we have two basic things we would do. Neither matches what is asked.
-
Non-AD Network (the one we are dealing with here.) There is no value or purpose to DDNS in this scenario. You have no problem to solve. Simply remove the Windows servers and go to normal, everyday DHCP and DNS. Ubiquiti, Linux VMs, everything already handle this perfectly well. There is nothing for the industry to improve here.
-
AD Network (not the scenario we are discussing.) External DNS and DHCP cannot handle the updates for this, this is a limitation of the architecture and is not related to Windows or Linux. In this case, AD itself, not DHCP, has to update DNS and in both Windows and Linux cases, does so automatically as DNS must be part of AD. This is all transparent and cannot be handled by external DNS servers. Linux via Samba4, the only way to get AD apart from Windows own AD, has both the DNS server and the AD-pushed updates to it all included in the same package, all working out of the box as it has to by definition in being an AD replacement. So in this scenario, there is nothing to change or configure and would be handled automatically when needed by the nature of having implemented AD.
-
