Does Windows Print Server use DNS for client requests

We have Windows 2008 print server, we have network printers.
we manually map network printers for users to the print queue on windows servers.
Recently a Network print device10 has been moved to a different location (Area15) , and print device15 has been moved to area10 users in area15 were asked to reboot their computers to flush DNS, however when they printed, their print jobs ended up in area10, it has followed the old print device hostname.

I wonder if Windows print server can be part of the issue ?
I typed the command: Ipconfig /displaydns on print server, I saw correct hostname to ip mapping, I am not sure when and why does the print server do the mapping?

Any clarification will be very much appreciated.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

JohnBusiness Consultant (Owner)Commented:
The client machines will probably map by Printer Name so DNS may be needed for that.

Try the FLUSHDNS command on a problem workstation.

Open cmd.exe with Run as Administrator
ipconfig /flushdns followed by net stop dnscache followed by net start dnscache

Then restart the computer

See if that helps.
jskfanAuthor Commented:
if you run ipconfig /displaydns in the print server you will also see Dns host mapping to ip address of the printers.

I checked that in the print server.
in which case print server does that ?

**I thought PCs would only query DNS cache locally for host name if they cannot find it they query DNS server.They would never query Print server.
JohnBusiness Consultant (Owner)Commented:
Did you try flushing DNS?
Check Out How Miercom Evaluates Wi-Fi Security!

It's not just about Wi-Fi connectivity anymore. A wireless security breach can cost your business large amounts of time, trouble, and expense. Plus, hear first-hand from Miercom on how WatchGuard's Wi-Fi security stacks up against the competition plus a LIVE demo!

Spike99On-Site IT TechnicianCommented:
To avoid having to re-map those printers on each workstation, I would swap printer names so that people who were mapped to the Area15 printer will print to the Area10 printer once it's moved to their area & vice versa.

Here are the steps I would take (assuming the printer share names are "Area10" and "Area15"):
1.  Rename the Area10 Printer & change the Share name to Area15-TEMP (needed because you won't be able to give it the same name or share name as the other printer until you rename it)
2.  Rename the Area15 Printer & change the Share name to Area10
3.  Rename the Area15-TEMP Printer & Share Name to Area15

Since users are connecting to the print server by their share name, refreshing DNS won't help unless you also changed their share names.
jskfanAuthor Commented:
My Question is  Why print server DNS cache is caching printer hostnames ?
Seeing that Client PCs have DNS cache and if the host name is not in their cache they contact DNS server...
JohnBusiness Consultant (Owner)Commented:
Did you ever try flushing DNS ?
Spike99On-Site IT TechnicianCommented:
I think this issue might be a problem with share names & not with DNS, which is why I recommended changing the share names along with the printer names.  

When you physically moved the printers, did you change their share names?
jskfanAuthor Commented:
SHarename is the print queue name ..correct ?
Of course I changed the share names...


each sharename is mapped to a hostname, some hostnames have 2 or sharenames though .

but the problem is not there.....

PCs talk to hostnames , (in printer configuration is called Port), so the PC queries DNS server about the Port name, DNS server will render the IP of that hostname it has on the DNS table. the PC then uses that IP to send print jobs to...

The process does not involve print server at all...........

What I am asking if you go to print server and type Ipconfig /Displaydns........
you will see hostnames of the printers cached............
the Question is causes the print server to cache hostnames in DNS cache ?
The problem is that you manually map printers, the map follows the printer no matter where the printer is. Best way is to use GPP to push the printers to the users based on the location of the user and the printer.  Such that if you move a printer, you would update the GPP to match.

renaming the printer on the print server does not change the mapping on the user side. Change the IP on the print server is the only way to alter the user's mapped printer destination with the caveat that if the printers are different, the drivers will be mismatched and they will not be able to print until the drivers are updated to match the new printer mappings.
If this is shared printer mapped on client, no matter where you keep printer, it will work properly as long as server hosting that printer has online and reachable on SMB protocol and have print permissions.

If this typical standalone network printer (mapped with some IP port on client machine), then changing location might change / swap printer IP and then your print job might end up printed by wrong printer.
Also if you have manually created Host(A) records for this network printers, you need to change that as well.
Make sure client port mapping and dns hostnames if registered are correct for those printers.
Open a command prompt window and change to the directory:


and issue the command:

     cscript prnmngr.vbs -l > "somepath you can write to"\printers.txt

Then look at the files printers.txt.  For the printers you have changed verify that the printer name and port are what you want it to be.  The printer name should be "host\share" or "printername" depending on if the printer is a shared resource on another computer or you are just printing directly to a networked printer.  You also need to verify the port name, sometimes when you define a printer, even when shared from another computer, it will save the IP address of the printer.

Last thing to check is if you have a WINS entry for the "host" that the printer maybe shared on.  Remember, depending on how things may be defined, Windows still uses WINS in some cases for host name lookups.

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
jskfanAuthor Commented:
Thanks..I will check that later
JohnBusiness Consultant (Owner)Commented:
Thanks for the update and I hope the suggestions work out for you when you try them.
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

From novice to tech pro — start learning today.