DNS Problem - Extraneous A Records keep coming back

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

  1. Paul Goldman

    Paul Goldman Guest

    I have a Win2K3 SBS system installed. Our company is at 2 physical
    locations, LA and Las Vegas. The 2 locations are connected via a branch
    office VPN. The SBS Server is in LA and is at IP address 10.0.0.253. There
    is a Win2K3 server in Las Vegas that is acting as a Domain Controller at IP
    address 10.1.0.11. If I ping the LA server by it's domain name, it pings at
    10.0.0.110. When I look at the DNS entries I notice that there is an entry
    for the SBS server at the 110 address and the 253 address. When I delete the
    110 entry and flush the DNS cache in Las Vegas, the ping results in address
    of 253. But, mysteriously, the A record for the 110 address keeps coming
    back, and the Las Vegas server pings 110, so obviously some process is
    putting it back in.

    In addition, there is an active directory synch problem between the 2
    servers. I tried to uninstall AD from the Las Vegas server, (so that I could
    later reinstall) but it failed with an error message "Active Directory could
    not transfer the ramining data in directory partition....The DSA operaton is
    unable to proceed because of a DNS lookup failure".

    I did not install these servers, and my predecessors were kind of weak. Does
    anyone have any ideas what is going on?
     
    Paul Goldman, Nov 16, 2004
    #1
    1. Advertisements

  2. Hi,
    The DNS behavior that you are seeing is expected on a server running DNS and
    RRAS, check the following article for a resolution on getting the proper A
    records registered:

    292822 Name resolution and connectivity issues on a Routing and Remote
    Access
    http://support.microsoft.com/?id=292822

    In regards to the replication issues, since they are highly dependant on
    name resolution, this will need to be addressed first. Make sure that the
    servers are pointing to a common DNS server and can access the proper SRV
    records. You might have to use metadata cleanup at this time to remove the
    orphaned DC off the AD and then attempt to re-add it again as a new DC.

    Regards,
    Damian

    --
    Damian N. Leibaschoff, MS IST, MCSE
    Microsoft Corporation

    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.
     
    Damian N Leibaschoff [MSFT], Nov 16, 2004
    #2
    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.