On 09/01/2011 11:53 PM, Vbvbrj wrote:
On 01.09.2011 19:01, CT wrote:
so did you end up setting up a slave zone (for the internal AD DNS)
on your public DNS server ?
No, for now I just left the AD DNS (Microsoft DNS) instead of BIND. I
didn't have time to move all DNS servers to BIND and make
On 01.09.2011 19:01, CT wrote:
so did you end up setting up a slave zone (for the internal AD DNS) on
your public DNS server ?
No, for now I just left the AD DNS (Microsoft DNS) instead of BIND. I
didn't have time to move all DNS servers to BIND and make them
primary/slave for locale zone.
_
On 09/01/2011 07:59 AM, Vbvbrj wrote:
I had the same question a while ago. Using bind with forward only to an
AD DNS will get to errors for infrastructure, because of BIND caching
unable to disable for this forwarded zone. Also BIND does not redirect
all updates queries to AD DNS, while in an AD
I had the same question a while ago. Using bind with forward only to an
AD DNS will get to errors for infrastructure, because of BIND caching
unable to disable for this forwarded zone. Also BIND does not redirect
all updates queries to AD DNS, while in an AD environment updates are
made very often
Hello,
Do add "forward only;" to this zone statement.
Is this name server available/visible to the Internet ?
--> add "allow-query" statement to limit who can query for your internal
zone.
Kind regards,
Marc Lampo
Security Officer
EURid
-Original Message-
From: CT [mailto:gro...@
Hello,
Do add "forward only;" to this zone statement.
Is this name server available/visible to the Internet ?
--> add "allow-query" statement to limit who can query for your internal
zone.
Kind regards,
Marc Lampo
Security Officer
EURid
-Original Message-
From: CT [mailto:gro...@obsd
6 matches
Mail list logo