On Thu, Jan 7, 2016 at 12:52 PM, Michael B. Smith <[email protected]> wrote: > Yes. just do it.
Apparently, it resolved itself yesterday. I left after a half day, when the DNS showed the PTR record as I posted. When I came in this morning, it all looks normal. No, I don't know why. But it all looks OK. I ran dnslint, and dcdiag, on most of the Domain Controllers, and didn't have any unexplained issues. So I guess I am good to go ... > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Michael Leone > Sent: Thursday, January 7, 2016 9:49 AM > To: [email protected] > Subject: [NTSysADM] Weird DNS issue - reverse zone > > Here's something odd. We had some DNS setting issues on a client, and the > record expired and dropped out of DNS. We corrected the DNS settings, and I > went to create a static record this time, rather than let it register (and > possibly expire again in future). > > And I got an error creating the PTR. Going to the reverse zone, I already see > a record there with the IP I am trying to add, but the record shows as a name > of "(same as parent folder)", with a type of "Pointer (PTR)", and data says > the name of the client we just just fixed. > > How this happened, I don't know. > > Ideally, I would just delete the record, and create a new, regular static PTR > (so it had the correct name of .the IP address, rather than "(same as parent > folder)". But I'm leery of deleting it, because of the type of record it says > it is. I looked at the properties of the zone, and it does show the correct > name servers; the rest of it looks OK, I think. > > Should I be able to delete this odd record, and then create a correct, static > PTR? > >
