external DNS records for two servers

Discussion in 'DNS Server' started by Loane Sharp, Feb 17, 2006.

  1. Loane Sharp

    Loane Sharp Guest

    Hi there

    We have a small network (two servers) running Windows Server 2003. The two
    servers are connected to a broadband modem / WLAN router / firewall (single
    hardware unit) for client access to network resources and the Internet.

    When I am off-site I connect to one of the servers (the domain controller)
    using Remote Desktop Connection by typing in the external domain name
    server1.mydomain.com. This domain name resolves to the external IP address
    of the router, and the router in turn passes all incoming traffic to this
    server (the domain controller).

    The problem is ... To connect to the other server, I set up a VPN connection
    and use Remote Desktop to connect to the internal IP address
    .... because I can't figure out how to setup the DNS records so that a
    subdomain (say server2.mydomain.com) will connect directly to the second

    I tried creating a forward lookup zone for the second server
    (server2.mydomain.com) and added an A record to this zone (pointing to, but when I try to connect to this domain name
    server2.mydomain.com using Remote Desktop, I get to the first server

    Please can you help.

    Best regards
    Loane Sharp, Feb 17, 2006
    1. Advertisements

  2. Loane Sharp

    Herb Martin Guest

    I don't know what "a subdomain ... will connect" means but why not
    use Remote Desktop to leap from from one server to the other? Get
    connected to #1 and run another Remote Desktop from there to the

    Otherwise the VPN idea works: connect to your network and then
    all servers should be ready as long as your DNS is working there
    but if it isn't then install the Remote Desktop Web connection and
    use that to connect (it can use the local servers name resolution
    to find the servers.)

    After all that you might even consider setting up a router-firewall
    map from another port (not 3389) to the #2-server on 3389; then
    you client must specify a different port when you connect through
    the firewall (e.g.,, 3390).

    External-3390 mapped to internal-3389 on #2 server address.
    Herb Martin, Feb 18, 2006
    1. Advertisements

  3. Loane Sharp

    Loane Sharp Guest

    Hi Herb
    Thanks for the ideas. I was hoping for a DNS-related solution, to push my
    understanding in this area, but your methods will work perfectly.
    Best regards
    Loane Sharp, Feb 18, 2006
  4. Loane Sharp

    Herb Martin Guest

    To advance you DNS knowledge remember this:

    DNS (A-records) ONLY resolve names to IP addresses.

    So anything that must distinguish services from each other
    or map one address to another must be done in additional
    to (and outside of) DNS.

    Port mapping, referral pages (for HTTP), address mapping,
    Herb Martin, Feb 19, 2006
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.