Re: /etc/resolv.conf and sendmail

From: Nifty Hat Mitch (mitch48_at_sbcglobal.net)
Date: 07/20/04

  • Next message: Mark: "up2date and channels"
    Date: Tue, 20 Jul 2004 14:12:48 -0700
    To: For users of Fedora Core releases <fedora-list@redhat.com>
    
    

    On Wed, Jul 14, 2004 at 11:06:16PM -0400, Gene Heskett wrote:
    > On Wednesday 14 July 2004 14:05, Alexander Dalloz wrote:
    >
    > [...]
    > >
    > >Of course, if Philippe did give his Sendmail a hostname which is not
    > >resolvable, neither by the hosts file nor a DNS, his MTA will not
    > > work proper.
    ...
    > All of which makes sense (I think, I'm having trouble with he
    > "internal" status of AAA yet)

    I recall reading a comment that local host names for sendmail need "enough"
    dots. i.e.

          box.bogustopdomain # will not work for some.
          box.subdomain.bogustopdomain # can work.

    Since there is a AAA.com., aaa.net. and aaa.org resolver code could be
    looking any of these up because you do not have enough dots.

    I recommend the top two levels of a private host name be researched
    for conflicts. I once found a nifty but flawed how-to for sendmail
    and dns that said use "invalid.com". It turns out that there is a
    registered domain by that name. Following the directions in this case
    did unpredictable and possibly bad things.

      http://www.interex.org/tech/9000/Tech/sun_hpux_interop/chap10_dns.html

    In part the root of this is the ndots of resolver code (not really a
    sendmail problem). In some cases /etc/hosts can use dots to force
    termination and closure. i.e. DNS resolver code should understand
    that a trailing dot terminates the fully qualified domain name.

          192.188.1.5 boxa.aaa. boxa.aaa boxa

    Also "Mail -v fred@boxa.aaa." may respond differently than
    without the trailing dot "Mail -v fred@boxa.aaa". If things are correct
    they should be the same. Compare and contrast...

         host boxa.aaa.
         host boxa.aaa
         Mail -v fred@boxa.aaa.
         Mail -v fred@boxa.aaa

    next do a reverse lookup on the host results. Forward and reverse lookup
    should be consistent.

          $ host boxa.aaa.
          boxa.aaa. has address 192.168.0.51
          $ host 192.168.0.51
          51.0.168.192.in-addr.arpa domain name pointer boxa.aaa.
         
    Since aaa is not a subdomain of a .com .net or other high level domain
    this dot count thing could be important.

    In addition sendmail has a need to locally resolve private network
    addresses.

       http://sendmail.org/tips/private-dns/

    The point here is that if the reverse lookup fails for a private
    network as it will without local interaction mail will queue. This
    "should be OK" with hosts first in resolv.conf but I have not found it
    to be satisfactory.
     
    Also there may be issues with path MTU discovery for some ISP services.

        http://sendmail.org/tips/pathmtu.html

    It can be useful and diagnostic to force your outgoing MTU to be
    modestly sized.

    Lastly if you are on a DHCP assigned address you will find that
    setting up sendmail is painful. The short TTL for the domain name is
    a signature of dynamic DNS. Use the ISP's mail host as a smart host.
    This may require authentication. Set 'reply to:' headers on mail to
    be the ISP's assigned mail address. Collect mail from the ISP with
    fetchmail/ pop/ imap for local access.

    I once thought that MX records would be helpful but there is a window
    when your old IP address and DNS records could point to a different
    box. If that box answers then rejects mail, mail will bounce back to
    the sender.

    Summary:
    in etc/hosts

            192.168.0.10 a.aa.priv.notpublicnet a
        not
            192.168.0.10 a.aa a

    -- 
    	T o m  M i t c h e l l 
    	/dev/dull where insight begins.
    -- 
    fedora-list mailing list
    fedora-list@redhat.com
    To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    

  • Next message: Mark: "up2date and channels"

    Relevant Pages

    • Re: Postfix smtpd DNS lookup delay
      ... They are setup as CLI only boxes BTW. ... /etc/nsswitch.conf files (which DNS query tools ignore, ... Yes the "host" command with -t type lookups. ... so the resolver isn't going to be asking someone else. ...
      (alt.os.linux.suse)
    • Re: SuSE 8.0 and slow DNS resolution
      ... > suggests to the resolver that there is a DNS available for this domain. ... as the address given in the request is a full url including the dots, ... uname -a I'll come back with, I am not at the right machine now ...
      (comp.os.linux.networking)
    • Re: Web Site Mystery
      ... host our own web site at this location. ... So in our DNS setup, there is a pointer to the ip address of the ... Run an ipconfig /all on your server and you'll see the ... www.europacrown.com don't work from our corporate network. ...
      (microsoft.public.windows.server.general)
    • Re: Underscore in IIS 6 Host Header definition
      ... The RFC that you referenced does not define the standard for the DNS ... An underscore is not valid in a host. ...
      (microsoft.public.inetserver.iis)
    • Re: Retardedness
      ... have not written any reverse DNS code. ... Begins an asynchronous request for IPHostEntry ... information about the specified DNS host name. ... GetHostAddresses: Returns the Internet Protocol addresses for ...
      (alt.os.windows-xp)