RE: The Redhat Linux server always try to resolve the local IP addresson the DNS.

From: Marco A. Ramos (mramos_at_sanyoval.net)
Date: 06/04/05

  • Next message: Frank Lee: "if the program need two input files"
    To: "General Red Hat Linux discussion list" <redhat-list@redhat.com>
    Date: Fri, 3 Jun 2005 18:55:56 -0700
    
    

    OK, I fixed changing the DNS server.

    I made this test the DNS reverse query (dig Ėx Local ip address) and the DNS
    respond with a timeout, I try with other DNS and this new one respond with
    no records but respond.

    The only question is, is correct that the server always try to resolve the
    IP address?

    Thank you,

    -----Original Message-----
    From: redhat-list-bounces@redhat.com
    [mailto:redhat-list-bounces@redhat.com]On Behalf Of Marco A. Ramos
    Sent: Friday, 03 June, 2005 6:49 PM
    To: redhat-list@redhat.com
    Subject: The Redhat Linux server always try to resolve the local IP
    addresson the DNS.

    The Redhat Linux server always try to resolve the local IP address on the
    DNS.

    For example if I made a ping to some a local PC the server not respond for a
    like 60 seconds, after that display the ping messages, if I put that IP
    address on the /etc/hosts file the ping respond immediately, the big problem
    with this situation is that the pop3 locals clients canít connect to the
    mail server because takes much time making the resolve query and the mail
    software client, respond with a timeout error.

    This happened with any configuration change.

    Information:

    - The DNS is the ISP site

    - The file /etc/host.conf has (order hosts, bind)

    - This happened with all IP address including address from the same
    network

    Any help?

    Thank you all, regards.

    Marco

    --
    redhat-list mailing list
    unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
    https://www.redhat.com/mailman/listinfo/redhat-list
    -- 
    redhat-list mailing list
    unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
    https://www.redhat.com/mailman/listinfo/redhat-list
    

  • Next message: Frank Lee: "if the program need two input files"

    Relevant Pages

    • Re: blocking annoying login popup applets
      ... > DNS server as centralized within my local network? ... Another machine is definitely not necessary for a local caching DNS ... Choice of djbdns vs. BIND: ... domains will resolve to 192.168.27.1. ...
      (comp.os.linux.networking)
    • Re: Dns.GetHostEntry functionality
      ... server as well as a DNS server. ... It is only the device that cannot resolve the name. ... The router is connected to the cable modem to the internet, but the router has DHCP turned off. ... don't have a network server you normally will not have a DNS server. ...
      (microsoft.public.dotnet.framework.compactframework)
    • Re: DNS not authoritative for domain
      ... I am using an internal DHCP server which is also my DNS and WINS ... I have configured a PPTP VPN using ISA to test whether or not I had an issue ... >> I can correctly resolve short and FQDN inside my domain. ...
      (microsoft.public.windows.server.dns)
    • Re: aol..
      ... These are all AOL's email server. ... DNS work fine. ... This newsgroup only focuses on SBS technical issues. ... If we unable to resolve this issue after steps above, ...
      (microsoft.public.windows.server.sbs)
    • Re: Cannot a DC, HOPELESS Case
      ... If the DC is not fully registered in DNS then it won't resolve ... the DCs NIC properties specify the correct DNS server. ... >>> error whenever I'm running DCpromo! ...
      (microsoft.public.win2000.active_directory)