[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

Can not access our domain website internally but it works externally,

Hello,

We recently put an exchange server in place and transferred our DNS Zone from Enom to Godaddy. The website works externally as we pointed the A record and CNAME www to company.com but not internally. The MX record is different from the website record. Is there a DNS entry we need on our internal DNSsince we used split DNS for the email? The domains are company.local and company.com I can not ping www.company.com internally but works externally fine. Any help would be much appreciated.
0
JRome225
Asked:
JRome225
  • 3
  • 3
1 Solution
 
DrDave242Commented:
Is there a DNS entry we need on our internal DNSsince we used split DNS for the email?
Can you describe your split DNS setup? Do you have a company.com zone on your internal DNS servers?
0
 
Simon Butler (Sembee)ConsultantCommented:
Almost certainly you have setup a split DNS for the entire zone.
The easiest solution to this is to change the split DNS to specific host instead.

http://semb.ee/splitdns

That way it only works for the hosts that you specify. If you then change the web host for any reason, you don't have to another record to change (or forget about).

Simon.
0
 
JRome225Author Commented:
The website is hosted externally. Is there simply an internal dns record I can add?
0
Cyber Threats to Small Businesses (Part 2)

The evolving cybersecurity landscape presents SMBs with a host of new threats to their clients, their data, and their bottom line. In part 2 of this blog series, learn three quick processes Webroot’s CISO, Gary Hayslip, recommends to help small businesses beat modern threats.

 
JRome225Author Commented:
Dave- Yes there is a company.com and company.local under the forward lookup zones. With SOA srvr.cmpny.local, hostmaster.cmpny.local and cname mail = srvr.cmpny.local and owa = srvr.cmpny.local under the Company.com lookup zone.

The other administrator modified the host file on the server to point externally and it works on the server. Would this be a solution for each client computer?
0
 
DrDave242Commented:
Rather than modifying host files, you can simply create a host record named www in the company.com zone and give it the address of the website. However, you may not need that zone at all, unless you've got machines in the company.com domain whose names need to be resolved to different IP addresses by internal and external users.

Are there any other records in the company.com zone? You don't have to give details, especially the IP addresses associated with those records; I'm just wondering whether that zone really needs to be there at all.
0
 
JRome225Author Commented:
Well I added the www A record under company.com pointing to external IP per the blog instructions. Hopefully it works, I'll post results this evening.
0
 
DrDave242Commented:
OK cool. Don't forget that you may need to flush the resolver cache (via ipconfig /flushdns) on a machine before it will resolve the new record properly.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

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