Re: conflict between .local and .com

From: Lanwench [MVP - Exchange] (lanwench_at_heybuddy.donotsendme.unsolicitedmail.atyahoo.com)
Date: 11/19/04


Date: Fri, 19 Nov 2004 14:06:17 -0500

fixitman wrote:
> Yeah.. on closer scrutiny I found the possys.com entry in DNS

Entry? What kind? In what zone?

> and I
> removed it. So now that behavior went away, but on most clients I
> can't resolve outside addresses unless I add the ISP DNS to the the
> (client) NICs.... and even then nslookup dosn't resolve most (but not
> all) local domain names.

Then there's a problem somewhere - your internal DNS server's forwarders.
Try changing to different external DNS servers for there.
>
> I listed my server and Client ipconfig /all output in my latest
> response to the thread "Losing Clients".

Can't find it - since this is related, post it here.
>
> Unfortunately I can't "Remove" the DNS IP's from the client nics
> until I get this resolved. Otherwise I'd get lots of evil looks from
> folks who can't read their email or browse the web! ;)

You can test this on one machine.
>
> "Lanwench [MVP - Exchange]" wrote:
>
>> fixitman wrote:
>>> Ok.. I'm still having some nslookup weirdness. I have had to
>>> temporarily go around to all our clients and put one of our ISP DNS
>>> IP's in because otherwise they can't hit our off-site pop server and
>>> our off-site web page.
>>
>> Undo that. It will cause you no end of problems.
>>
>>>
>>> I can see that its a confilict between our offsite .com address and
>>> our .local address.
>>
>> No - if you have forwarders configured properly, requests for
>> anything.com will be resolved by your ISP's DNS servers.
>>>
>>> Here is what happens with nslookup:
>>> If I try one of our client machines by typing in
>>> "machine1.possys.local" nslookup can't resolve the name. But, if I
>>> type in "machine1.possys.com" it resolves it fine. but we have no
>>> local possys.com web page.. instead that's served by our web hosting
>>> agency. So where might I have "possys.com" entered where I
>>> shouldn't?
>>
>> You don't have a zone defined for possys.com in DNS, do you? You
>> wouldn't, by default...everything ought to work. Were you having
>> problems resolving names (mail.domain.com, www.domain.com ) by
>> pinging it (even if it didn't reply), or were you having problems
>> accessing the external servers themselves from your network?
>>
>> Standard or Premium (ISA) SBS?



Relevant Pages

  • Re: DNS signature failed to verify error
    ... In our last we discussed the need for there to be a NS record for each DNS ... Under the zone domain.local there is a delegation _msdcs which only has one ... _msdcs.domain.local is configured the "Replicate to all DNS servers in the AD ... Thanks for the DCDiag syntax suggestion. ...
    (microsoft.public.windows.server.dns)
  • Re: Windows 2008 DNS Secondary 2003 primary DNS zone
    ... I have a primary DNS zone "mydomain.com" running on a 2003 DC, ... we register our domain names with) All the DNS servers are AD domain ... When you have an AD integrated zone, the DNS data is stored in the actual AD database and is replicated to all DCs and will be available to any DC that has DNS installed, depending on the zone replication scope setting. ...
    (microsoft.public.windows.server.dns)
  • Re: 2 Questions...
    ... In one post you asked about the value of the empty root. ... With a multi-domain forest one has a few choices for DNS ... One could use standard zone transfer to these, ... as already stated or by having the DNS servers of corp forward to ...
    (microsoft.public.windows.server.dns)
  • Re: Question re: DNS forwarding best practices
    ... change rate of the root DNS zone's content. ... to a primary of the zone, so hopefully you have at least one ... as the case might allow) to the DNS servers of the root. ...
    (microsoft.public.windows.server.dns)
  • Re: sys vol check
    ... instead of the local DNS server and two ISP DNS servers. ... I need to configure the DHCP to use all three internal DNS servers ... If DNS zones are AD Integrated are writtable. ...
    (microsoft.public.windows.server.active_directory)