On Thu, Jan 7, 2016 at 12:20 PM, Charles F Sullivan <[email protected]> wrote: > When you created the A record, you had the option of selecting "Update PTR > record" (or similar to that). If you do that, I don't believe you should > have to do anything manual to get the PTR record changed.
I always do, yes. And I did, yes. > It should just happen, as far as I know. I would also disable dynamic DNS on > the client. > It's not working anyway, it seems, but if it works at all it could cause a > conflict. It did seem to correct itself, sometime yesterday (I left at noon; this morning, the PTR record looks normal) > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > On Behalf Of Michael Leone > Sent: Thursday, January 7, 2016 10:29 AM > To: [email protected] > Subject: [NTSysADM] Re: Weird DNS issue - reverse zone > > Also, dnslint shows no errors. dcdiag /a /c shows no DNS errors. > > On Thu, Jan 7, 2016 at 9:49 AM, Michael Leone <[email protected]> wrote: >> 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? > >
