Hairpin routing
-
@scottalanmiller said:
@Jason said:
We use .local but also have a lot of macs and it sucks.
Recommendation from MS anymore is internal.domain.com or something similar
A lot of people use ad.domain.com mostly because it is short.
That is what I use on new stuff, for exactly that reason, it is short.
-
@JaredBusch said:
@scottalanmiller said:
@Jason said:
We use .local but also have a lot of macs and it sucks.
Recommendation from MS anymore is internal.domain.com or something similar
A lot of people use ad.domain.com mostly because it is short.
That is what I use on new stuff, for exactly that reason, it is short
literally ad.domain.com?
-
This post is deleted! -
@Dashrender said:
@JaredBusch said:
@scottalanmiller said:
@Jason said:
We use .local but also have a lot of macs and it sucks.
Recommendation from MS anymore is internal.domain.com or something similar
A lot of people use ad.domain.com mostly because it is short.
That is what I use on new stuff, for exactly that reason, it is short
literally ad.domain.com?
Where "domain.com" is your domain, yes.
-
@scottalanmiller said:
@Dashrender said:
@JaredBusch said:
@scottalanmiller said:
@Jason said:
We use .local but also have a lot of macs and it sucks.
Recommendation from MS anymore is internal.domain.com or something similar
A lot of people use ad.domain.com mostly because it is short.
That is what I use on new stuff, for exactly that reason, it is short
literally ad.domain.com?
Where "domain.com" is your domain, yes.
Yes.
-
So those of you that have had a domain for over a decade, have you all moved to new domains to follow this newish domain naming.
-
@Dashrender said:
So those of you that have had a domain for over a decade, have you all moved to new domains to follow this newish domain naming.
We've had ours well over a decade and it was already very much warned by MS not to do split horizon and they had been telling us .local was the way to go. I actually don't remember there ever being a time that they didn't warn against using your domain name. I started working with AD in beta in 1999 and by then I believe we were already warned. I've been on AD since Windows 2000 and the very first materials I saw from MS the number one thing that they trained you on when you did your first research was not to do that. We've been on AD for thirteen or more years of the same domain at NTG and have always been on .local.
-
@Dashrender said:
So those of you that have had a domain for over a decade, have you all moved to new domains to follow this newish domain naming.
Why would you spend tyhe money to move to a new domain structure? Sure if you are going to be redoing things for other reason, but their is no technical reason to move an existing domain that I am aware of.
-
I agree with Jared, best practice is to do one thing, but once the wrong thing is done, you pretty much just live with it. The negatives are there, but aren't generally dramatic. Just make sure new domains don't have overlapping domains with existing ones.
-
@scottalanmiller said:
I agree with Jared, best practice is to do one thing, but once the wrong thing is done, you pretty much just live with it. The negatives are there, but aren't generally dramatic. Just make sure new domains don't have overlapping domains with existing ones.
Almost all of my clients are on .local for example. They are because they used to be on SBS and that is how SBS set it up by default. The #1 rule of SBS was to always follow the wizards unless you wanted to spend a lot of time doing shit manually.
-
Definitely most everyone that I have seen is on .local. It was the advised standard for so long and it was so during the era when the majority of companies moved to AD. Even though the new standard has been around for a little bit now, nearly every company I deal with moved to AD prior to that time period. New companies get new AD, obviously, but as a market percentage they aren't so much yet, that I've seen.
