IWETHEY v. 0.3.0 | TODO
1,095 registered users | 1 active user | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New Re: Windows DNS server, but internally only.
I recall a problem with Win2K losing the first DNS server, and falling back on the secondary. This drove us nuts for quite a while at work, since desktops would stop resolving stuff on the local net, but could resolve names in the outside world. I *think* that we resolved the problem by adding a second internal DNS server, so that losing the first was benign. At the time (~3 year back) there was chatter on the net about the problem, but no acknowledgement from Microsoft.
New Thanks. Was that the *client* "losing the first DNS server"?
If so, maybe a dummy IP (for the second DNS server) would fix it.
New Yup. Win2K client was losing first DNS entry
The DNS server happened to also be Win2K, though that appeared to be unrelated to the client problem.
New Sounds familiar
We had to set up two nameservers at work, too. Sorry, nothing useful, just a Me Too.
===

Purveyor of Doc Hope's [link|http://DocHope.com|fresh-baked dog biscuits and pet treats].
[link|http://DocHope.com|http://DocHope.com]
     Somebody somewhere is lying to me about how DNS works - (FuManChu) - (6)
         Welp... - (folkert) - (5)
             Windows DNS server, but internally only. - (FuManChu) - (4)
                 Re: Windows DNS server, but internally only. - (dws) - (3)
                     Thanks. Was that the *client* "losing the first DNS server"? - (FuManChu) - (2)
                         Yup. Win2K client was losing first DNS entry - (dws) - (1)
                             Sounds familiar - (drewk)

Powered by blind unix!
80 ms