Re: mail malady - dns/postfix

From: Norberto Meijome (freebsd_at_meijome.net)
Date: 08/31/05

  • Next message: martin hudec: "Re: portsnap and updates using cron"
    Date: Thu, 01 Sep 2005 02:30:12 +1000
    To: Jerod Prothe <jprothe@usd217.org>, FreeBSD Questions <freebsd-questions@freebsd.org>
    
    

    Jerod Prothe wrote:
    >
    >
    > Norberto Meijome wrote:
    >
    >> Jerod Prothe wrote:
    >>> Norberto Meijome wrote:
    >>>> Jerod,
    >>>> pls define 'local citizens'. My view of "local" is surely different
    >>>> to yours.
    [...]
    >
    > Actually the ones complaining are the ones in the same domain as our
    > ISP. Meaning, pld.com (the one and only ISP in the area) subscribers are
    > having trouble emailing staff here.

    well, you could ask your ISP to make sure they have expired your zone if
    they haven't.

    you can easily test by doing
    nslookup - [your_isp's_NS]
    which will force nslookup to query that server.

    I've known ISPs that ignore the settings in SOAs and set their
    own....which is a real pain.

    Still that doesn't help with those others that haven't updated yet, so
    they are going to otto's IP for SMTP service. make that IP the one that
    galley uses (as well as galley's real...). or just wait it out...though
    for 100 days that wait will be long. I would definitely check whether
    your ISP's NS is playing along nicely.

    >> over time (depending on your SOA) this will get fixed.
    >>
    >
    > What are good values to have for refresh/expire/retry times in zone
    > files? I would very much like to have other's records concerning my
    > network to be up-to-date.

    well, it really all depends to what delay you're happy to live with.
    from memory:

    Refresh is the one that tells non-authoritative (downstream) DNS servers
      when to refresh the data.

    expire when to consider it too old to serve it at all (in case your
    authoritative is down)

    retry is how often to try to get the real info from your authoritative
    server.

    so refresh is the one you really want to focus on for when things work
    ok, and the others for when your server is in trouble ;). I'd say it
    roughly takes 2 times refresh time for propagation to most the network
    (from experience, could be completelly wrong). It also depends on how
    much your zone is cached of course (how many users request this zone
    determines how many non-auth servers you need to worry about).

    As I said, I've set some high traffic zones to 20 minutes refresh and it
    works really well for us - YMMV

    B
    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"


  • Next message: martin hudec: "Re: portsnap and updates using cron"

    Relevant Pages

    • Re: SMTP Service
      ... Your isp tech support is in another time zone. ... Using dns or a smarthost? ... server called smtpauth.earthlink.net. ...
      (microsoft.public.backoffice.smallbiz2000)
    • Re: [opensuse] RE: DNS caching only server setup issues request for help and patience
      ... zones with preference direct the master DNS server to ... that's o.k as I will leave my ISP in as authoritative. ... the DNS root server in Japan. ... If you have set up an empty slave zones it is unlikely to get a zone ...
      (SuSE)
    • Re: Re: Re: Bind9: rndc reload doesnt work for slave servers
      ... refresh interval in their SOA record anyway. ... wants you to poll their zone more frequently, then they can just reduce the ... refresh time in their SOA record, and your server will honour their ...
      (freebsd-isp)
    • Re: Help with Zone tranfers keep breaking
      ... because you can refresh from other available secondary. ... The Problem with running a secondary zone with two different AD Integrated ... since all AD integrated zones list the server they are on as the Master Name ... other depending on which one is listed on its MNAME record. ...
      (microsoft.public.windows.server.dns)
    • Re: DNS Upstream refresh
      ... Now I need to refresh the dns information upstream cause some MX servers ... zone, tunred on notify for the zone. ... of your mail server. ...
      (comp.os.linux.networking)