Avatar of Phy2015
Phy2015
Flag for United States of America asked on

After Changing DNS IP at GoDaddy.com for website, inner office users cannot access external website with same domain name.

We had a website in a development mode and were able to access it from the office using the IP address and www.domain.com.

I have in the local DNS an A record for www pointing to the site IP which allowed access during development.    

After making the site live, removing a forwarder at GoDaddy.com and changing the A (Host) record (@) to the site IP we are not able to access the site from the office.

The site is still accessible from external networks using the www.domain.com and the IP address.

I can ping both the IP & the www.domain.com from the office.
Using tracert for the IP gets out for 16 hops.
Using tracert for the www.domain.com only returns 1 entry which is our DNS server.

Thanks,
DNSHTML

Avatar of undefined
Last Comment
Phy2015

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
DrDave242

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
Phy2015

ASKER
DrDave,
Thanks for the response.
Are you saying that this forwarder is set in the site itself, in PrestaShop on the hosting server?   There is no forwarder at GoDaddy where the domain name is registered and the A records set.
Phy2015

ASKER
DrDave,
Sorry, to answer your question externally www.domain.com is converting to domain.com?
Jan Bacher

Are you using this doman name internally within your network?  What error do you receive when you query the site?  Can you post the domain name?
Your help has saved me hundreds of hours of internet surfing.
fblack61
Phy2015

ASKER
The local domain is the same name as the web site domain.
DrDave242

Are you saying that this forwarder is set in the site itself, in PrestaShop on the hosting server?
Yep, if the URL is changing, the redirect is on the site itself. Whoever manages the site will be the one that needs to remove the redirect.
Jan Bacher

Do you have an internal DNS server?  Can you add the www A record pointing to the external IP?
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
Michael Machie

On your DNS server you will need a couple entries.

In Forward Lookup Zones
- You will most likely have a Zone for your internal domain. in this zone create a Host(A) record that has the server name pointing to the internal IP address of your web server.
Name: webservername | Type: Host(A) | IP: xxx.xxx.xxx.xxx  [Internal IP of server].

- You will also most likely have another zone for your 'domain.com' web servers. You will need to create a Host (A)  record for the internal server name that points to your internal IP address.
Name: webserver internal name [webserver1.domain.com/local] | IP: [internal IP address]

As an example:
My lab domain is 'internal_domain.local', so I have a Forward Lookup Zone called 'internal_domain.local' .Within this zone I have a HOST(A) record that states:
'webserver1' [internal server name] pointing to IP address: xxx.xxx.xxx.xxx [Internal IP].

I also have another Forward Lookup Zone called 'public_web_domain.net' [use your own Public Domain name here]. Inside this zone I have another HOST(A) record stating the INTERNAL server name (not public DNS name), that points to my INTERNAL IP of the Server.

With this setup you will be able to use the Public DNS name [webserver1.domain.com] in your intranet machines to connect to your web server internally, using the public DNS name.    

I hope this is clear. If not please ask questions.
DrDave242

Do you have an internal DNS server?  Can you add the www A record pointing to the external IP?
It appears that he's already done this:

I have in the local DNS an A record for www pointing to the site IP which allowed access during development.
The problem seems to be that the site is redirecting www.domain.com to domain.com. Queries for that name from inside his office will resolve to the IP of a domain controller, as they're supposed to.
Phy2015

ASKER
Machienet,

In your example are you assuming that the web site id hosted locally?  The site is hosted externally.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23
SOLUTION
Michael Machie

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
DrDave242

Machienet: I'm pretty sure that's already been done too:

After making the site live, removing a forwarder at GoDaddy.com and changing the A (Host) record (@) to the site IP we are not able to access the site from the office.
The @ record is the domain.com record. The site wouldn't be accessible externally without that record.
Phy2015

ASKER
By modifying the store URL in PredtaShop from domain.com to www.domain.com corrected the issue.

However DrDave & Machienet suggestions/solutions let us to discovering this fix.

Thanks for your help!