How to resolve selected internal domain name to an external DNS
We have an outside vendor hosting our website www.YYY.com.
Our internal network has the same network name YYY.com.
We setup an A record in our internal DNS server to resolve www.YYY.com to the outside IP address.
The problem is that the vendor hosting our site changes the IP address frequently and we would have to keep on changing our internal A record to resolve the correct IP address. We are tied with a contract to the hosting site (inherent issue).
How can we selectively resolve just the www.YYY.com to the external DNS server so the correct IP address is resolved correctly everytime the hosting company changes the IP address without needing manual intervention?
Our internal DNS server is a Windows 2003 Server that has DNS forwarding enabled.
Thank You.
Our internal network has the same network name YYY.com.
We setup an A record in our internal DNS server to resolve www.YYY.com to the outside IP address.
The problem is that the vendor hosting our site changes the IP address frequently and we would have to keep on changing our internal A record to resolve the correct IP address. We are tied with a contract to the hosting site (inherent issue).
How can we selectively resolve just the www.YYY.com to the external DNS server so the correct IP address is resolved correctly everytime the hosting company changes the IP address without needing manual intervention?
Our internal DNS server is a Windows 2003 Server that has DNS forwarding enabled.
Thank You.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
andrewc2189
Out of curiosity, where do internal clients resolve www.YYY.com to without the A record? Do requests not get forwarded to the external DNS server without the A record? As you said, the inherent issue is that it's not a static IP. I have heard of people with setups that somehow update their records to reflect changes in dynamic addresses using home servers, I'll try to find more info on that.
sorrillo makes more sense to me on this one, I would say to take that route over the ways people run websites out of their home! Cheers.
Is that the only domain name that goes to your Website??
If you had another DNS name that pointed to your website i.e. www.YYY.co.uk then you could set the alias up for www to point to that.
You have been tripped up by using the external domain name as you internal rather that yyy.local.
Regards
If you had another DNS name that pointed to your website i.e. www.YYY.co.uk then you could set the alias up for www to point to that.
You have been tripped up by using the external domain name as you internal rather that yyy.local.
Regards
ASKER
Thank you for your replies.
Sorillo -
Sorillo -
- deleted the A record (www) in my zone YYY.com
- created a new zone - www.YYY.com and setup the appropriate Name server that is resolving this url.
- flushed the DNS cache for all the internal DNS servers
- nslookup for www.YYY.com results to only the www.YYY.com and no ip address
- ping www.YYY.com only gives me an error that cannot find host www.YYY.com
nslookup for www.YYY.com results to only the www.YYY.com and no ip address
I don't understand what you mean. Could you post the nslookup result ? (masking domain name if you want).
You should also flush the local dns cache using ipconfig /flushdns before the ping test.
I don't understand what you mean. Could you post the nslookup result ? (masking domain name if you want).
You should also flush the local dns cache using ipconfig /flushdns before the ping test.
ASKER
i flushed the dns cache on the DNS servers and local PC that i'm using.
i attached a screen shot of the nslookup that shows no IP address resolved and ping result
nslookup.JPG
i attached a screen shot of the nslookup that shows no IP address resolved and ping result
nslookup.JPG
Sorillo:
I had a similar situation sometime ago when my hosting company's DNS servers were unreliable for a period of 3 months.
I forwarded my queries to XO Communicaionns and Cogent DNS servers. Also, I set my DNS cache for quick expiration. It did overwork my DNS servers, but worked like a charm for the short period that I needed it to work.
I had a similar situation sometime ago when my hosting company's DNS servers were unreliable for a period of 3 months.
I forwarded my queries to XO Communicaionns and Cogent DNS servers. Also, I set my DNS cache for quick expiration. It did overwork my DNS servers, but worked like a charm for the short period that I needed it to work.
ASKER
You never will get this to resolve as you are asking because your internal domain name is the same as your external name. The only way to do it is point the alias of www to a different external domain name so your internal users can view the webpage.
If your IP was static then you could put this in DNS but as you have stated your ISP keeps changing this so it wont last long. You want to eliminate the need for you to change the IP address.
I don't believe you can achieve this using internal methods to resolution your are seeking.
If your IP was static then you could put this in DNS but as you have stated your ISP keeps changing this so it wont last long. You want to eliminate the need for you to change the IP address.
I don't believe you can achieve this using internal methods to resolution your are seeking.
I think andrewc2189 already asked this but maybe in a different way:
If you remove www.yyy.com from your DNS completely, what happens? I think the DNS by default should look up the external IP address from "the Internet at large" once it does not find it locally. The yyy.com address you have setup should still resolve to the internal address but the www.yyy.com should resolve to the external address I believe unless you run into issues with yyy.com interfering with your ability to resolve www.yyy.com externally.
If you remove www.yyy.com from your DNS completely, what happens? I think the DNS by default should look up the external IP address from "the Internet at large" once it does not find it locally. The yyy.com address you have setup should still resolve to the internal address but the www.yyy.com should resolve to the external address I believe unless you run into issues with yyy.com interfering with your ability to resolve www.yyy.com externally.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
no viable solution
Scrap your internal domain and set it up correctly. Lots of work though dependent on your architecture.
ASKER
i almost died laughing..
thanks for making my friday !!!
thanks for making my friday !!!
I might be able to explain why my solution did not work on your case. I must admit I never used myself, it was just theoretical.
Anyways, I tested some domains to see what happened.
Using experts-exchange.com as a testing domain did not work as expected. I believe this is what went wrong:
https://www.experts-exchange.com canonical name = experts-exchange.com
https://www.experts-exchange.com points to the domain itself which will not have the correct resolution as it can not be delegated.
Using sun.com as a testing domain did work as expected. That's why:
Name: www.sun.com
Address: 72.5.124.61
www.sun.com does not point anywhere else, it just returns the IP.
Your case might be like https://www.experts-exchange.com, you can confirm it with nslookup ans see if it just resolves to an ip or to the domain without the www.
Anyways, this solution did not solve your problem so this comment is not an objection, just a clarification.
Greetings.
Anyways, I tested some domains to see what happened.
Using experts-exchange.com as a testing domain did not work as expected. I believe this is what went wrong:
https://www.experts-exchange.com canonical name = experts-exchange.com
https://www.experts-exchange.com points to the domain itself which will not have the correct resolution as it can not be delegated.
Using sun.com as a testing domain did work as expected. That's why:
Name: www.sun.com
Address: 72.5.124.61
www.sun.com does not point anywhere else, it just returns the IP.
Your case might be like https://www.experts-exchange.com, you can confirm it with nslookup ans see if it just resolves to an ip or to the domain without the www.
Anyways, this solution did not solve your problem so this comment is not an objection, just a clarification.
Greetings.