Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 700
  • Last Modified:

Unable to access company websites internally after adding an alternative UPN suffix to Active Directory

Hello Experts,

As part of the steps to migrate onto Office 365, I added our external domain name as an alternative UPN suffix within Active Directory and after doing so, we are no longer able to access our company websites internally.

I suspect that adding the UPN suffix has created an DNS issue internally and I am unclear how to resolve it, any information would be greatly appreciated.

Below is our network configuration;

Internal Domain
cadcasbs.local

External Domain
cadca.org

External Websites trying to access internally
www.cadca.org
drugfreekids.cadca.org
forum.cadca.org
cadcadnsconfiguration.PNG
0
Darrell James
Asked:
Darrell James
1 Solution
 
Mike ThomasConsultantCommented:
adding the upn should not matter whatsoever.

with the absence of the cadca.org locally in you dns all lookups will user forwarders or root hints to query external dns, what happens when u do an nslookup? does this external resolution take place?
0
 
Darrell JamesDirector of Information TechnologyAuthor Commented:
Thanks for the help, all of a sudden, it started working again, so I think something else was going on.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now