Brian Trudeau wrote:
> I keep having problems with domainkeys, I’ve followed the instructions
> to the letter at http://www.qmailtoaster.com/qt-doc/QT-README.domainkeys
> and it still is failing almost 24 hours later. I got it working before
> but I had updated qmailtoaster with the newer rpms released on the 16^th
> and it hasn’t worked since… It fails at
> http://www.skylist.net/resources/senderID_results.php and to all the
> autoreplies at [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>.
>
>
>
> Here’s what my djbdns config looks like…
>
>
>
> '_domainkey.eastek-intl.com:o=-; [EMAIL PROTECTED]
>
> 'private._domainkey.eastek-intl.com:k=rsa;
> p=MEwwDQYJKoZIhvcNAQEBBQADOwAwOAIxAMlJYD1aLGvm5pLnxEnXl0Vlv4Qfjx4UBrfSlEUgriFSHdStgqqCuBIllAIUabpkEwIDAQAB
>
>
>
> I made a little script to check the key at different points, I can’t
> believe it takes THIS long for it to update. It took less time the 1^st
> time I installed the new qmail with domainkeys then this time to update
> the key.
>
>
>
> ./chk_domainkey.sh
>
> tinydns :
> MEwwDQYJKoZIhvcNAQEBBQADOwAwOAIxAMlJYD1aLGvm5pLnxEnXl0Vlv4Qfjx4UBrfSlEUgriFSHdStgqqCuBIllAIUabpkEwIDAQAB
>
> localdns:
> MEwwDQYJKoZIhvcNAQEBBQADOwAwOAIxAMlJYD1aLGvm5pLnxEnXl0Vlv4Qfjx4UBrfSlEUgriFSHdStgqqCuBIllAIUabpkEwIDAQAB
>
> external:
> MEwwDQYJKoZIhvcNAQEBBQADOwAwOAIxAMlJYD1aLGvm5pLnxEnXl0Vlv4Qfjx4UBrfSlEUgriFSHdStgqqCuBIllAIUabpkEwIDAQAB
>
> extern#2:
> MEwwDQYJKoZIhvcNAQEBBQADOwAwOAIxAMlJYD1aLGvm5pLnxEnXl0Vlv4Qfjx4UBrfSlEUgriFSHdStgqqCuBIllAIUabpkEwIDAQAB
>
> extern#3:
> MEwwDQYJKoZIhvcNAQEBBQADOwAwOAIxAMlJYD1aLGvm5pLnxEnXl0Vlv4Qfjx4UBrfSlEUgriFSHdStgqqCuBIllAIUabpkEwIDAQAB
>
> internet:
> MEwwDQYJKoZIhvcNAQEBBQADOwAwOAIxALibc4P7lOLP/x82AwICOHr+HDwgU+PG7OXRlxleLGqC3zsQZEZg1B2DmK3G/QxzVwIDAQAB
>
> itnern#2:
> MEwwDQYJKoZIhvcNAQEBBQADOwAwOAIxAMlJYD1aLGvm5pLnxEnXl0Vlv4Qfjx4UBrfSlEUgriFSHdStgqqCuBIllAIUabpkEwIDAQAB
>
>
>
> Anyone have any ideas what I’m missing here, or am I just really
> impatient? It did fail at one of my ISP dns caching servers, but they
> are always slow when it comes to dns updates, and way behind the rest of
> the internet.
>
>
>
> --
>
> Brian Trudeau, Network Administrator
>
Brian,
The way DNS works is actually quite simple, and often misunderstood. Let me
try to explain it.
When a DNS server (caching or otherwise) obtains a DNS record, it caches it
for as long as the TimeToLive(TTL) parameter for that record specifies (TTL
is specified as a number of seconds). If a particular DNS server doesn't
have the old record yet, it will acquire the new record right away. Servers
that do have the old record will acquire the new one as soon as their copy
of the old one expires, which depends on 1) when they obtained the old copy,
and 2) the value of TTL. So you see, the "slowness" in updating is actually
controlled by very record you're maintaining.
While you're getting things set up, a reasonable TTL value is 3600 (1 hour),
or perhaps even 300 (5 minutes). Once things are working though, be sure to
reset TTL to a more (network) friendly value, such as 86400 (1 day) or more.
FWIW, if you use the "dig" command to look up DNS records, you'll see the
TTL value decrease on subsequent inquiries. "dig" is worth getting to know
if you need to configure DNS.
--
-Eric 'shubes'
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
