From: "Joseph C. Lininger" <jbahm@pcdesk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: domain: proppogation problem
Date: Thu, 5 Feb 2004 12:19:44 -0700 (Mountain Standard Time) [thread overview]
Message-ID: <Pine.WNT.4.58.0402051217390.2144@merlin> (raw)
In-Reply-To: <20040205162100.GA1511@comcast.net>
Hello,
Actually, if you have bind configured properly and dig works right on your local machine, there really isn't anything you can do. It can take 24 to 48 hours for dns information to propogate, and sometimes even longer if values have been cached by the machine your testing from.
--
Joseph C. Lininger
jbahm@pcdesk.net
On Thu, 5 Feb 2004, Igor Gueths wrote:
> Hi all. Last night I got rndc working and now it seems the server is
> running as it should be. However, when I try resolving my domain from a
> machine other than mine, on a different network, it still isn't found.
> This means that I have still not been noticed by the root servers. I
> don't remember who said this, but what was mentioned was that the
> proppogation time had to do with the way your zone file was written.
> Would the MINTTL field of the SOA record by any chance have something to
> do with this? Currently, I have my serial number set to yyyymmdd format,
> refresh is 1H, retry is 2H, expire is 1W, and TTL is 1D. I assume that
> since TTL is set to 1 day that it can take up to 24 hours to proppogate,
> and that if I want to reduce this time I should reduce the TTL field? Am
> I still going wrong on something here? P.S: Thanks for all the replies
> so far!
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Igor Gueths
` Joseph C. Lininger [this message]
` Igor Gueths
` Luke Davis
` Igor Gueths
` Shaun Oliver
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.WNT.4.58.0402051217390.2144@merlin \
--to=jbahm@pcdesk.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).