Joining ISE to a Reversed DNS Zone

[Jason2005]

I have joined ISE on the same reversed zone as 50.168.192.in-addr.arpa (ise1.srvcore.local), but ISE have an address of 192.168.99.35.

ISE could resolve and ping DNS domaine names on Windows Server and could PING its name "ise1.srvcore.local" and can PING "srvcore.local", and can NSLOOKUP "srvcore.local" but cannot NSLOOKUP "ise1.srvcore.local".

====> Is it OK to join a node having an address of 192.168.99.35/24 in the reversed zone of 50.168.192.in-addr.arpa ?

====> Could that ever cause any issues ?

Cisco Catalyst Center VA for ESXi FAQ 

ISE MnT Log sizing calculator for TACACS+ and RADIUS 

ISE 3.2p3 - Enabling SSO for Admins... access denied error 

ISE Intune Dynamic VLAN segmentation 

[Aref Alsouqi]

Personally I never tried it myself, but I'm wondering why you would want to do that rather than having ISE in the correct DNS zone?

[Jason2005]

Cause it would require adding an additional DNS Zone with the ip address of 192.168.99.0/24 in addition to 192.168.50.0/24 Zone.

Any suggestions ?

[Aref Alsouqi]

To help me wrapping my head around it, could you please share a use case of this?

[thomas]

@Jason2005 , Why are you linking to these other unrelated community articles and documents?

[thomas]

@Jason2005 , Why are you linking to these other unrelated community articles and documents?