Re: Internal domain resolving to external domain not owned by us

On 4 Nov, 12:29, James Yeomans BSc, MCSE
<JamesYeomansBScM...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi there, so if i understand correctly your internal domain "domain.net" is
also registered on the internet by a different company? You say some pc's are
experiencing name resolution problems and resolving queries to an external ip
adress? Those machines probably dont have your dns server configured as their
dns server in the tcp/ip properties. If they were using your dns server they
would either resolve the address or they would get a response that the record
does not exist. Assuming your zone is authoritative (which it probably is)
then any queries for "domain.net" will be resolved or unanswered, they will
not be forwarded. So check the tcp/ip configuration on the computers with the
problem.
James.
--
James Yeomans, BSc, MCSE  
Ask me directly at:http://www.justaskjames.co.uk



"durx" wrote:
Due to a merge, we are now migrating our domain - domain.internal to
the second aquired domain -  domain.net.
Due to certain pressure we have no choice but to migrate in that
direction.

The internal domain.net is the same name as an external domain -
domain.net which is not owned by us.

Some of the machines in both trusted domains are resolving the domain
and server.domain.net to this external address.

the previous administrator was very cavalier and shrugged his
shoulders and explained they always sorted it with host files.

Is there a way in DNS to totally block the resolution to this external
domain, as i really dont like the thought of host files.
And how do we remove this external record from our DNS?

cheers

Phil- Hide quoted text -

- Show quoted text -

I have added the domain.net DNS as a secondary on the domain.internal
and vice versa, and yes it is authoritative.
Sometimes it works, sometimes it fails.The only way to get this to
resolve correctly is to flush the local dns, or to try 4 or 5 times,
which would implies to me that our DNS has a cache of this external
domain.
I have added a second DNS suffix to the workstations which has helped
in some cases, but it still fails on the first or second lookup.
How do i check where this is cached in DNS, if it is, then how do i
superscede or remove it?

phil
.

Relevant Pages

  • RE: Third domain controller
    ... "James Yeomans BSc, MCSE" wrote: ... running dcpromo i should point the dns to one of the other dns servers that ...
    (microsoft.public.windows.server.dns)
  • Re: Need Help from DNS Expert on Subdomain DNS Records
    ... When you use nslookup to resolve these names do you get the correct internal ... domain from within and outside our firewall. ... public IP to point to the same private IP, ... You need to verify that the all DNS servers assigned to a the DNS Client be ...
    (microsoft.public.windows.server.dns)
  • 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)
  • 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: NS and domain A record affecting AD
    ... Clients are pointing to the local dc for both WINS and DNS, ... If the remote dc's are on a slow link you may not even get your gpo's ... If local clients can not resolve AD domain name to ...
    (microsoft.public.windows.server.active_directory)