🚀 go-pugleaf

On Monday, in article <933575060snz129.os2.7@sunshine.tm>
     corixia@btinternet.com "Richard Ashton" wrote:

> In article <19990801.2223.27547snz@dsl.co.uk>
>            bhk@dsl.co.uk "Brian {Hamilton Kelly}" writes:
> 
> >I've fixed the problem: this OS/2 machine is now running BIND v8.1.2a,
> >with a forwarders option to use my ISP's name server for anything other
> >than the local LAN.  Since that time (about 18:00 today:-), there have
> >been NO spurious requests for ISDNpm to connect to Demon (the resolvers
> >of each machine, OS/2 and Win9x, have been told to use this machine alone
> >for DNS).  I presume that whatever it is that the Win9x machines were
> >requesting every 900 seconds is now provided to them by my named.
> 
> Seems unlikely, AFAIK that version has no NetBIOS Name Server
> capability.

All the same, it's true.  Until I started running named on the OS/2
machine, the ISDNpm trace window used to show an attempt to connect to
Demon's nameserver (which each of the Windows machines knew about) every
15 minutes (more frequently if there was more than one of the Win boxes
alive).

Since I've had named running, it's been perfectly quiet: not a single
spurious dial-on-demand. :-)

I suspect that the traffic may be requests for the apocryphal top-level
domain WORKGROUP (although in my case, I have changed from the default).
YOY does a Windoze box ask the *DNS* for this???

-- 
Brian {Hamilton Kelly}                                         bhk@dsl.co.uk
    "But we're a university.  We /have/ to have a library!..."said Ridcully,
         "What sort of people would we be if we didn't go into the library?"
    "Students", said the Senior Wrangler, morosely. [TP: The Last Continent]