Point an FQDN to public ip Address

Home Forums Server Operating Systems Windows Server 2000 / 2003 / 2003 R2 Point an FQDN to public ip Address

This topic contains 9 replies, has 5 voices, and was last updated by  mirfanaslam 9 years, 12 months ago.

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts

  • mirfanaslam
    Member
    #137037

    i have dynamic ip address on router but mostly it same all time untill i restart router.

    On Lan i configure my Domain e.g(businessserver.local)

    how i point FQDN work.businessserver.local to public ip addres on my router.

    Basicaly how i point lan fqdn to public ip

    thanks


    stamandster
    Member
    #280218

    Re: Point an FQDN to public ip Address

    You want your WAN IP to route to a certain LAN IP on your network and to be accessible from the outside world?


    mirfanaslam
    Member
    #347692

    Re: Point an FQDN to public ip Address

    stamandster;134371 wrote:
    You want your WAN IP to route to a certain LAN IP on your network and to be accessible from the outside world?

    YES i WANT to do


    stamandster
    Member
    #280221

    Re: Point an FQDN to public ip Address

    lol… Only for a certain server I would imagine. Like HTTP/HTTPS/FTP right?


    Nonapeptide
    Member
    #316246

    Re: Point an FQDN to public ip Address

    mirfanaslam;134363 wrote:
    i have dynamic ip address on router but mostly it same all time untill i restart router.

    On Lan i configure my Domain e.g(businessserver.local)

    how i point FQDN work.businessserver.local to public ip addres on my router.

    Basicaly how i point lan fqdn to public ip

    thanks

    Let me see if I understand you. You want people to be able to go to your public IP address (the router’s public IP) and access certain services on your business’s server which is on the LAN? Simple port forwarding in your router would solve that or even using a DMZ feature if the router supports it. What router do you have?

    (Also, your router might have built-in support for DynDNS which will point a FQDN to your public IP even if it changes. Of course, static IP addresses are fairly cheap these days too [no wonder we’re runnig out of IPV4 address space].)


    joeqwerty
    Moderator
    #301039

    Re: Point an FQDN to public ip Address

    First you’ll need a valid public domain name as .local is not a valid gTLD. Then create the appropriate FQDN that points to the public ip assigned to you by your ISP, then create the appropriate port forwarding rules on your firewall/router to route traffic to the internal ip address, then set up a DynDNS account and client to update the FQDN when the public ip address changes.


    stamandster
    Member
    #280222

    Re: Point an FQDN to public ip Address

    He doesn’t have to make his internal FQDN the same as his external one. It seems that he simply wants his public IP to be able to connect to internal services.

    But, port forwarding could be the option to use. Make sure you only allow the ports you actually need open to only the IP addresses you are going to use these services on. The smaller the allowed hole the better off you will be.

    You could also setup your server in a DMZ zone. But then that get’s into more complication.

    However, if you’re going to do anything like RDP, etc. I would suggest using a VPN connection instead of something just wide open.


    Nonapeptide
    Member
    #316248

    Re: Point an FQDN to public ip Address

    joeqwerty;134415 wrote:
    First you’ll need a valid public domain name as .local is not a valid gTLD.

    I suppose it’s a matter of interpretation here. :mrgreen: I was interpreting the OP’s somewhat broken english (I’m not making fun of you mirfanaslam, you’re good) to mean that he wants his external IP to forward to work.businessserver.local on his LAN. Or maybe I misinterpreted and mirfanaslam wanted what you mentioned; to have the DNS name work.businessserver.local publically resolvable.

    mirfanaslam;134363 wrote:
    how i point FQDN work.businessserver.local to public ip addres on my router.

    Basicaly how i point lan fqdn to public ip

    We’ll have to wait until mirfanaslam responds.


    mohanmathew
    Member
    #311120

    Re: Point an FQDN to public ip Address

    joeqwerty;134415 wrote:
    First you’ll need a valid public domain name as .local is not a valid gTLD. Then create the appropriate FQDN that points to the public ip assigned to you by your ISP, then create the appropriate port forwarding rules on your firewall/router to route traffic to the internal ip address, then set up a DynDNS account and client to update the FQDN when the public ip address changes.

    Since he want to access the lan from WAN, he needs to get a valid domain name which points to his lan public IP and the definitely port forwarding will do the trick. Also if the lan is on dynamic IP, DynDNS is the way.


    stamandster
    Member
    #280228

    Re: Point an FQDN to public ip Address

    A public facing FQDN is only a facade for an IP address. He doesn’t “need” an FQDN to access his internal network. It’ll only be good if he wants to do it publicly.

Viewing 10 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic.