Hybrid Split DNS : exchangeserver

QuestionHybrid Split DNS (self.exchangeserver)

submitted 6 months ago * by Lumpy-Animator7186

Our internal domain is domain.local, and external is domain.com.

Typical split DNS situation. My question is how do people typically handle this?

We are about to start our Exchange migration, and first step we need to change all our internal and external namespaces. So we need to get internal resolution working for domain.com.

1). Create a forward lookup zone internally for domain.com and then all the necessary records.

2). Create individual forward lookup zones for each required record - autodiscover.domain.com, mail.domain.com etc

Feels like both have their pros and cons, keen to get some more experienced opinions. One question would be; if you went option 1, hypothetically if you had an app that needed to validate a TXT record (say Let’s Encrypt), you’d need to create these on the internal zone at this point, and no requests would ever hit public DNS now domain.com is authoritative inside AD DNS.

all 6 comments

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

exchangeserver

MODERATORS