FQDN config to internal server

hello,
I want to use my newly purchased FQDN "mywebsite.com" to point to my internal server. I have a sonicwall 2400, server 2008 and FQDN GoDaddy. I have tried using youtube, research google, shows hundreds of advanced to basic practices to create this "Forward". any suggestions on how to get this going? I have spoke with two network certified admins and they said its as simple as opening a port for remote access to an internal pc. Ok, good, but I use a FQDN for that aswell :( I can get around firewall config (basic config), DNS Config (basic config). any tips or references would greatly be appreciated. thanks...
GrizNation23IT DirectorAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Paul MacDonaldDirector, Information SystemsCommented:
You want to access an internal server from outside your network?  If so, you'll need to NAT the port of the service in question so connections to the outside of your firewall are passed through to the server in question.  Since you're using a SonicWall device, the instructions should be in that user manual.
0
BembiCEOCommented:
And..., just not to forget this..
You bought the domain from provider. So the provider is responsible what happens if somebody uses the domain. Currently if somebody uses the name, the request reaches your provider.
Your provider has to forward this request to your own external IP.
Most of the providers have a web tool, where you can change the default setting (a target on the provider server) to point to your own IP address. You can usually reroute the domain itself  (as wildcard) as any subdomain like www.mywebsite.com

And if the request then hits your Firewall, the you need a NAT rule in the firewall, which forwards the external request (i.e.www.mywebsite.com) on a dedicated port (i.e port 80 for http) to your internal webserver (ie myweb.mydomin.intern) on a dedicated port (i.e. port 80 for http).
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
GrizNation23IT DirectorAuthor Commented:
perfect, I actually walked through this with firewall wizard! your answer is right on. thank you,
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.