Can not delete a PTR record

Discussion in 'DNS Server' started by Mehmet YILDIZ, Apr 15, 2009.

  1. Hello,

    We have 6 DC W2K3 servers which are all DNS servers too. DNS data are AD
    integrated.

    My problem is that I have a PTR record in a reverse lookup zone that I
    cannot delete !!!! Every time I delete this record it comes back instantly.

    The « hostname » of this PTR record does not exist.

    What kind of magic can make it reappear in the DNS ??

    Thanks for your help





    My English is poor, so I'll explain my problem in French too.

    Notre architecture AD comprends 6 DC en W2K3 qui font office de serveur DNS
    par la meme occasion. Le DNS est intégré à l'AD

    Dans une zone inversée, nous avons un enregistrement PTR qu'on arrive pas à
    supprimer. En effet, à chaque fois que je supprime celui-ci, il réapparait
    aussitot.

    Le "hostname" correspondant au PTR n'existe pas

    Par quelle magie celui-ci revient-il dans le DNS ?


    Merci de votre aide.
     
    Mehmet YILDIZ, Apr 15, 2009
    #1
    1. Advertisements

  2. Hello Mehmet,

    Your English is fine.

    What is the record that is registering? Is it a domain controller or a
    non-DC? If a domain controller, it is automatically registering. If you see
    an extra record registering for a specific DC, the DC may be multihomed and
    both interfaces are registering. However, if this is not the case, we'll
    need more information regarding the type of record, if any of the DCs are
    multihomed (more than one IP or more than one NIC), etc, because it is
    difficult to tell with the limited information you've provided.

    --
    Ace

    This posting is provided "AS-IS" with no warranties or guarantees and
    confers no rights.

    Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
    Microsoft Certified Trainer


    For urgent issues, you may want to contact Microsoft PSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.
     
    Ace Fekay [Microsoft Certified Trainer], Apr 15, 2009
    #2
    1. Advertisements

  3. What is the record that is registering?
    It's a PTR record registered in a Reverse Lookup Zone
    No, it's not a DC, the PTR record matches an old linux server that was
    suppressed from DNS one year ago.
    There is one multihomed DC but, this one is only listening to one selected
    IP address

    ==> All DCs are DNS/WINS/DHCP installed with W2K3 R2 SP2 UK

    My problem :

    I had a linux server called "LOIS" with ip 192.168.0.1.
    A static (Host) A record was created on DNS with the corresponding PTR
    record.
    This server was suppressed last year. Its host record was deleted but not
    the PTR record.

    Now we are installing a new server called "tom" and with the same IP address
    (192.168.0.1)

    So, there are theses records in DNS:

    Forward Lookup Zone
    tom 192.168.0.1

    Reverse Lookup Zone (192.in-addr.arpa)
    192.168.0.1 tom
    192.168.0.1 LOIS (this record is in upper case, all others records are in
    lower case)

    I have tried to create a new HOST (A) record named "LOIS" with corresponding
    PTR
    But this operation create a new PTR record called "lois" (in lower case)
    So I have three PTR records in Reverse Lookup Zone "192.in-addr.arpa" with
    the same IP address ("tom", "lois" and "LOIS")

    Deleting host record "LOIS" only delete the PTR record "lois" (in lower
    case)

    Best regards.
    Thanks for your help
     
    Mehmet YILDIZ, Apr 16, 2009
    #3
  4. If I may suggest and recommend, never multihome a domain controller. Even if
    you set DNS to listen to one, the multihomed DC will register duplicate
    records in DNS, such as the LdapIpAdress and GcIpAddress records, which will
    cause problems with client access, group policies, DFS, etc. I have created
    a step by step to make necessary registry and other changes if you like to
    keep your DC multihomed to insure a multhomed DC functions properly.

    What does 'surpressed' mean?

    Is the Reverse Zone a secondary zone, or is it AD integrated? Are there any
    secondaries of this zone that another machine, possibly with the LOIS name
    is using, which wuold send DNS updates to it?
    If the record is in upper case, then it means the original host that is
    sending the DNS updates to was spelled using upper case. DNS is not case
    sensitive, but will honor case when accepting registration requests.

    If the reverse zone is AD Integrated, and you change the update settings to
    Secure Only, and delete the bad PTR, does it return?

    Ace
     
    Ace Fekay [Microsoft Certified Trainer], Apr 16, 2009
    #4
    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.