Newbie: DNS Setup in Two Locations

  • Thread starter Thread starter Kris
  • Start date Start date
Enkidu,
After applying DNS entry of Server A into Server B BINGO!!!! I was able to
pass thru' Network Credentials window.
I was wondering what type of config will this be:
In ServerA --- put DNS entry of Server B
In ServerB --- put DNS entry of Server A
Do I need forwarders (DNS Mgmt) then?

Thanks
Kris
 
Kris said:
Enkidu,
After applying DNS entry of Server A into Server B BINGO!!!!
I was able to pass thru' Network Credentials window.
I was wondering what type of config will this be:
In ServerA --- put DNS entry of Server B
In ServerB --- put DNS entry of Server A
Do I need forwarders (DNS Mgmt) then?
Click to expand...
I guess you mean into the NIC DNSes. Glad it worked.

In order to decide what to define where, consider what is
going to happen a) when it is working and b) when one of the
DNS servers fails or goes down. If both servers are working
the clients can look up the necessary information and
register themselves in DNS in either of them, which then
propogate the information. It is therefore useful to have
them both defined in each client, but it doesn't matter in
which order.

A DNS server is also a DNS client, and therefore should have
both. When Server A comes up it might be beneficial if it
could do its login etc with the other DNS since its own DNS
may not be fully functional at that stage. Therefore it
might be best to put the other server *first* in the
server's NIC definitions. Same for the other server, as a
client.

As far as forwarders goes, they are used to forward request
to an external DNS for Internet access. If you want your
clients to access Internet sites, then you will need to
configure forwarders to point to some Internet DNS.
Alternatively you can let the DNS use 'root hints' to
recursively look up Internet addresses.

Cheers,

Cliff
 
Cliff,
Are you saying I never have to configure anything under forwarders as well
as reverse lookup section in DNS Console (unless Inet lookups)? It should be
blank? Everything (local) gets resolved via DNS services (nic's having dns
ip numbers)?
Thanks
Kris
 
Also I'm getting error Event ID: 7062
The DNS Server encountered a packet addressed to itself -- IP address
192.168.xxx.xxx(my dns server ip address).
Please help.
 
In
Kris said:
Also I'm getting error Event ID: 7062
The DNS Server encountered a packet addressed to itself -- IP address
192.168.xxx.xxx(my dns server ip address).
Please help.
Click to expand...

A forwarder will normally eliminate that error. It can also be due to a
delegation misonfiguration or the domain controller is multihomed.

Here's more info on it:
http://www.eventid.net/display.asp?eventid=7062&eventno=479&source=DNS&phase=1

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services
Infinite Diversities in Infinite Combinations.
=================================
 
Ace,
Its not multihomed.
I found one suggestion in google search to put a check for Disable Recursion
under Advaced Tab of Server properties.
I have no more messages of it.
Thanks
Kris
 
In
Kris said:
Ace,
Its not multihomed.
I found one suggestion in google search to put a check for Disable
Recursion under Advaced Tab of Server properties.
I have no more messages of it.
Thanks
Kris
Click to expand...

Disable recursion under the adv tab eliminates it from allowing anyone else
to use this machine as a forwader, but also stops it from looking elsewhere.

If you reenabled recursion and confgured a forwarder, does it work? In my
experience, a forwarder eliminates that error.

Ace
 
Back
Top