locked
AD Integrating conditional DNS forwarders stops them working RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have a conditional forwarder set up in Domain A to go to the DNS servers for Domain B.  This works fine as standard conditional forwarders, but if I change them to AD integrated they stop working!  I then have to remove the conditional forwarders and configure as standard again.  If I just remove the check from the 'Store this conditional forwarder in Active Directory and replicate it as follows:' box it doesn't return to working, I need to completely remove the conditional forwarders and recreate from scratch.

    Has anyone else seen this and know how to resolve?

    Wednesday, December 3, 2014 10:09 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi FugratUK123,

    According to your description, in my opinion, the conditional forwarder doesn’t work means that clients in domain A can’t resolve names of domain B.

    Due to the conditional forwarder works fine when it was configured without AD integrated. Please check the AD replication at first. When you configured conditional forwarder as AD integrated, can you see the conditional forwarder in DNS servers of other DCs?

    If you changed it to AD integrated by editing properties of the existing conditional forwarder.

    Please also try to delete the previous standard conditional forwarder. Then create a new conditional forwarder with checking that option. To see if it can work properly.

    You can use repadmin /showrepl command to verify if the AD replication has any problems.

    In addition, you could also use dcdiag /test:dns command to perform DNS test.

    For more details, please refer to articles below,

    Repadmin /showrepl

    http://technet.microsoft.com/en-us/library/cc742066.aspx

    Best Regards,

    Tina

    • Proposed as answer by Tina_Tan Thursday, December 11, 2014 2:51 AM
    • Marked as answer by FugratUK123 Thursday, December 11, 2014 9:37 AM
    Thursday, December 4, 2014 9:51 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi FugratUK123,

    According to your description, in my opinion, the conditional forwarder doesn’t work means that clients in domain A can’t resolve names of domain B.

    Due to the conditional forwarder works fine when it was configured without AD integrated. Please check the AD replication at first. When you configured conditional forwarder as AD integrated, can you see the conditional forwarder in DNS servers of other DCs?

    If you changed it to AD integrated by editing properties of the existing conditional forwarder.

    Please also try to delete the previous standard conditional forwarder. Then create a new conditional forwarder with checking that option. To see if it can work properly.

    You can use repadmin /showrepl command to verify if the AD replication has any problems.

    In addition, you could also use dcdiag /test:dns command to perform DNS test.

    For more details, please refer to articles below,

    Repadmin /showrepl

    http://technet.microsoft.com/en-us/library/cc742066.aspx

    Best Regards,

    Tina

    • Proposed as answer by Tina_Tan Thursday, December 11, 2014 2:51 AM
    • Marked as answer by FugratUK123 Thursday, December 11, 2014 9:37 AM
    Thursday, December 4, 2014 9:51 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi all

    I got this sorted, unsure why it didn't work through the GUI but I added the zone using dnscmd with

    Dnscmd /zoneadd <zone name> /dsforwarder <Server 1 IP> <Server 2 IP> /dp /forest

    and it works ok

    Thanks

    Thursday, December 11, 2014 9:47 AM