resolve external website when internal same...

[karmic]

K, I used to know the fix for this but can't for the life of me remember.

Have a server that has internal DNS .com name the same as their website that's hosted externally. When users hit the

http://www.mycompanywebsite.com

it doesn't come up, just get dns error.

I've added a new alias record to the dns server but still not working...

How do I tell the server to point

http://www.mycompanywebsite.com

instead of the internal dns server again?

Thanks.

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[karmic]

k, nevermind... its the add host.

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[JordanR]

Karmic,
I was looking for answers to the question you orginally asked and I guess you figured it out.
Could you share with me the solution?

Thanks,
Jordan

 

[karmic]

sure... trying this off the top of my head.

go into the DNS snap-in, expand the forward lookup zone, expand the DNS name... right click on the dns name, and add host. fill in

http://www in

the alias name and the IP address of your website below it.

Restart the DNS server.

Theres information from microsoft here:

http://www.microsoft.com/technet/tr...03/proddocs/entserver/sag_DNS_pro_AddHost.asp

Good luck

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[JordanR]

karmic,
Thanks for the infor, but it seems that I have done this before and it isn't working as I had expected.

Is there something that I must do with the the DNS addresses on the Domain controller, ie. have the Primary DNS address on the Domain controller point to the ISP address instead of pointing to itself?

Your help is greatly appreciated.

Jordan

 

[karmic]

ok, few questions here...

Are you hosting your own site locally or is it held in a third party? If your site is external, can you hit it from the server? If not, try statically assigning the ISP DNS servers in the servers network connections and try the site again.

What is your dns domain name? is it mycompany.com? is it the same as your website?

If you are in the same situation as my client was, simply adding a host to the dns should work. You may have to reload the dns records (right click the dns domain name, click reload) and restart the dns server.

Let me know your exact situation. I'm assuming all your clients have internet?



~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[JordanR]

"Are you hosting your own site locally or is it held in a third party?"
ans. the site is currently hosted at a 3rd party.

"If your site is external, can you hit it from the server?"
ans. no, I am not able to hit from the server.
Prmary DNS on server points to itself, Secondary DNS points to ISP DNS address

"If not, try statically assigning the ISP DNS servers in the servers network connections and try the site again."

my ques. Should I add the ISP DNS addresses in the Addvanced section along with the website's IP addresses?

"What is your dns domain name? is it mycompany.com? is it the same as your website?"
ans.yes, dns domain name is the same as the website.

"If you are in the same situation as my client was, simply adding a host to the dns should work."
ans. I had added

http://www pointing

to external dns address. But I didn't reload or restart the dns server.

You may have to reload the dns records (right click the dns domain name, click reload) and restart the dns server.

"Let me know your exact situation. I'm assuming all your clients have internet?"
ans. my clients do have interet access. their primary dns points to domain controller and secondary dns points to ISP.

Thanks for your help.

 

[karmic]

Take out the local server IP from the dns server list and input the ISP DNS servers, if you can hit the site from the server at this point then the new host should work.

Try reloading the dns records and restart the DNS server, that's what it took for the clients to see the website from the internal network...

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[JordanR]

If I take out the local server IP from the dns server list would that cause a problem with the dns server?

What I mean is that when I installed DNS, active directory to make the server a domain controller, it gave me errors because it could not locate the dns server that was hosting the domain name xyz.com so I pointed the dns address to itself and my problem was resolved.

So, I am wondering, if I change the addresses to both primary and secondary pointing to external DNS will cause a problem with AD, DNS, etc.

Jordan

 

[karmic]

using the ISP DNS addresses in TCP/IP does not normally cause problems with the DNS. The two are separate entities.
Just use the ISPs DNS servers as a trial and put it back.

BTW, are you using 127.0.0.1 for the dns on the server or an actual network IP? Generally, use the network IP of the dns server (in this case its normally your PDC)

Good luck

~ K.I.S.S - Don't make it any more complex than it has to be ~

 

[JordanR]

I will try using the ISP's DNS and if it causes problems I will change it back.
I am using the network IP on the PDC and not the 127.0.0.1.

Thanks
I will let you know how it turns out.

Jordan