I am talking about a 2 Server Solution - Client gets IP from W2K Server and Unix (Reliant RM400) is used for other applications and printing over xprint spooler.
If the client IP is changed by the W2K and is sending a print job to the spooler on the Unix Server, xprint receives the job, works on it and tries to send it back to the client by dns name => due to the changed ip the Unix server can't look up the client and xprint gives an error, saying that the client cannot be reached. Writing the IP of the Client into the hosts is not an option.
I don't really know what "named" you mean ( /etc/named.boot is the only i know so far ;) ) and what it does - so far we tried to kill the inet process with flag -15 but it simply doesn't restart...
TTL is about 30 Minutes which is not the satisfying option we are searching for - users with notebooks who change servers alot a day don't really have time to wait for max. 30mins to print ;)
nscd? Sorry 4 being noob :/
something like ipconfig /flushdns would be perfekt ;)
Main Topics
Browse All Topics





by: jleviePosted on 2004-04-22 at 09:25:08ID: 10890751
Are we talking about a DNS server or client?
On a DNS server stopping and restarting named will clear out any cached information it may have. However, on a server and a client the cached information may be further upstream and you simply have to wait for the TTL for the data to expire.
Also, the cache may not be in DNS. If the system runs nscd it may be caching the information.