Reverse Lookup Zone record problem

Discussion in 'Windows Small Business Server' started by G.Y, Jul 11, 2006.

  1. G.Y

    G.Y Guest

    Recently I have noticed that on our SBS 2k3 sp1 box DNS-->Reverse lookup
    zone having the following problem
    1.It contains multiple PTR record. for one computer eg.
    Name:10.1.1.1
    Type: PTR
    Data: andrewpc.domain.local

    Name: 10.1.1.10
    Type: PTR
    Data: andrewpc.domain.local

    Name: 10.1.1.12
    Type: PTR
    Data: andrewpc.domain.local

    Name: 10.1.1.14(This is the actual IP of andrewpc,but it points to other pc)
    Type: PTR
    Data: kenpc.domain.local

    In the Forward Lookup Zone:
    andrew points to 10.1.1.14 This is the actual IP assigned by DHCP

    2. Some PTR record are wrong for some PC but not all of them

    It looks like Rverse Lookup Zones are not updating itself and keep adding
    more records for the same pc if this pc's IP is changed. However,DHCP and
    Forward Lookup Zones appears to be quite normal.

    I remembered DNS setting was using 'Integeted with AD' and Update was
    Secure Only. I tried to reload this zone, it doesn't change.

    Did anyone have this kind of problem before? If you need any more info to
    trouble shoot, let me know

    Server OS: SBS2003 SP1
    Running DNS,DHCP,Exchange,AD

    Client PC: Win XP sp2


    Any help is appreciated!!!!!!! Many thanks

    G.Y
     
    G.Y, Jul 11, 2006
    #1
    1. Advertisements

  2. G.Y

    Gregg Hill Guest

    Set it up to scavenge stale records.

    Gregg Hill
     
    Gregg Hill, Jul 11, 2006
    #2
    1. Advertisements

  3. G.Y

    G.Y Guest

    Thanks Gregg.That is a good point.

    I've also set up DHCP to dynamic update DNS A and PTR records.
     
    G.Y, Jul 12, 2006
    #3
  4. G.Y

    Gregg Hill Guest

    You are welcome! It works every time for me.

    Gregg Hill
     
    Gregg Hill, Jul 12, 2006
    #4
  5. G.Y

    G.Y Guest

    I've tried torun aging and scavenge on DNS server, but it doesn't clean up
    any stale records, any reason why?
    Now I have to count on the settuing that aging interval(both non-refresh and
    refresh) is 1 day. So it should do its job within 2 days.

    I will let you know if it works next week.Gregg
     
    G.Y, Jul 13, 2006
    #5
  6. G.Y

    Gregg Hill Guest

    G.Y.,

    I have always manually deleted the incorrect records or just dumped all the
    records, ,then let them re-create on their own. Once they get re-created
    after I have set it up to scavenge stale records, I no longer have incorrect
    records, even months later.

    Perhaps it only changes the setting for records created after the scavenging
    has been set up?

    Gregg Hill
     
    Gregg Hill, Jul 13, 2006
    #6
    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.