Lync 2013, internal and external domain name the same..

[irBosOtter]

Hi guys and gals,

I was wondering if it's possible to setup Lync 2013 on a domain where the domain name is the same, internal and external ie mydomain.co.za

Not sure who the idiot was that setup the internal domain like that, but that's the situation and I am not finding to much info on the net regarding a Lync setup with internal and external domain name the same...

Anyone done it?

 

[grim]

Hi guys and gals,

I was wondering if it's possible to setup Lync 2013 on a domain where the domain name is the same, internal and external ie mydomain.co.za

Not sure who the idiot was that setup the internal domain like that, but that's the situation and I am not finding to much info on the net regarding a Lync setup with internal and external domain name the same...

Anyone done it?

It wasn't some idiot that set it up like that, he should've preferably used something like ad.mydomain.co.za but nothing wrong with having just mydomain.co.za internally.

Lync will work perfectly fine, it'll probably make your life easier with having the same domain name, just make sure you add the relevant DNS records pointing internally on your internal DNS servers.

We normally setup domains as (label).domain.co.za and then add a UPN suffix for domain.co.za so that the users can use their email addresses as their usernames instead of domain\username or username@(label).domain.co.za

Also domain.local should never be used in a production environment, people that setup domains like that are idiots.

 

[irBosOtter]

It wasn't some idiot that set it up like that, he should've preferably used something like ad.mydomain.co.za but nothing wrong with having just mydomain.co.za internally.

Lync will work perfectly fine, it'll probably make your life easier with having the same domain name, just make sure you add the relevant DNS records pointing internally on your internal DNS servers.

We normally setup domains as (label).domain.co.za and then add a UPN suffix for domain.co.za so that the users can use their email addresses as their usernames instead of domain\username or username@(label).domain.co.za

Also domain.local should never be used in a production environment, people that setup domains like that are idiots.

Thanks, but believe me, there was an idiot here at one point. Even the whole internal IP range was a public range (196 range, and all of them are live IP's on the internet). So yes, one big idiot was here.

I know the best way to do it is to create a sub domain of your domain that you have, but alas, that's not the case here.

I just cannot find any documentation that says you can use the same internal as external, will see what happens when we set it up

 

[grim]

Thanks, but believe me, there was an idiot here at one point. Even the whole internal IP range was a public range (196 range, and all of them are live IP's on the internet). So yes, one big idiot was here.

I know the best way to do it is to create a sub domain of your domain that you have, but alas, that's not the case here.

I just cannot find any documentation that says you can use the same internal as external, will see what happens when we set it up

It'll work fine, I have setup Lync on environments like that before.