Re: Config check for box swith two nics

From: Paul Howarth (paul_at_city-fan.org)
Date: 03/21/05

  • Next message: Felipe Alfaro Solana: "Re: Fork bombing a Linux machine as a non-root user"
    Date: Mon, 21 Mar 2005 17:28:07 +0000
    To: For users of Fedora Core releases <fedora-list@redhat.com>
    
    

    GPL wrote:
    > I may have been over thinking this. My internal DNS will resolve names
    > on the internal net and external net. I think now in the way I have
    > been reading the responses to this thread that I feel better about my
    > understanding of this process.
    >
    > One thing though regarding the hosts file:
    >
    > 127.0.0.1 localhost.localdomain localhost
    > 10.192.0.200 windmere.internaldomain.com windmere
    > 208.x.x.x windmere.externaldomain.com windmere
    >
    > Is it bad practice to give the box two FQDNs per network? Would I
    > experience any negative repercussions from approaching the setup in
    > this manner?

    That should be fine.

    What I would do in this situation is install the caching-nameserver
    package so that you resolve all names yourself. Then, add the following
    entries to your named.conf to forward queries for internal names and
    addresses to the internal DNS servers:

    //
    // Forward requests for internaldomain.com to intranet DNS servers
    //
    zone "internaldomain.com" {
            type forward;
            forward only;
            forwarders { 10.192.0.1; 10.192.0.2; };
    };

    //
    // Similarly, forward rDNS lookups for internal network
    //
    zone "10.in-addr.arpa" {
            type forward;
            forward only;
            forwarders { 10.192.0.1; 10.192.0.2; };
    };

    The IP addresses in the "forwarders" lines should be those of your
    internal DNS servers.

    This means that you don't rely on your ISP's DNS servers for external
    name resolution, and you can still resolve external names without delay
    even if your internal DNS servers are unavailable.

    Internal lookups will be referred to the internal DNS servers as before.

    Your resolv.conf should just point to localhost. No external DNS servers
    need to be mentioned there. Just make sure that named starts at boot time.

    >>What routes other than those above do you want?
    >
    > The routes were what the box generated itself, I added no further
    > routes. Works fine from what I have tested.

    That's OK then.

    Paul.

    -- 
    fedora-list mailing list
    fedora-list@redhat.com
    To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    

  • Next message: Felipe Alfaro Solana: "Re: Fork bombing a Linux machine as a non-root user"

    Relevant Pages

    • Re: DNS Forwarders - weird question
      ... > their DNS servers and all is well. ... Their hosts resolve off their DNS ... > requests to bigcompany's internal DNS servers, ...
      (microsoft.public.windows.server.dns)
    • Re: Config check for box swith two nics
      ... > on the internal net and external net. ... Your /etc/resolv.conf should point to your internal DNS servers. ...
      (Fedora)
    • Re: DNS Forwarders - weird question
      ... > forwarding and is sent to bigcompany's DNS servers. ... > servers don't resolve their own website and it fails. ... > should be sent to my ISP's DNS servers instead of bigcompany's DNS ... Thus when my DNS server forwards these>>> requests to bigcompany's internal DNS servers, ...
      (microsoft.public.windows.server.dns)
    • Re: VERY Slow startup - Workstation Service error?!?!
      ... I've double checked the settings - when ... internal DNS servers. ... Still seems strange - it happens even when the network is ... >Domain members must be setup to point to an internal DNS ...
      (microsoft.public.windowsxp.general)
    • Re: Nameserver scenario with advertisers and resolvers
      ... Sorry, but here is another question, if I have my resolvers setup correctly, ... Now when I setup my internal DNS servers to query my ... what configuration should I use for internal DNS? ...
      (microsoft.public.windows.server.dns)