It's unusual for a DNS record to be deleted straight away. It is usually dnsTombstoned first.
You can use ADSIEdit.msc to connect to DC=DomainDNSZones,DC=domain,DC=com, and the zone is located under DC=MicrosoftDNS. If the record is dnsTombstoned, it may still be there.
You can also use repadmin to confirm if the DNS record still exists:
>repadmin /showobjmeta CONTOSOMDDC1 "DC=contosomddc1,DC=contoso.com,CN=MicrosoftDNS,DC=DomainDnsZones,DC=contoso,DC=com"
10 entries.
Loc.USN Originating DSA Org.USN Org.Time/Date Ver Attribute
======= =============== ========= ============= === =========
12646 Default-First-Site-Name\CONTOSOMDDC1 12646 2014-02-03 18:44:13 1 objectClass
12646 Default-First-Site-Name\CONTOSOMDDC1 12646 2014-02-03 18:44:13 1 instanceType
12646 Default-First-Site-Name\CONTOSOMDDC1 12646 2014-02-03 18:44:13 1 whenCreated
12646 Default-First-Site-Name\CONTOSOMDDC1 12646 2014-02-03 18:44:13 1 showInAdvancedViewOnly
12646 Default-First-Site-Name\CONTOSOMDDC1 12646 2014-02-03 18:44:13 1 nTSecurityDescriptor
12646 Default-First-Site-Name\CONTOSOMDDC1 12646 2014-02-03 18:44:13 1 name
398215 Default-First-Site-Name\CONTOSOMDDC1 398215 2014-11-21 13:48:09 619 dnsRecord
12646 Default-First-Site-Name\CONTOSOMDDC1 12646 2014-02-03 18:44:13 1 objectCategory
20501 Default-First-Site-Name\CONTOSOMDDC1 20501 2014-02-03 20:08:18 1 dNSTombstoned
12646 Default-First-Site-Name\CONTOSOMDDC1 12646 2014-02-03 18:44:13 1 dc
0 entries.
Type Attribute Last Mod Time Originating DSA Loc.USN Org.USN Ver
======= ============ ============= ================= ======= ======= ===
Distinguished Name
=============================
There are scenarios where a domain controller will unregister and dnsTombstone its own A record if there is a problem. This can occur even if the A record is static. If dnsTombstone is true, at least you may be able to correlate the time it occurred.
ipconfig /flushdns
flushes the DNSclient
cache and is not related to the DNS server component or the registration of AD related DNS records, AFAIK.