Link to home
Start Free TrialLog in
Avatar of BetfairRomania
BetfairRomania

asked on

Microsoft DNS Delegation Zone

Hi,
I have to Active Directory domains which are called:
domain1.local with 2 DNS servers dns11.domain1.local and dns12.domain1.local
and
domain2.local with 2 DNS servers dns21.domain2.local and dns22.domain2.local
I create in dns11.domain1.local a zone called domain2.local. On this new zone I create a new delegation which is pointing to dns21.domain2.local and dns22.domain2.local.
When I am using my client computer to ping machines from domain2.local those are not answering.
Mu delegation is not working, can you please help me with this.
Thank you.
Avatar of Chris Dent
Chris Dent
Flag of United Kingdom of Great Britain and Northern Ireland image


> On this new zone I create a new delegation

Do you created something like sub.domain2.local in there?

From the sound of it you don't want to be using a Delegation here. You want to resolve names in domain2.local? Instead you want to use any of...

1. Conditional Forwarder
2. Stub Zone
3. Secondary Zone

Which is most appropriate depends a bit on the DNS server. Most are capable of 1, but Windows 2000 isn't.

Chris
Avatar of BetfairRomania
BetfairRomania

ASKER

Hi,
thank you for your answer.
What I really need is from my client computer when I run this commands ping -a 192.168.180.23 and this ping server1.domain2.local I need this machine called server1.domain2.local to respond.
I create in dns11.domain1.local a reverse lookup zone for 180.168.192 and also in this DNS server I create a forward lookup zone called domain2.local which i delegated to dns21.domain2.local.
Thank you.

> ping -a 192.168.180.23

This is an entirely different matter. Ping -a attempts to resolve a name from the given IP address. That requires Reverse Lookup not Forward. Where is the Reverse Lookup Zone?

When you run "ping server1.domain2.local" the DNS server your client uses will need a way to find the records in domain2.local. This one comes to the next bit.

> delegated to dns21.domain2.local

Zones can only be delegated from a parent zone. To delegate domain2.local you would have to have a zone called "local.".

You cannot Delegate this and expect to be able to resolve names. You must use one of the three options I quoted above.

Chris
Hi,

> domain1.local
dns11.domain1.local and dns12.domain1.local

>domain2.local
dns21.domain1.local and dns22.domain2.local

What I need is:
> when you ping server1.domain2.local = 192.186.180.23
> when you ping -a 192.168.180.23 = server1.domain2.local

What I have done:
>in dns11.domain1.local and dns12.domain1.local I create a reverse lookup zone called 180.168.192
>in dns11.domain1.local and dns12.domain1.local I create a forward lookup zone colled domain2.local and from new delegation wizard I select dns21.domain2.local and dns22.domain2.local
>I create a new PTR record entry as 23  in reverse lookup zone called 180.168.192

Thank you.
ASKER CERTIFIED SOLUTION
Avatar of Chris Dent
Chris Dent
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
HI,
in this way reverse is working only for DNS machine domain2.local (dns21 and dns22).
How can I make it  work  for all machine from domain2.local domain
Thank you.

Do both domains share the same IP range?

Are you wanting them to use Dynamic Updates to add themselves to the zone?

You might create a Secondary zone for the Reverse Lookup on the DNS servers in domain2.local.

Chris
Hi,
on both DNS servers from domain2.local I have a reverse lookup zone for all machines served by those DNS servers.
No this domains are using diffren IP range.
Thank you.