This is workable for napster.com (which does not provide any other services
this site requires access to), but for AOL, Yahoo, etc creating a new zone
is unmanageable. I still need AOL's (as an example) web servers and e-mail
servers to resolve properly. If I create a new zone, this means that I have
to maintain a complete AOL host table, either manually or by scripting to
pull down their entire host table and then updating the entries I want to
resolve to loopback.
Isn't it possible to configure the DNS so that my internal DNS will respond
to queries for the specific DNS names (login.oscar.aol.com, for example) but
still pass other queries for the zone (aol.com, for example) on as normal?
Greg S.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 11, 2000 5:56 PM
To: Scheidel, Greg; [EMAIL PROTECTED]
Subject: RE: [FW1] Does anyone know how to block Napster?
On my case I added a new zone for NAPSTER.COM and pointed the domain itself
to 127.0.0.1 now whenever you try to connect to anything.NAPSTER.COM it goes
back to your loop back address.
+------------------------------------------------------------
| Jose J. Cintron - <[EMAIL PROTECTED]>
|
| Integrated Management Services, Inc.
| 2101 Wilson Boulevard, Suite 916
| Arlington, VA 22201
|
| Phone: 703.528.0334 x323
| FAX: 703.528.3477
| Web: http://www.imsidc.com/
+------------------------------------------------------------
-----Original Message-----
From: Scheidel, Greg [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 11, 2000 15:07
To: '[EMAIL PROTECTED]'
Subject: RE: [FW1] Does anyone know how to block Napster?
I have attempted to implement putting server.napster.com in our DNS, but
have not been successful. I have attempted adding it directly to the
named.root file, our standard hosts file, and a separate "hint" cache file
with no luck. The closest I've come is creating a separate
zone-of-authority on my DNS server for napster.com; this leaves me with the
obvious disadvantage that I would then have to go in and add entries for
every DNS name under napster.com that I *did* want to resolve correctly.
Not such a big deal for Napster, but unworkable for AOL or Yahoo!.
Can anybody describe how to implement this block via DNS?
Greg S.
-----Original Message-----
From: Igor Gashinsky [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 04, 2000 1:24 PM
To: Chris Close; '[EMAIL PROTECTED]'
Subject: Re: [FW1] Does anyone know how to block Napster?
Chris,
The way Napster apparently works, is that it connects to
server.napster.com, and asks it for the nearest napster server, so we
simply added an entry to our DNS to point server.napster.com
to 127.0.0.1, and that seemed to stop Napster on our network. This however
relies on the fact that our users do not know enough to edit hosts files,
or request resolution from another name server ;) Crude, but effective.
Your milege may vary.
-Igor Gashinsky
At 09:25 AM 4/4/00 -0700, Chris Close wrote:
>
>I know someone has probably already posted this, but I can't seem to find
>it.
>
>Napster is a MP3 sharing program that when running allows you to download
>MP3's off of other users PC's and allows them to download MP3's off of your
>PC as well. I know it has a configurable port which can be set to anything
>including 80 which needs to be open to allow web browsing, and I don't know
>if blocking access to Napster's addresses will work as it download's the
>files off of someone else's PC. I also think it has the ability to use a
>proxy server's web ports. Anyone got any ideas?
>
>Thanks
>
>Chris Close
>Sr. Systems Administrator
>Document Sciences Corporation
>mailto:[EMAIL PROTECTED]
>"Make it idiot proof and someone will make a better idiot."
>
>
>
>===========================================================================
=====
> To unsubscribe from this mailing list, please see the instructions at
> http://www.checkpoint.com/services/mailing.html
>===========================================================================
=====
>
============================================================================
====
To unsubscribe from this mailing list, please see the instructions at
http://www.checkpoint.com/services/mailing.html
============================================================================
====
============================================================================
====
To unsubscribe from this mailing list, please see the instructions at
http://www.checkpoint.com/services/mailing.html
============================================================================
====
============================================================================
====
To unsubscribe from this mailing list, please see the instructions at
http://www.checkpoint.com/services/mailing.html
============================================================================
====
================================================================================
To unsubscribe from this mailing list, please see the instructions at
http://www.checkpoint.com/services/mailing.html
================================================================================
