Re: DNS QUERIES

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Omer maydan (omermaydan_at_yahoo.com)
Date: 08/09/04 

Date: Mon, 9 Aug 2004 19:24:42 +0200

by default, each new DC that you promote, an A record with the AD domain
name is created in DNS. also by default, a round robin is enabled on the dns
server, which means that every new query to this name should bring the next
A record of your domain name, meaning Server1 IP. anyway, it is normal
behaivor. look under your domain dns zone, you have some records with "Same
as Parent domain" name on them. this means your companydomainname. and you
have 2 or more records like this, and pointing to different IP address
Server1, and Server2. if it does note cause you any problems, just ignore
it. if you always get the same record, check that round robin is enabled on
the server properties. and on the query thing, the clients DO query they
predefined DNS servers. The fact that you get the domain FQDN record
resolved to another IP, does not mean that you don't query your intendent
DC\DNS server. 

-- 
Omer Maydan
MCSE, Security+
"collin camp" <collin@network-logic.com> wrote in message
news:2c6a01c47e2a$956ea880$a501280a@phx.gbl...
> having a little problem and hoping someone can help out.
> i recently added another windows 2003 server (call it
> server2 into the same domain /forest -same LAN for a
> total of 2 DCs.- example: server1 and server2
>
> note: both server have latest microsoft patches, server1
> has been up and running for 1 year now with out any
> problems.
>
> server1- 192.168.12.150
> server2 - 192.168.12.151
>
> the problem is that when pinging our domain name which is
> our company name, all clients (xp pro machines and even
> both servers are quering server2. Clients use to query
> server1 before adding this new server.
>
> i ran netdiag /fix on both servers and no errors
> nslookup see's each server/ ip as the default- no problem
> here.
>
> i checked network settings on both servers and each is
> pointing at themself in dns;  forwarders are pointing to
> ISP.
> Client PCs only point to server1 but yet are still
> quering server2 when i do a ping for the domain name.
>
> I turned off server2 for awhile for testing reason and
> users can still resolve dns and get web sites using
> server1 but queries to our domain is still quering the ip
> of server2.
>
> i even rebooted server1 but no help.
>
> SERVER1 has the FSMO role and the 2nd server will be just
> a peer domain conroller.
>
> any help would be greatly appreciated,
>
> collin

Relevant Pages

  • ACE/STEVE
    ... frssysvol ... DC Server1 is advertising itself as a DC and has DNS ... Failed cannot test for Host SPN ...
    (microsoft.public.win2000.dns)
  • Re: Cannot Add Second Node to Cluster: Multiple DNS records were found for "MyServer.MyNet.local"
    ... So now I think I only have one problem: the multiple DNS thing ... (not withstanding, the nightmare configuration). ... You should never cluster domain controllers. ... Server1 failed to register its IP info on the DNS in ...
    (microsoft.public.windows.server.clustering)
  • Disabling DNS Registration of 2nd NIC?
    ... Our PDC and primay DNS is a Windows 2003 server. ... NICs - 1 for our internal network, and the 2nd for a different, ... PDC Machine name: Server1 ...
    (microsoft.public.windows.server.dns)
  • Re: Os x intranet DNS issue?
    ... dempson@xxxxxxxxxxxxx (David Empson) wrote: ... The "server1" name is using a Windows-specific naming protocol (probably ... From then on, click the bookmark. ... With dynamic DNS or WINS a static IP isn't necessary. ...
    (comp.sys.mac.system)
  • Re: DNS QUERIES
    ... nothing to do with him resolving your domain name. ... > even though in dns settings they point to themselves. ... which means that every new query to this name ... >>A record of your domain name, meaning Server1 IP. ...
    (microsoft.public.windows.server.dns)