Re: DNS with Active Directory problem
From: Herb Martin (news_at_LearnQuick.com)
Date: 02/01/05
- Next message: Herb Martin: "Re: Windows DNS and RBL Lookups"
- Previous message: Sam Hawas: "Re: Import DNS Records From Text File"
- In reply to: Dan Page: "Re: DNS with Active Directory problem"
- Next in thread: Dan Page: "Re: DNS with Active Directory problem"
- Reply: Dan Page: "Re: DNS with Active Directory problem"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 31 Jan 2005 20:19:08 -0600
"Dan Page" <dan.j.pageNOSPAM@NOSPAMbtinternet.com> wrote in message
news:#YgETo#BFHA.244@TK2MSFTNGP10.phx.gbl...
> Hi,
>
> I've applied you're advice and some things are working better now. Active
> directory MMC opens almost instantly, and my DNS server is forwarding
> queries it cannot resolve out to the internet, the cache is filling up
with
> website IP addresses. I assume this is right.
Sounds good. Cache is good. (We resolve without going
to the internet for every request if we already know the
answer.)
> Perhaps I wasn't very clear with my config, I'll try to explain better:
>
> DSL modem/router, IP 192.168.0.1 is connected to my Server's first NIC
> 192.168.0.2
> The IP addresses are both fixed and my DNS is set to forward unknown
> requests to 192.168.0.1
Ok. So the server is not DHCP assigned and will not
have to fight the DNS setting.
Just set the same DNS server on both NIC ( 10.10.1.1 or
192.168.0.1) and don't use any other (as long as you have
no other internal DNS servers.)
I assume you DSL/modem/router is also a (caching only)
DNS server.
You forward to it, it does the internet lookups or gets the
ISP to do them (by forwarding again.)
> All 9 client computers are connected via various hubs to my Server's
second
> NIC 10.10.1.1
> Addresses are assigned with DHCP, the servers IP 10.10.1.1 is fixed.
>
> What I don't get is this: My server is called "lionserver", when I sit at
> the computer and "ping lionserver" it pings 192.168.0.2 which is it's 2nd
> NIC. Shouldn't it ping 10.10.1.1 which is the LAN interface?
They are both LAN interfaces but that is my experience
too -- first NIC gets bound last, or it just registers them
both in DNS and the clients get them (round robing) and
pick one.
You can disable the registration of on of the NICs, or
you can register one of them under a different suffix,
or you can try altering (reverseing the binding order.)
-- Herb Martin > > Regards, > Dan > >
- Next message: Herb Martin: "Re: Windows DNS and RBL Lookups"
- Previous message: Sam Hawas: "Re: Import DNS Records From Text File"
- In reply to: Dan Page: "Re: DNS with Active Directory problem"
- Next in thread: Dan Page: "Re: DNS with Active Directory problem"
- Reply: Dan Page: "Re: DNS with Active Directory problem"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|