none
DNS name resolution

    Question

  • Can someone help me! I am trying to find out how to take two domain names pointing to the same public ipaddress and have them resolve to two separate internal ipaddresses.

    For example: wpu.us and wpc.com is pointing to 69.12.111.777 public and private wpu.us -> 192.168.12.4, wpu.us -> 192.168.12.63

    External
    wpu.us -> 69.12.111.177
    wpu.us -> 69.12.111. 177

    Internal
    wpu.us -> 192.168.12.4
    wpu.us -> 192.168.12.63

    Sunday, July 14, 2013 5:45 AM

Answers

  • I was able to get this working by configuring an edge server and install Forefront TMG.

    • Marked as answer by cBola Thursday, July 18, 2013 5:33 PM
    Thursday, July 18, 2013 5:33 PM

All replies

  • you should create the  A Host record in the Internal Dns server to resolve 192.168.12.4 and for the external you should do it from the Domain Hosting Company. 

    http://www.arabitpro.com

    Sunday, July 14, 2013 9:46 AM
  • I have created the A record in my local DNS and still both addresses are still resolving to the 192.166.12.4. There is not a router involve, the public ipaddress is assign directly to the server which have two nic cards. 

    Sunday, July 14, 2013 12:51 PM
  • I have created the A record in my local DNS and still both addresses are still resolving to the 192.166.12.4. There is not a router involve, the public ipaddress is assign directly to the server which have two nic cards. 


    You might want to clear your cache by restarting your computer.

    Miguel Fra | Falcon IT Services, Miami, FL
    Web Site | Blog

    Sunday, July 14, 2013 3:39 PM
  • Hello,

    the ISP has to configure the external part so the public ip addresses are resolving the 2 public names.

    What is behind the router in your network, firewall with DMZ locating the servers for wpu.us and wpu.com? Are the machines webservers?


    Best regards

    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://msmvps.com/blogs/mweber/

    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

    Sunday, July 14, 2013 5:58 PM
  • I am not using a router. The public ipaddress is directly assigned to the window server running Hyper-V. The other servers are virtual servers.


    • Edited by cBola Tuesday, July 16, 2013 1:58 AM router
    Tuesday, July 16, 2013 1:58 AM
  • Yes, they are also configured as webservers.  

    Tuesday, July 16, 2013 2:04 AM
  • Hello,

    Having a Windows Server directly connected to the Internet is a really bad idea. Even with the firewall ON, Windows opens ports each time you add roles, so you have to be very careful not to expose the server.

    It appears that you want to do a split brain DNS. You want internal hosts to resolve to a local IP while external hosts resolve to public IP for the same FQDN. Is that right?

    If so, then you will need to set up an internal DNS server with a zone for wpu.us and in that zone add the A record that corresponds to your internal server. Then, make sure that the local hosts are using that DNS server to resolve.

    I noticed that you listed two private addresses for the internal server. You cannot point to two IP's simultaneously. If you want to load balance then you should set up round robin DNS to distribute incoming http request between your two IIS servers.

    For more information, script your topology and exactly what it is that you want to accomplish.


    Miguel Fra | Falcon IT Services, Miami, FL
    Web Site | Blog



    Tuesday, July 16, 2013 4:59 AM
  • I have created the A record in my local DNS and still both addresses are still resolving to the 192.166.12.4. There is not a router involve, the public ipaddress is assign directly to the server which have two nic cards. 

    What do you mean by 'both addresses are resolving to 192.168.12.4'. Do you mean that both external and internal hosts resolve to that IP or do you want the same domain name to alternatively resolve between two IP?

    If the latter, then are you trying to load balance?


    Miguel Fra | Falcon IT Services, Miami, FL
    Web Site | Blog

    Tuesday, July 16, 2013 5:09 AM
  • It is two domain names wpu.com and wpu.us.

    I would like wpu.com to resolve to 192.166.12.4  from 69.12.111.777

    and wpu.us to resolve to 192.168.12.63 from 69.12.111.777


    • Edited by DRManning Tuesday, July 16, 2013 5:22 AM add names
    Tuesday, July 16, 2013 5:21 AM
  • It is two domain names wpu.com and wpu.us.

    I would like wpu.com to resolve to 192.166.12.4  from 69.12.111.777

    and wpu.us to resolve to 192.168.12.63 from 69.12.111.777

    Tuesday, July 16, 2013 5:34 AM
  • It is two domain names wpu.com and wpu.us.

    I would like wpu.com to resolve to 192.166.12.4  from 69.12.111.777

    and wpu.us to resolve to 192.168.12.63 from 69.12.111.777

    Hello,

    without any port forwarding behind the ip address there will be no way that i know to split the traffic. Especially Hyper-V is NOT a product made for the routing and firewall options.

    Network access is controlled with router and firewall NOT with a server directly connected to a public port.

    The network setup should look like this:

    Internet > routerWANport > routerLANport > switch > internal network with all servers/clients in PRIVATE ip range


    Best regards

    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://msmvps.com/blogs/mweber/

    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

    Tuesday, July 16, 2013 7:55 AM
  • It is two domain names wpu.com and wpu.us.

    I would like wpu.com to resolve to 192.166.12.4  from 69.12.111.777

    and wpu.us to resolve to 192.168.12.63 from 69.12.111.777


    Hello,

    DNS does not forward, it only resolves. Again, you need to tell us what you are trying to accomplish because I have no idea what you want to do.

    If you want DNS to resolve wpu.com to 192.168.12.4 then you need to create an A record in the zone that's authorative for that domain name. If the zone is in a public DNS server, keep in mind that private IP are not routable across the public Internet so nobody outside of your LAN will be able to access.

    You can opt for split brain DNS where you have a private and public zone and have each resolve accordingly. Internal hosts should use the private DNS server that will resolve to the local IP and the public computers will use the public IP that resolve to the public IP addresses.

    If you are hosting and you want your IIS site available to the public, then, as Meinolf pointed out, you need to use port forwarding. Port forwarding requires a router with NAT/PAT.

    You can use Windows RRAS but as pointed out already, the best option is a hardware router. Your DNS will resolve to the public IP address 69.12.111.177 and then get forwarded to the private IP address.

    Also, you will not be able to use port 80 and forward the same public IP and port to both private IP's. You will need to run both sites on one IIS server and then use bindings to separate the traffic from both sites into their respective IIS sites.

    Again, please post a detail of what you are trying to accomplish so that we are not spinning our wheels.


    Miguel Fra | Falcon IT Services, Miami, FL
    Web Site | Blog


    Tuesday, July 16, 2013 3:53 PM
  • I was able to get this working by configuring an edge server and install Forefront TMG.

    • Marked as answer by cBola Thursday, July 18, 2013 5:33 PM
    Thursday, July 18, 2013 5:33 PM