Re: Phantom FQDN resolution
- From: "Paul Bergson [MVP-DS]" <pbergson@xxxxxxxxxxxxxxxxx>
- Date: Wed, 28 Mar 2007 07:42:21 -0500
Have you checked the AD specific zones, such as _msdcs, for any references
to these former trust partners.
--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.
"Todd Jenkins" <ToddJenkins@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7706BAE9-4903-49C6-B205-EAE758800056@xxxxxxxxxxxxxxxx
Hi,
I have a problem with FQDN resolution. The problem is not in DNS.
Scenario: 3 forests, each with their own DNS servers. A trust setup
between
(A to B) (A to C) (B to C) . They WERE sharing a common resource
(Exchange
2003). Now each forest has their own Exchange server and the need for the
trusts has gone. The trusts have been removed as has the physical
connectivity between the forests. If I ping the IP address of a DC in
forest
C from forest A or B, there is no response as expected. But, if I do a
ping
-a on the same foreign DC, I get a FQDN resolution followed by the ping
timeout. I want to remove the references to the foreign DC's. I have
looked
in each DNS server and the domain does not exist. I have looked in hosts
and
lmhost and the domain does not exist. I can get the FQDN for the DC from
any
machine in forest A and B. It's my guess that AD is keeping the
references
to the foreign DC's.
Thanks for the help
Todd
.
- References:
- Phantom FQDN resolution
- From: Todd Jenkins
- Phantom FQDN resolution
- Prev by Date: Re: Installing a new Domanin Controller
- Next by Date: Re: Child Domain Login Issue
- Previous by thread: Phantom FQDN resolution
- Next by thread: Re: Phantom FQDN resolution
- Index(es):
Relevant Pages
|
