Re: Netbios name resolves to "wrong domain"

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Sweet link. Yes we do have WINS. The parent domain has a stub zone for each
child domain and each domain DNS is replicating within the domain. I just
don't understand how a client can query for server1.domain1.root.com, whose
real name is server1.domain2.root.com, and get a valid IP back. I would
think it would timeout as there's no A record for server1.domain2.root.com in
domain1.root.com.

"Todd J Heron" wrote:

> First of all, do you have WINS?
>
> Without WINS, and you query by the flat, non-FQDN name, then the client's
> domain name gets automatically appended to the query and the preferred DNS
> server listed in client's IP properties looks in the zone of "domain name"
> for that host. Are you following me?
>
> When you have multiple domains, it gets a little more complicated. You said
> you are forwarding from the child to the parent root domain, but in the
> parent domain, how does it know how to reach all the other child domains?
> Delegation zones? Stub zones? Conditional Forwarding? Secondary Zones?
> For each domain in the enterprise, are you replicating ADI to all DCs in the
> domain, all DNS servers in the domain, or to all DNS servers in the forest?
>
> Have a read here.
>
> DNS Suffix Struggle:
> http://mcpmag.com/columns/article.asp?editorialsid=1109#post
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> ----------------------------------------------------------------------------
> This posting is provided "as is" with no warranties and confers no rights
>
> "Tynman" <Tynman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:69DDAE7E-DD98-498C-93D3-A16D97C522F3@xxxxxxxxxxxxxxxx
> Question, how does that work? A client tries to query a hostname only, so
> the client takes the first name in the search order, of course, and then
> forwards the query to it's first DNS server. I'm just confused at why the
> DNS server would return a FQDN that doesn't exist.
>
> "Todd J Heron" wrote:
>
> > You've got a DNS Suffix Search Order problem. On the client machine
> > pinging
> > the wrong name, adjust this order accordingly, and your problem should be
> > solved. Try putting domain1.root.com at the top of this list.
> >
> > --
> > Todd J Heron, MCSE
> > Windows Server 2003/2000/NT; CCA
> > ----------------------------------------------------------------------------
> > This posting is provided "as is" with no warranties and confers no rights
> >
> > "Tynman" <Tynman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:9959BA76-29B1-438B-B31C-57DFF67EA243@xxxxxxxxxxxxxxxx
> > Have a strange issues here: When I ping a client by host name it resolves
> > to
> > the correct IP addres; however, it attaches the incorrect domain name.
> > For
> > example: The actual member server name is server1.domain1.root.com, but
> > it's
> > resolving to server1.domain2.root.com and server1.domain3.root.com and
> > server1.domain4.root.com. When I look in the cache I can see the correct
> > hostname with the incorrect domain name and it's in the incorrect domain.
> > I've checked the domains that it's resolving to to make sure there's not a
> > host record there and there's not.
> >
> > Our current setup is a root domain with 8 child domains. The server that
> > I'm trying to resolve is in one of the child domians. All child DNS
> > servers
> > are pointing as forwarders to a DNS server in the root domain.
> >
> > Any ideas?
> >
> >
>
>
.



Relevant Pages

  • Re: DCDIAG DNS Failure
    ... so the sddcsrv03 is a DC and DNS server right? ... also describe your actual reverse ... and forward zones. ...
    (microsoft.public.windows.server.dns)
  • Re: DCDIAG DNS Failure
    ... so the sddcsrv03 is a DC and DNS server right? ... My Forward zones are as follows: ... Without advance view I have 4 forward lookup zones and 7 ...
    (microsoft.public.windows.server.dns)
  • Re: DNS Zone merge
    ... > I understand how to migrate over the DNS zones. ... >> hosting the transferred zones so DNS server on W2k machine would be ... If your child zones are being hosted by the child domain's respective DNS ...
    (microsoft.public.win2000.dns)
  • Re: DNS Recommendations w/ Active Directory & (2) DNS Servers
    ... DNS, and others stating better to use Second Server with Secondary ... while another post specifies that Stub Zones ... and the need for backup 2nd DNS server in the event our Primary Domain ... Unnecessary if you have no Secondaries -- these settings only affect ...
    (microsoft.public.windows.server.dns)
  • Re: Dcdiag errors before transfering existing DNS on Win 2K to Win 200
    ... I am in the middle of transfering existing DNS on Win2K DC to Win2003 ... forward and reverse lookup zones as secondary zones. ... the IP address is registered correctly with the DNS server. ... Running partition tests on: Configuration ...
    (microsoft.public.windows.server.dns)