DNS Entry Getting Lost?

MGD King's Thoughts

Getting What's Inside My Head Out
 

About The King

The King of MGD!A lot of people ask me what does MGD King mean? Well, it was a nickname given to me because I used to drink large quantities of Miller Genuine Draft. Someone mentioned to me that I was the King of MGD, and so it stuck.

Twitterverse

Note: For Customization and Configuration, CheckOut Recent Tweets Documentation

DNS Entry Getting Lost?

by MGD King September 23, 2010 2:19 PM

For the last several months I’ve been having an issue with DNS (Domain Name Services) that I just couldn’t figure out! It seemed like at least once a week a user would call up and say “we can’t print to the Sales printer.” And every time, after some quick troubleshooting, it would be determined that the DNS entry for the printer would be lost! It was getting to the point that as soon as someone would call with a problem with that printer, I would immediately check DNS and re-add it because it would disappear!

Adding to the frustration was that this wasn’t the only printer that this happened to. Another printer in another building on it’s own subnet and DNS Server/Domain Controller was doing the exact same thing and never at the same time!!! I was beginning to think that it was related to the NIC cards on the printers because these were the only two devices on the entire network that would vanish from DNS! But they both began doing this as soon as they were installed.

As I said earlier I was going through this headache for months, close to a year as a matter of fact, and finally one day I sat down and said “I’m going to figure out what is causing this!" I opened up the DNS Admin Console and noticed that the hostname and IP addresses that I was having problems with, which were added manually and not through DHCP, had a date/time stamp on them (the DNS Admin Console for Windows Server 2008 R2 and Windows 7 displays the date/time stamp for DNS entries) where other hostnames/IP addresses that had been added manually didn’t; more specifically, ones that had been added or modified when we were still using Windows Server 2003 R2. Why did this entry and every new entry  that I tried testing with have a date/time stamp? That’s why the DNS entry was vanishing! It had an expiration date! Now I just have to figure out how to remove that date/time stamp!!!

I searched the Internet looking for anything that could shed some light on this and one article I found mentioned the “Advanced” view in the DNS Admin Console. “Hmm… I don’t remember an advanced setting in the DNS Admin console!” I thought. Then I found it! Right there under the View menu was a setting so simple yet so overlooked (the easy ones are always overlooked, aren’t they?) that I just couldn’t  believe that I had missed something that simple!!! After checking the “Advanced” option in the view menu here’s what I found when looking at an entry:

image

EUREEKA!!!! There it is!!! I unchecked the “Delete this record when it becomes stale” option and BINGO!!! The entry doesn’t vanish anymore and, more importantly, users won’t be calling saying that they can’t print!!! Well, they may still call but at least it won’t be for this nagging DNS issue!!!

So I guess the morale of the story is when using Microsoft Management Tools always remember to use the Advanced settings.

Comments (11) -

Lisvard
4/23/2013 10:52:08 AM #

I'm having the exact same problem, but the “Delete this record when it becomes stale” option is already unchecked. Did you change any other setting?

Reply

MGD King
4/23/2013 2:56:03 PM #

No, that was the only change I had to make (I think, it was some time ago). Maybe restarting the DNS services might help?

Reply

Chad
8/28/2013 5:57:32 PM #

My question, when I uncheck that and then refresh DNS it comes back on.  I am wondering if printer is turning that option back on and if so how?  Thanks

Reply

MGD King
8/29/2013 6:07:15 AM #

Chad, I don't believe it's the printer turning it back on. Is this this only DNS server you have on your network? Do you have a static IP assigned at the printer or is set to DHCP?

Reply

Chad
8/29/2013 2:19:50 PM #

I just went through and deleted some entries then recreated them manually and later the updated from static to a timestamp.  I also did a query for DNS servers and checked all of them.  None of them are set to scavenge old records.  So I am lost as to why these printers keep reverting back, any help would be greatly appreciated.

Reply

MGD King
8/31/2013 6:56:25 AM #

What kind of printers are they? Are they all the same kind? We had problems with Konica Minolta printers. How are they shared on your network, more specifically, how are the ports configured in your sharing?

Reply

Chad
9/6/2013 10:19:27 AM #

These are mostly Lexmark varying models, they are setup with DHCP reservations and DNS names.

Reply

MGD King
9/7/2013 7:57:22 AM #

Why the DHCP reservations? To me that seems a little redundant. We have our printers set up with DNS names, and assign a static IP at the printer which is outside the scope of DHCP addresses that we have defined, then all we do is set up a DNS A Record to that printer and share that name as the printer's port.

For example we have a DHCP range of 192.168.100.101 through 200 for workstations and assign printers addresses in the 201 to 220 range.

Reply

Glen
11/1/2013 9:30:25 PM #

Thank you.  This was driving me nuts.  I also select the Advanced View in ADUC and didn't even know it existed in DNS.

Reply

Distant Midget
11/13/2014 5:10:42 AM #

Oh my God, thank you so much, finally a fix.!
I've been losing my terminal server constantly, I knew it was DNS related as I could always RDP to the IP address but never the hostname. I just had it do the same thing on a new server I had built yesterday and decided it was time to fix this issue.

Chuffed now, there are now no niggly little issues on the LAN.
Cheers again.

Reply

DNS Admin
10/13/2015 6:20:53 PM #

The timestamp on the DNS record is for DNS Scavenging. Typically Scavenging is enabled to manage Dynamic DNS records - which can either be created by DHCP or by the Host itself. Though unchecking the timestamp setting does mean Scavenging won't delete it, there are various other reasons why the record could be deleted otherwise. For example, if DHCP wrote the record, it can delete it. If DHCP is configured for Dynamic DNS Updates, if a lease is manually removed or a reservation is applied over the lease, it will attempt to remove the DNS record - independent of DNS Scavenging. Additionally, with Dynamic DNS Updates enabled on the DHCP server - after the refresh interval, it’s going to overwrite the DNS record, so the Timestamp will eventually be re-added.

Your issue wasn't specifically the Timestamp, per say, it was a mismatch in configuration. If the printer was configured with DHCP enabled, its record should be dynamic (i.e. with a timestamp), if the printer is configured static, then either the printer needs to maintain its own DNS record through a periodic dynamic DNS update, or the DNS record needs to be manually added. Manually added DNS records don't receive a timestamp, so something else must have overwritten that record giving it a timestamp. Given you haven't explicitly granted anyone write access, you can look at the ACLs on the record to see who has write access - this will tell you who (or what) performed the dynamic update.

Reply

Add comment