Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
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,
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,
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
When you access the site from an external network, does the URL in the browser bar change from www.domain.com to domain.com? If so, there's a redirect on the site that's doing this, and it will interfere with access from inside your office until it is removed. Removing that redirect from the site is the only fix unless you want to change your internal domain name to something that doesn't match your external domain name.
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.
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.
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?
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.
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/loc
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.
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/loc
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.
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.
Machienet,
In your example are you assuming that the web site id hosted locally? The site is hosted externally.
In your example are you assuming that the web site id hosted locally? The site is hosted externally.
@Phy2015:
My apologies, I must have missed that.
So, log into your ISP's control panel for your account and add another record that points to the same IP, but make it for domain.com . This way you will have two records, each one pointing to each of the variations.
Someone types in www.domain.com and it will resolve.
Someone types in domain.com and it will still resolve.
I needed to do that for one of my externally hosted web servers in the past for the same issue.
My apologies, I must have missed that.
So, log into your ISP's control panel for your account and add another record that points to the same IP, but make it for domain.com . This way you will have two records, each one pointing to each of the variations.
Someone types in www.domain.com and it will resolve.
Someone types in domain.com and it will still resolve.
I needed to do that for one of my externally hosted web servers in the past for the same issue.
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.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial