Re: mail malady - dns/postfix

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

  • Next message: Norberto Meijome: "Re: portsnap and updates using cron" 
    Date: Thu, 01 Sep 2005 01:59:09 +1000
To: Jerod Prothe <jprothe@usd217.org>

    Jerod Prothe wrote:
    >
    >

    >
    > CNAME to galley? That's a good idea.
    this will only affect those who have an updated record of your zone and
    can see that new record. For those that still think that MX is otto on
    it's real(old) IP, the CNAME wont help them a bit. Assigning otto's
    public IP to galley will fix this problem.

    Also, you may want to make triple sure the serial of your zone gets
    updated with every change...else downstream DNS servers wont necessarily
    pickup the changes.

    > I changed it and reduced the
    > expire time to 10d (I got it out of the Lehey Complete FreeBSD book). I
    > wonder why it is that Australia has updated but a US State has not?
    >

    because i never looked up your zone before, so when I just did it, it
    had to go to the authoritative server to look it up. that info is
    correct, hence what I can see is correct.

    and for your own sake, if your servers can take it, i'd reduce those 10d
    to whatever delay you are willing to put up with for updates in your
    zone. I just beef up the DNS server and set it to 20 minutes - which
    equates to almost full propagation in about an hour or so (with most of
    the traffic updated within 30 minutes). **YMMV**.

    Best,
    beto
    _______________________________________________
    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: Norberto Meijome: "Re: portsnap and updates using cron"

    Relevant Pages

    • Re: DNS and active directory
      ... my other two w2k3 DNS servers are listed so I am guessing ... on my Root domain dns server is set to replicate to "All DNS servers in the ... SHOULD be set to replicate to the forest so that the updates for each zone ... DNS data can be replicated in various application directory partitions (in ...
      (microsoft.public.windows.server.dns)
    • Re: Nameserver scenario with advertisers and resolvers - Solution Sum
      ... These are the two "hidden" DNS servers. ... I setup two more DNS servers in a Primary/Secondary configuration ... I created the zone for the internal domain. ...
      (microsoft.public.windows.server.dns)
    • Re: AD integrated/secondary zone entry discrepancies in W2k forest
      ... The DNS servers are clients too, ... The child domain DNS servers need to be able to query the root domain ... zone, and one way to do that is by having an active-directory integrated ... confusing and it may be simpler to make them all standard secondaries. ...
      (microsoft.public.windows.server.dns)
    • Re: 4010 Error continue
      ... Reed Wiedower posted their thoughts, ... > restart either of my two DNS servers the logs are filled with 4010 ... > Directory is functioning properly and reload the zone. ... I would first delete the netlogon.dns file, and restart the ...
      (microsoft.public.win2000.dns)
    • Re: Error on Forwarders in my dcdiag results
      ... > with both of my ISP DNS servers (would occurr about 1-2 times per ... > 1.0.0.127.in-addr.arpa zone nor do I want one. ... PTR and it is in the 127.in-addr.arpa. ... if you use 127.0.0.1 in your DNS server it will send this query to the ...
      (microsoft.public.windows.server.dns)