Re: Internal domain resolving to external domain not owned by us
- From: James Yeomans BSc, MCSE <JamesYeomansBScMCSE@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 4 Nov 2008 07:38:01 -0800
do any of the dns servers have forwarders configured? Try running nslookup
against the different dns servers to see the responses they return. That way
you can prove whether or not each individual server is functioning corerctly
and pin it down to 1 or 2 that are not. For nslookup informatin look here:
http://support.microsoft.com/kb/200525
James.
--
James Yeomans, BSc, MCSE
Ask me directly at: http://www.justaskjames.co.uk
"durx" wrote:
On 4 Nov, 14:01, James Yeomans BSc, MCSE.
<JamesYeomansBScM...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Anything your dns server keeps in its cache should only lat for 20 minutes
before it expires. You can run ipconfig /flushdns to clear the cache on
servers or workstations.
There's no real reason why the query should fail the first 2 times and then
resolve correctly, if a client queries a dns server and the server is
authoritative for that zone it will answer the query or tell you the record
doesn't exist. Are your clients definitely configured with the correct dns
servers?
James.
--
James Yeomans, BSc, MCSE
Ask me directly at:http://www.justaskjames.co.uk
"durx" wrote:
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- Hide quoted text -
- Show quoted text -
James,
My DNS is as follows;
Pri is domain.internal - local DNS server
Sec is domain.internal - local DNS server
third Pri is domain.net- local DNS server
all above DNS servers are local to site on same ip range and carry
secondary zones of their opposite DNS.
cheers
phil
- References:
- Internal domain resolving to external domain not owned by us
- From: durx
- RE: Internal domain resolving to external domain not owned by us
- From: James Yeomans BSc, MCSE
- Re: Internal domain resolving to external domain not owned by us
- From: durx
- Re: Internal domain resolving to external domain not owned by us
- From: James Yeomans BSc, MCSE
- Re: Internal domain resolving to external domain not owned by us
- From: durx
- Internal domain resolving to external domain not owned by us
- Prev by Date: Re: Internal domain resolving to external domain not owned by us
- Next by Date: RE: Strange Irregular DNS/Networking Problems
- Previous by thread: Re: Internal domain resolving to external domain not owned by us
- Index(es):
Relevant Pages
|
