DNS question and Exchange 2010

Hi,
I'm running Exchange 2010 and my own DNS server ( I know it's not recommended but I've been doing it fine for the past few years).
Just recently I've been having some odd error messages in my queues. I've already posted a question here about that so I'm not going to go into that again.( http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_28583497.html )  
But something I noticed is that the timestamp on my DNS entries for my two mail servers (.72 and .73) has changed recently to a recent date, just about the same date I started having trouble.
My question is this, what could cause those timestamps to change? I did not change them. Would some internal process cause them to change?

Thanks,
Nacht
Screen-shot-2014-12-22-at-7.43.37-AM.png
LVL 1
nachtmskAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Simon Butler (Sembee)ConsultantCommented:
That appears to be an internal DNS server, so I don't understand where you are getting the idea that it isn't recommended. Everyone with Active Directory needs to have an AD DNS Server.

As for why, the zone should be AD integrated, so that would suggest the zone and host has been updated. If you were NOT seeing frequent updates then that suggests there is a problem with AD. If I look at my own then the timestamp is earlier this month.

Simon.
0
Dan McFaddenSystems EngineerCommented:
This means that the server(s) automatically updated the registration of their A record.  This is normal and allows for DNS scavenging to run and clean old, outdated DNS records.  You can prevent this record from ever being scavenged by doing the following:

in DNS Manager (with admin permissions)
1. find the record and right-click it, select properties
2. Uncheck "Delete this record when it becomes stale"
3. click "OK"

The timestamp should now report "static"

The problem with this is, if you ever replace this server and do not keep the same services and IP address, you will have to manually delete the record.  It means more Admin work.

With the server being responsible for registering and re-registering (updating the timestamp), you will not have to manually manage the DNS record.  This function goes along with the NIC IPv4 configuration under advanced on the DNS tab where is says: "Register this connection's DNS address."  Which is typically on for both static & DHCP configured Windows devices.

I would say that, if you check these things, all will be in order.

Dan
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DNS

From novice to tech pro — start learning today.