Forwarders listing

  • Thread starter Thread starter KJ
  • Start date Start date
K

KJ

Can you use an internal DNS server and use forwarders to
external DNS server AND an internal DNS server? Will it
get feedback from both or will it stop when it gets answer
from 1st one listed? Say you list 65.65.65.23 and
10.23.2.2 in the forwarders tab, will it try both
depending on where the query needs to go?
 
No, it tries only one. It will only try another if it receives no response
from one.

--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
www.akomolafe.com
www.iyaburo.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
 
KJ said:
Can you use an internal DNS server and use forwarders to
external DNS server AND an internal DNS server? Will it
get feedback from both or will it stop when it gets answer
from 1st one listed? Say you list 65.65.65.23 and
10.23.2.2 in the forwarders tab, will it try both
depending on where the query needs to go?

IT's not recommended to forward between internal DNS servers if they host
the same zone name since it'll cause a forwarding loop. If forwarding to an
internal machine that is hosting public records, and that's forwarding to
the ISP, then that would be fine.

At the same token, if you mix forwarders, internal and external, it will
stop as soon as it gets an answer. It's not a load balancing mechanism, but
rather a fault tolerant mechanism for fail-over, so whatever forwarders you
list need to have the same data, so if public, then both need to be public.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
That is not good. Why doesn't Microsoft build this into
the forwarder capability then? I now would have situation
where I would have to pull records internally to zone
file.

How about, can I have to DNS servers and one forward to
internal and the other to external and use AD integrated?
Is there a way to make this work and keep both servers in
sync and know about the ext. and int. zones?
 
With W2k3 you can use conditional forwarding to forward only for a specific
domain/zone.

What are you trying to work out? Maybe if you can give us an example, one of
us can come up with a solution.

Ace


That is not good. Why doesn't Microsoft build this into
the forwarder capability then? I now would have situation
where I would have to pull records internally to zone
file.

How about, can I have to DNS servers and one forward to
internal and the other to external and use AD integrated?
Is there a way to make this work and keep both servers in
sync and know about the ext. and int. zones?
 
An external domain needs to be moved internal, the
external is a child domain but want to keep same name and
move internal and forward to external parent. There are
multiple internal domains including children of parent.
Need to know of servers that are part of these other
internal domains. So, instead of pulling an internal
domain zone, would like to forward for extraction of
records to be able to see these without using the parent's
child:

joke.com is parent
new.joke.com is child
joke.com creates int.joke.com
Don't want to give up DNS set up for new.joke.com but
would like to forward to joke.com and int.joke.com
 
KJ said:
An external domain needs to be moved internal, the
external is a child domain but want to keep same name and
move internal and forward to external parent. There are
multiple internal domains including children of parent.
Need to know of servers that are part of these other
internal domains. So, instead of pulling an internal
domain zone, would like to forward for extraction of
records to be able to see these without using the parent's
child:

joke.com is parent
new.joke.com is child
joke.com creates int.joke.com
Don't want to give up DNS set up for new.joke.com but
would like to forward to joke.com and int.joke.com

If I understand what's going on here, it sounds like a delegation is your
better bet. You can delegate the child zone from the parent DNS to the
child's DNS. Then from the child's DNS you can forward to the parent/ From
the parent, forward externally to your ISP.

Here's some info and steps on delegation:
255248 - HOW TO Create a Child Domain in Active Directory and Delegate the
DNS Namespace to the Child Domain:
http://support.microsoft.com/?id=255248

(Delegation and Forwarding) - Directing queries through forwarders and
delegation:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechn
ol/windowsserver2003/proddocs/standard/sag_DNS_imp_DirectingQueriesThroughFo
rwarders.asp


I hope I understood what you're trying to do, if not, I apologize.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top