Skip Navigational Links
LISTSERV email list manager
LISTSERV - COMMUNITY.EMAILOGY.COM
LISTSERV Menu
Log In
Log In
LISTSERV 17.5 Help - LSTOWN-L Archives
LISTSERV Archives
LISTSERV Archives
Search Archives
Search Archives
Register
Register
Log In
Log In

LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

Menu
LISTSERV Archives LISTSERV Archives
LSTOWN-L Home LSTOWN-L Home

Log In Log In
Register Register

Subscribe or Unsubscribe Subscribe or Unsubscribe

Search Archives Search Archives
Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: Panix DNS hijacking
From:
Ben Parker <[log in to unmask]>
Reply To:
LISTSERV list owners' forum <[log in to unmask]>
Date:
Mon, 17 Jan 2005 10:25:20 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (38 lines)
On Mon, 17 Jan 2005 10:39:36 -0500, Rich Greenberg <[log in to unmask]> wrote:

>Throughout this event, lists that I subscribe to which are
>hosted on Apple (not sure about Peach) continued to be delivered
>properly.  

Apple and Peach use the same DNS server.  It seems unlikely they would give
different results.

>Does Lsoft not use the usual DNS systems 

We use regular DNS.

>that expire records after (usually) 24 hours,  

The time-to-live (TTL) for how long a (local) nameserver should cache a DNS
record is set by the Start-of-authority record of the domain in question.  The
new/current record for Panix.com sets that at 900 seconds (15 minutes).  A
more typical time is 86400 seconds (24 hrs).  

>or does it internally cache certain domains
>on a longer term basis?

Actually the TTL is expressed as 2 values, a 'minimum' time (the common TTL
referred to above) which represents how long the information can be considered
'authoritative' or valid, and an 'expiration' time after which the record must
be considered invalid and discarded.  If a DNS refresh lookup is attempted
after the minimum time has expired, but before the maximum expiration time has
expired, AND the lookup attempt fails to return new information, the DNS
server will return the information to the requesting mail server from cache as
'non-authoritative'.  It is then up to the mail server to decide whether or
not to take a chance using this information.  Usually, mail servers will try
it.  And if it works (as it apparently did in your case) then you get the
mail.

I don't know that this is exactly what happened in this case, but it sounds
likely.

ATOM RSS1 RSS2

COMMUNITY.EMAILOGY.COM CataList Email List Search Powered by LISTSERV