Re: DNS resolcing externally for local machines..
- From: GaryB <GaryB@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 24 Apr 2006 09:43:02 -0700
Thanx Lanwench..
The clients are picking up the external dns IPs from DHCP scope options. I
have
006 DNS servers (192.168.45.10, 194.72.6.57, 194.73.82.242 ). The DC has no
DNS options set on its NIC, and the only other place the external DNS servers
appear are as forwarders.
Should I remove the external DNS from the DHCP scope options and simply
leave the internal (192.168.45.10)?
This had worked for a year like this so a tad confused..
Appreciate you help..
G
"Lanwench [MVP - Exchange]" wrote:
Inline.....and this is why I wanted to see your ipconfig /all :).
In news:C2873D27-F73A-406C-A4EC-0F99578F4324@xxxxxxxxxxxxx,
GaryB <GaryB@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
An update if it may help any experts, seem odd that I have 4 entries
in the DNS Suffix Search List. On the 2000 member servers & 20003 DC
its only 1 entry which is the corp.OURcompany.
Windows IP Configuration
Windows IP Configuration
Host Name . . . . . . . . . . . . : XP_LAN_IT
Primary Dns Suffix . . . . . . . : corp.OURcompany.co.uk (This is our
internal domain)
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . :
corp.OURcompany(This is our internal
domain) ADServer (Our DC)
OURcompany (? This is also the name of
our external website)
co.uk
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : ADServer
Description . . . . . . . . . . . : Broadcom NetXtreme 57xx Gigabit
Controller Physical Address. . . . . . . . . : 00-0F-1F-E7-8A-F3
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.45.141
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.45.1
DHCP Server . . . . . . . . . . . : 192.168.45.10
DNS Servers . . . . . . . . . . . : 192.168.45.10
194.72.6.57
194.73.82.242
Ding! Here's your problem. You must *not* use any external IP addresses in
your AD clients' DNS settings. Only the internal (usually AD-integrated) DNS
server's LAN IP. Then you use forwarders on the local DNS server itself to
your ISP's DNS server to handle external lookups. AD relies heavily on DNS
and this is a very common misconfiguration - it's easy to fix, however.
Change your DHCP scope so it hands out only 192.168.45.10.
See http://support.microsoft.com/default.aspx?scid=kb;en-us;323380 for more
info.
Primary WINS Server . . . . . . . : 192.168.45.10
Lease Obtained. . . . . . . . . . : 24 April 2006 11:15:14
Lease Expires . . . . . . . . . . : 19 January 2038 04:14:07
- Follow-Ups:
- Re: DNS resolcing externally for local machines..
- From: Kevin D. Goodknecht Sr. [MVP]
- Re: DNS resolcing externally for local machines..
- References:
- Re: DNS resolcing externally for local machines..
- From: Lanwench [MVP - Exchange]
- Re: DNS resolcing externally for local machines..
- Prev by Date: Re: DNS resolcing externally for local machines..
- Next by Date: Re: Error: can't find _ldap._tcp.dc._msdc.<DNSDomainName>
- Previous by thread: Re: DNS resolcing externally for local machines..
- Next by thread: Re: DNS resolcing externally for local machines..
- Index(es):
Relevant Pages
|
Loading