assign external FQDN DNS name to internal SBS IP for internal use

Discussion in 'Windows Small Business Server' started by Nick, Nov 16, 2004.

  1. Nick

    Nick Guest

    Hi All,

    Sorry for the poor subject description but I wondered if anybody could help
    me with a DNS query.

    We want to allow our pocket pc/smartphone devices to connect/activesync to
    our sbs exchange server; this will work fine from outside the LAN because
    they can resolve the FQDN to the external IP of our SBS box e.g.
    mail.domainname.co.uk

    However, when they're connected to internal PCs and have internet access via
    them from inside the LAN, this attempt to resolve/lookup won't work because
    the DNS request gets forwarded to the outside ISP DNS that then points it
    back to the external SBS IP.

    Is it possible to add a record the internal SBS DNS to return the internal
    IP of the SBS box when an internal client requests a resolve of
    mail.domainname.co.uk?

    Is there any other reason why this would not be a good idea? Is there an
    alterative?

    If it is, please let could someone let me know how...sorry if this seems
    like a dumb question!

    Many thanks,

    NickP
     
    Nick, Nov 16, 2004
    #1
    1. Advertisements

  2. Nick,

    You can create a domainname.co.uk forward lookup zone on your SBS server.
    Then you can create an A record named mail that points to your internal IP.
    Therefore when internal clients try to resolve mail.domainname.co.uk it
    will resolve to your internal IP. The problem with this method is now your
    server thinks it knows everything about the domainname.co.uk domain and
    will not forward DNS request for the domain to your external DNS servers.
    Therefore you will need to manually create all the A records you need to
    access and point them at the public IP. (www = 55.55.55.55)



    Best Regards,

    Justin Crosby, MCSE
    Microsoft Online Support Engineer

    Get Secure! - www.microsoft.com/security

    =====================================================
    When responding to posts, please "Reply to Group" via
    your newsreader so that others may learn and benefit
    from your issue.
    =====================================================

    This posting is provided "AS IS" with no warranties, and confers no rights.
    --------------------
     
    Justin Crosby [MSFT], Nov 16, 2004
    #2
    1. Advertisements

  3. Nick

    Nick Guest

    Hi Justin,

    That's kind of what I thought, I was just concerned about the DNS then
    thinking it completely responsible for the domain and how to get around it.

    Thank you; works a treat!

    NickP


     
    Nick, Nov 16, 2004
    #3
    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.