Re: blocking annoying login popup applets

From: /dev/rob0 (rob0_at_gmx.co.uk)
Date: 08/05/03


Date: Tue, 5 Aug 2003 06:24:02 -0700

In article <3F2F0B15.9EE08137@net0.net>, Wang Yu III wrote:
> /dev/rob0 wrote:
>
>> Please trim your excess quotes, Thank you.

"Excess quotes" refers to quoted material to which you are not making
any reference. You quoted my whole reply, whilst only indirectly making
reference to a small bit.

> Do you mean I would need to get another machine running Linux (or Unix) as
> DNS server as centralized within my local network?

Another machine is definitely not necessary for a local caching DNS
server. You can set it up on any existing Linux machine. Djbdns (did I
already give you the URL http://cr.yp.to/djbdns.html ? If so here it is
again, no extra charge :) does a fine job on dumpster-grade 486's. I run
it myself on a P166, which has a LOT of other server jobs.

> Well, I'm really thinking to do set up another box using an old laptop with
> 2 PCMCIA's (I got lots of working PMCIA NICs laying around) to do

Of course the more the merrier. :) If you only have one Linux box now,
you certainly would benefit from having another, because each can be
used to help troubleshoot network issues on the other. Windows gives you
few troubleshooting tools of any caliber, and NO good ones (unless you
go to the bother of installing something.)

> routing/filtering/blocking, etc. And I wanna whack that annoying Gator,
> too. Tell me more. Thanks.

1. Choice of djbdns vs. BIND:
    Djbdns is very easy to manage, once you figure out the documentation
    (which honestly, makes it sound harder than it is.) It runs well on
    junk. BUT ... as with other software from that author, standards are
    thrown out the window. Dynamic DNS, when a client sends its hostname
    to dhcpd, and then that hostname is resolvable to the assigned IP,
    is not possible with djbdns. I intend to switch to BIND for this
    reason, but I have not had time to undertake the project yet.
2. Here's my tinydns data, in relevant part:
#v+
    .gator.com:127.0.0.1:a:259200
    +*.gator.com:192.168.27.1:86400
    .date-manager.com:127.0.0.1:a:259200
    +*.date-manager.com:192.168.27.1:86400
    .gatoradvertisinginformationnetwork.com:127.0.0.1:a:259200
    +*.gatoradvertisinginformationnetwork.com:192.168.27.1:86400
    .feedbackresearch.com:127.0.0.1:a:259200
    +*.feedbackresearch.com:192.168.27.1:86400
    .bonzibuddy.com:127.0.0.1:a:259200
    +*.bonzibuddy.com:192.168.27.1:86400
    .webshots.com:127.0.0.1:a:259200
    +*.webshots.com:192.168.27.1:86400
#v-
    This machine is running tinydns on localhost, and dnscache on the
    internal IP, 192.168.27.1. Any request for ANY hostname in those
    domains will resolve to 192.168.27.1. You could as well have them
    resolve to 127.0.0.1. As you identify other troublesome domains
    (which you have done, and thanks, BTW, I have saved your list :)
    they can be added to your data file, 2 lines as shown. (I just
    noticed that "gator.com" returns "unknown host". To make the domain
    itself resolve, you would need an additional "+" line per domain,
    without the "*." after the "+".
3. This is just one of many wonderful things you can do with a local DNS
    server. Add aliases for all your services ... mail.yourcompany.lan,
    news.yourcompany.lan, et c. ... they can all resolve to the same IP
    for now, but if you ever need to split off a service onto a
    different host, you only have to update the alias and clients will
    follow! (You might want to stop and restart the dnscache service so
    as to delete the cached entry.) Be creative, have fun! :)

-- 
  /dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
  or put "not-spam" or "/dev/rob0" in Subject header to reply


Relevant Pages

  • Re: DNS not authoritative for domain
    ... I am using an internal DHCP server which is also my DNS and WINS ... I have configured a PPTP VPN using ISA to test whether or not I had an issue ... >> I can correctly resolve short and FQDN inside my domain. ...
    (microsoft.public.windows.server.dns)
  • Re: Dns.GetHostEntry functionality
    ... server as well as a DNS server. ... It is only the device that cannot resolve the name. ... The router is connected to the cable modem to the internet, but the router has DHCP turned off. ... don't have a network server you normally will not have a DNS server. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: aol..
    ... These are all AOL's email server. ... DNS work fine. ... This newsgroup only focuses on SBS technical issues. ... If we unable to resolve this issue after steps above, ...
    (microsoft.public.windows.server.sbs)
  • Re: Win2003 DNS not working using own ip address
    ... When it comes to DNS name resolution, ... the DNS server will respond to the ... client with a list of nearest names servers to resolve the name. ...
    (microsoft.public.windows.server.networking)
  • Re: Cannot a DC, HOPELESS Case
    ... If the DC is not fully registered in DNS then it won't resolve ... the DCs NIC properties specify the correct DNS server. ... >>> error whenever I'm running DCpromo! ...
    (microsoft.public.win2000.active_directory)