wideip
3 TopicsDeliver different ips having the same dns zone name but in different views
Good morning gentlemen. I have an interesting case to be solved, the scenario is: I have 2 listening and I have two views, one internal and one external, however the name of the zones are the same, for example xpto.com.br, I need that when a request is made to test.xpto.com.br to listening 1 ( 10.10.10.10) it delivers the ip of the internal view, and when a request is made to listening 2 (20.20.20.20) it delivers the ip of the external view. thanks for all the help in advance.1.1KViews0likes7CommentsiRule to drop Public IP access to DNS Wide-ip
We have wide-ip "abc01.example.com" which we want only to access from internal user (private ip) Do we have iRule to drop only public ip and allow private ip on that wide-ip? So when nslookup to "abc01.example.com" via public ip, F5 drop and when nslookup to "abc01.example.com" via private ip, F5 allow Thank you672Views0likes3CommentsView zone bigip dns manipulation
I have a bigip dns configured with 1 listening ip (I can have 2 if necessary), inside the bigip dns I have 2 views, one INTERNAL and the other INTRANET, in each view I have the same zones but with different ips, example: INTERNAL xpto zone. com.br entry type A 123.xpto.com.br ip 192.168.10.10, and in the INTRANET zone xpto.com.br entry type A 123.xpto.com.br ip 10.20.10.10. All my clients arrive here at some address in the 10.0.0.0/8 range. I need to find a way that when customers make a request I can direct them to a specific view, in this case INTRANET or INTERNAL. Another alternative that seems easier is to have 2 listening and each one responds through a view, but how to do that? It seems to me that when listening is consulted, it resolves by taking the priority view and if it does not find it, it goes on to the others if they exist, but in this case, as the zones are the same, they will always exist and I will never be able to deliver different ips as I want. Anyone any light?499Views1like2Comments