DNS Update Issue
-
@PhlipElder said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
Simple case of me never doing this wrong I guess. What a weird thing to screw up. Didn't really have time to sift through it all.
What do you normally use for your top level domain on an AD build?
ad.domain.com theoretically. Everything I've ever touched is already in place. Although i'd love to rebuild my families infrastructure from the ground up.
If it looks like this, then it owns domain.com
Oh man, what a mess.
Meh, not bad actually. Perfect? No. But small enough to not be a problem really.
Definitely not what I would do now if I set it up new.
-
@JaredBusch said in DNS Update Issue:
@PhlipElder said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
Simple case of me never doing this wrong I guess. What a weird thing to screw up. Didn't really have time to sift through it all.
What do you normally use for your top level domain on an AD build?
ad.domain.com theoretically. Everything I've ever touched is already in place. Although i'd love to rebuild my families infrastructure from the ground up.
If it looks like this, then it owns domain.com
Oh man, what a mess.
Meh, not bad actually. Perfect? No. But small enough to not be a problem really.
Definitely not what I would do now if I set it up new.
Okay, the masking threw me off.
_msdcs.domain.local
domain.com
domain.local
^^Zones?Why domain.com?
When we split DNS we usually leave domain.com to Internet DNS even if Location.Domain.Com is internal.
Then we set up the required internal DNS FLZs for services:
Remote.Domain.Com
SharePoint.Domain.Com
Mail.Domain.Com
LoB.Domain.ComApplication Request Routing (ARR) is used to parlay incoming HTTPS calls to their respective owners (RDS, Exchange, SharePoint, LoB) so we only require one WAN IP address with Internet DNS A records for the above pointing to the WAN IP address.
EDIT: To get around the AutoDiscover.Domain.Com we use the _autodiscover SRV record method.
-
@PhlipElder said in DNS Update Issue:
Are these Active Directory based domain controllers with AD integrated DNS set up?
Then DNS0 on all DCs should point to itself only. By default no other DNS server IP entry should be set on the NIC other than 127.0.0.1. Ever.
loopback address on multiple domain controllers as primary? Contrary to everything I have read. Discussing with Jared right now.
-
I have no idea why I had this misconception. So I have been doing this incorrectly. Loopback addresses on all DC's. I just realized that there is no benefit to anything else.
-
@PhlipElder said in DNS Update Issue:
Why domain.com?
I didn't set it up. THis is how I acquired it.
Not worth the effort to change everything.
Exchange 2007 was also installed on a DC. /sigh
-
@JaredBusch said in DNS Update Issue:
Exchange 2007 was also installed on a DC. /sigh
That's especially rough. I thought a file server was bad.
-
@JaredBusch said in DNS Update Issue:
@PhlipElder said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
Simple case of me never doing this wrong I guess. What a weird thing to screw up. Didn't really have time to sift through it all.
What do you normally use for your top level domain on an AD build?
ad.domain.com theoretically. Everything I've ever touched is already in place. Although i'd love to rebuild my families infrastructure from the ground up.
If it looks like this, then it owns domain.com
Oh man, what a mess.
Meh, not bad actually. Perfect? No. But small enough to not be a problem really.
Definitely not what I would do now if I set it up new.
This is just a throw back to the new days of AD. MS suggested just this - then after a while they suggested domain.local for the internal domain, and now they recommend ad.domain.com for the internal domain.
-
@Dashrender said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@PhlipElder said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
Simple case of me never doing this wrong I guess. What a weird thing to screw up. Didn't really have time to sift through it all.
What do you normally use for your top level domain on an AD build?
ad.domain.com theoretically. Everything I've ever touched is already in place. Although i'd love to rebuild my families infrastructure from the ground up.
If it looks like this, then it owns domain.com
Oh man, what a mess.
Meh, not bad actually. Perfect? No. But small enough to not be a problem really.
Definitely not what I would do now if I set it up new.
This is just a throw back to the new days of AD. MS suggested just this - then after a while they suggested domain.local for the internal domain, and now they recommend ad.domain.com for the internal domain.
MS originally suggested domain.local and stuck to it for a long time. That's how it started.
-
@scottalanmiller said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@PhlipElder said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
Simple case of me never doing this wrong I guess. What a weird thing to screw up. Didn't really have time to sift through it all.
What do you normally use for your top level domain on an AD build?
ad.domain.com theoretically. Everything I've ever touched is already in place. Although i'd love to rebuild my families infrastructure from the ground up.
If it looks like this, then it owns domain.com
Oh man, what a mess.
Meh, not bad actually. Perfect? No. But small enough to not be a problem really.
Definitely not what I would do now if I set it up new.
This is just a throw back to the new days of AD. MS suggested just this - then after a while they suggested domain.local for the internal domain, and now they recommend ad.domain.com for the internal domain.
MS originally suggested domain.local and stuck to it for a long time. That's how it started.
Pretty sure domain.local wasn't the thing in Windows 2000 days, that came in 2003 and lasted, as you said, a long time.
-
@Dashrender said in DNS Update Issue:
@scottalanmiller said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@PhlipElder said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
Simple case of me never doing this wrong I guess. What a weird thing to screw up. Didn't really have time to sift through it all.
What do you normally use for your top level domain on an AD build?
ad.domain.com theoretically. Everything I've ever touched is already in place. Although i'd love to rebuild my families infrastructure from the ground up.
If it looks like this, then it owns domain.com
Oh man, what a mess.
Meh, not bad actually. Perfect? No. But small enough to not be a problem really.
Definitely not what I would do now if I set it up new.
This is just a throw back to the new days of AD. MS suggested just this - then after a while they suggested domain.local for the internal domain, and now they recommend ad.domain.com for the internal domain.
MS originally suggested domain.local and stuck to it for a long time. That's how it started.
Pretty sure domain.local wasn't the thing in Windows 2000 days, that came in 2003 and lasted, as you said, a long time.
In 2000, it was simply
domain -
@JaredBusch said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@scottalanmiller said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@PhlipElder said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
Simple case of me never doing this wrong I guess. What a weird thing to screw up. Didn't really have time to sift through it all.
What do you normally use for your top level domain on an AD build?
ad.domain.com theoretically. Everything I've ever touched is already in place. Although i'd love to rebuild my families infrastructure from the ground up.
If it looks like this, then it owns domain.com
Oh man, what a mess.
Meh, not bad actually. Perfect? No. But small enough to not be a problem really.
Definitely not what I would do now if I set it up new.
This is just a throw back to the new days of AD. MS suggested just this - then after a while they suggested domain.local for the internal domain, and now they recommend ad.domain.com for the internal domain.
MS originally suggested domain.local and stuck to it for a long time. That's how it started.
Pretty sure domain.local wasn't the thing in Windows 2000 days, that came in 2003 and lasted, as you said, a long time.
In 2000, it was simply
domainMan - I know that a TON of people did that - but I didn't think that was the actual recommendation. I guess I'd have to find some old Win2K docs....
-
@Dashrender said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@scottalanmiller said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@PhlipElder said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
Simple case of me never doing this wrong I guess. What a weird thing to screw up. Didn't really have time to sift through it all.
What do you normally use for your top level domain on an AD build?
ad.domain.com theoretically. Everything I've ever touched is already in place. Although i'd love to rebuild my families infrastructure from the ground up.
If it looks like this, then it owns domain.com
Oh man, what a mess.
Meh, not bad actually. Perfect? No. But small enough to not be a problem really.
Definitely not what I would do now if I set it up new.
This is just a throw back to the new days of AD. MS suggested just this - then after a while they suggested domain.local for the internal domain, and now they recommend ad.domain.com for the internal domain.
MS originally suggested domain.local and stuck to it for a long time. That's how it started.
Pretty sure domain.local wasn't the thing in Windows 2000 days, that came in 2003 and lasted, as you said, a long time.
In 2000, it was simply
domainMan - I know that a TON of people did that - but I didn't think that was the actual recommendation. I guess I'd have to find some old Win2K docs....
I inherited a server 2003 that was set up like that.
-
@Dashrender said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@scottalanmiller said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@PhlipElder said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
Simple case of me never doing this wrong I guess. What a weird thing to screw up. Didn't really have time to sift through it all.
What do you normally use for your top level domain on an AD build?
ad.domain.com theoretically. Everything I've ever touched is already in place. Although i'd love to rebuild my families infrastructure from the ground up.
If it looks like this, then it owns domain.com
Oh man, what a mess.
Meh, not bad actually. Perfect? No. But small enough to not be a problem really.
Definitely not what I would do now if I set it up new.
This is just a throw back to the new days of AD. MS suggested just this - then after a while they suggested domain.local for the internal domain, and now they recommend ad.domain.com for the internal domain.
MS originally suggested domain.local and stuck to it for a long time. That's how it started.
Pretty sure domain.local wasn't the thing in Windows 2000 days, that came in 2003 and lasted, as you said, a long time.
In 2000, it was simply
domainMan - I know that a TON of people did that - but I didn't think that was the actual recommendation. I guess I'd have to find some old Win2K docs....
I don't know about MS recommendation, but when I was setting up NT4 networks prior to 2000, it was the recommendation from the company on how to setup their stuff.
-
@JaredBusch said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@scottalanmiller said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@PhlipElder said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
Simple case of me never doing this wrong I guess. What a weird thing to screw up. Didn't really have time to sift through it all.
What do you normally use for your top level domain on an AD build?
ad.domain.com theoretically. Everything I've ever touched is already in place. Although i'd love to rebuild my families infrastructure from the ground up.
If it looks like this, then it owns domain.com
Oh man, what a mess.
Meh, not bad actually. Perfect? No. But small enough to not be a problem really.
Definitely not what I would do now if I set it up new.
This is just a throw back to the new days of AD. MS suggested just this - then after a while they suggested domain.local for the internal domain, and now they recommend ad.domain.com for the internal domain.
MS originally suggested domain.local and stuck to it for a long time. That's how it started.
Pretty sure domain.local wasn't the thing in Windows 2000 days, that came in 2003 and lasted, as you said, a long time.
In 2000, it was simply
domainMan - I know that a TON of people did that - but I didn't think that was the actual recommendation. I guess I'd have to find some old Win2K docs....
I don't know about MS recommendation, but when I was setting up NT4 networks prior to 2000, it was the recommendation from the company on how to setup their stuff.
NT4, yes. But it behaved differently. AD I thought started with the .local recommendation.
-
@scottalanmiller said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@scottalanmiller said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@PhlipElder said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
Simple case of me never doing this wrong I guess. What a weird thing to screw up. Didn't really have time to sift through it all.
What do you normally use for your top level domain on an AD build?
ad.domain.com theoretically. Everything I've ever touched is already in place. Although i'd love to rebuild my families infrastructure from the ground up.
If it looks like this, then it owns domain.com
Oh man, what a mess.
Meh, not bad actually. Perfect? No. But small enough to not be a problem really.
Definitely not what I would do now if I set it up new.
This is just a throw back to the new days of AD. MS suggested just this - then after a while they suggested domain.local for the internal domain, and now they recommend ad.domain.com for the internal domain.
MS originally suggested domain.local and stuck to it for a long time. That's how it started.
Pretty sure domain.local wasn't the thing in Windows 2000 days, that came in 2003 and lasted, as you said, a long time.
In 2000, it was simply
domainMan - I know that a TON of people did that - but I didn't think that was the actual recommendation. I guess I'd have to find some old Win2K docs....
I don't know about MS recommendation, but when I was setting up NT4 networks prior to 2000, it was the recommendation from the company on how to setup their stuff.
NT4, yes. But it behaved differently. AD I thought started with the .local recommendation.
We have a .local here
-
@wirestyle22 said in DNS Update Issue:
@scottalanmiller said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@scottalanmiller said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@PhlipElder said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
Simple case of me never doing this wrong I guess. What a weird thing to screw up. Didn't really have time to sift through it all.
What do you normally use for your top level domain on an AD build?
ad.domain.com theoretically. Everything I've ever touched is already in place. Although i'd love to rebuild my families infrastructure from the ground up.
If it looks like this, then it owns domain.com
Oh man, what a mess.
Meh, not bad actually. Perfect? No. But small enough to not be a problem really.
Definitely not what I would do now if I set it up new.
This is just a throw back to the new days of AD. MS suggested just this - then after a while they suggested domain.local for the internal domain, and now they recommend ad.domain.com for the internal domain.
MS originally suggested domain.local and stuck to it for a long time. That's how it started.
Pretty sure domain.local wasn't the thing in Windows 2000 days, that came in 2003 and lasted, as you said, a long time.
In 2000, it was simply
domainMan - I know that a TON of people did that - but I didn't think that was the actual recommendation. I guess I'd have to find some old Win2K docs....
I don't know about MS recommendation, but when I was setting up NT4 networks prior to 2000, it was the recommendation from the company on how to setup their stuff.
NT4, yes. But it behaved differently. AD I thought started with the .local recommendation.
We have a .local here
same
-
man, after reading all this, I am pretty sure my DNS is not correct.
-
I'm just curious--what is it that we could prevent from occurring by putting DC2 first for DNS in DC1? In what scenario would we fail a lookup on ourself but succeed with a lookup? If replication is occurring they are the same. If replication is not occurring there is no guarantee that DC2 will have what you need vs. DC1.
Idk what I thought this for so long
-
@Dashrender said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@PhlipElder said in DNS Update Issue:
@JaredBusch said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
@Dashrender said in DNS Update Issue:
@wirestyle22 said in DNS Update Issue:
Simple case of me never doing this wrong I guess. What a weird thing to screw up. Didn't really have time to sift through it all.
What do you normally use for your top level domain on an AD build?
ad.domain.com theoretically. Everything I've ever touched is already in place. Although i'd love to rebuild my families infrastructure from the ground up.
If it looks like this, then it owns domain.com
Oh man, what a mess.
Meh, not bad actually. Perfect? No. But small enough to not be a problem really.
Definitely not what I would do now if I set it up new.
This is just a throw back to the new days of AD. MS suggested just this - then after a while they suggested domain.local for the internal domain, and now they recommend ad.domain.com for the internal domain.
Being a part of the SBS crew from the BackOffice 4.0 and 4.5 (NT) days, the .Local phenomena started around the discussion of Internet domain registration and keeping the internal and internet domains separate. That was prior to SBS 2003 that was the first product to deploy out of the box with .Local.
Some had to do with the confusion around registering the internet domain that was to be used internally. We used to encounter companies with Domain.Com that did not own the internet domain. It was painful to say the least.
AD was still relatively new so no one really new what to do about internal and external DNS though SBS 2003 did split the DNS for Remote.Domain.Com.
Besides wizards, which were primarily in the SBS realm, splitting the DNS became the norm and eventually the recommendation came about for Corp.Domain.Com with the caveat that the internet domain should be owned.
So, here we are. Most companies own their internet domains so it's a no-brainer to split the DNS for their setups.
-
It really doesn't matter so much. Many places .com works great, many .local works great. Some, like mine, AD is .local but we also have onprem .com and public .com. Any issues? Not a single one, ever.
For the DNS server itself, it's own FQDN first, secondary DNS server(s) next, loopback last. For DNS or DHCP, you can have CF in there too.
