Isolating dns resolution issue (same as parent folder)
Problem: Users can no longer access www.company.com from within the internal network. Everything is fine when accessing the website externally.
Situation: Prior to this weekend, resolving www.company.com from the internal network worked just fine because I have an A record pointing to the old public IP for www. Our external dns host just changed the ip of our www.company.com site, so I modified the internal A record for www to the new public IP.
Observation: When the website loads (when accessed internally or externally) it strips the www prefix from the url and finishes loading the page as http://company.com instead of Company.com
Diagnosis: When internal, the reason that the page does not load is because there is no A record for (same as parent folder) with the new public IP of the website. The only (same as parent folder) records are the SOA, NS, and A records of the internal domain controllers which is expected because of AD.
Resolution: Not sure.
A) Ask web host why the site is stripping the www prefix?
Create a (same as parent folder) A record with the new public IP of the website?
C) Alternate dns solution?
Thoughts? Suggestions?
Situation: Prior to this weekend, resolving www.company.com from the internal network worked just fine because I have an A record pointing to the old public IP for www. Our external dns host just changed the ip of our www.company.com site, so I modified the internal A record for www to the new public IP.
Observation: When the website loads (when accessed internally or externally) it strips the www prefix from the url and finishes loading the page as http://company.com instead of Company.com
Diagnosis: When internal, the reason that the page does not load is because there is no A record for (same as parent folder) with the new public IP of the website. The only (same as parent folder) records are the SOA, NS, and A records of the internal domain controllers which is expected because of AD.
Resolution: Not sure.
A) Ask web host why the site is stripping the www prefix?
Create a (same as parent folder) A record with the new public IP of the website?C) Alternate dns solution?
Thoughts? Suggestions?
Comments
-
blargoe
Member Posts: 4,174 ■■■■■■■■■□
The only correct answer is to ask the hosting company, the developer, or whoever made the change to redirect to company.com to not redirect Company.com. You don't want to add the public ip of company.com to your ad-integrated DNS.IT guy since 12/00
Recent: 11/2019 - RHCSA (RHEL 7); 2/2019 - Updated VCP to 6.5 (just a few days before VMware discontinued the re-cert policy...)
Working on: RHCE/Ansible
Future: Probably continued Red Hat Immersion, Possibly VCAP Design, or maybe a completely different path. Depends on job demands... -
KenC
Member Posts: 131
You don't want to add the public ip of company.com to your ad-integrated DNS.
Can you elaborate on this please.
Should the internal DNS server(s) not have a conditional forwarder set for www.company.com until DNS has propogated? -
undomiel
Member Posts: 2,818
Can you elaborate on this please.
Should the internal DNS server(s) not have a conditional forwarder set for Company.com until DNS has propogated?
If I'm reading the OP correctly, the problem isn't with the Company.com, the problem is that their internal AD domain is company.com which is the same domain as the external domain. So the A records that are pointing to company.com are only resolving to the records of the domain controllers, which is as it should be.
The best solution would be as blargoe said, to get in contact with the developers to stop the redirect. Any other solutions are going to get pretty hackish.Jumping on the IT blogging band wagon -- http://www.jefferyland.com/ -
KenC
Member Posts: 131
If I'm reading the OP correctly, the problem isn't with the Company.com, the problem is that their internal AD domain is company.com which is the same domain as the external domain.
Ok, thanks for that, thought internal was something like company.local