Forum Discussion
BPetronio_11363
Nimbostratus
NimbostratusLinkController and DNS
Hi all,
Nowadays i have a scenario with 1 link to a client, and 1 External DNS Server which resolve all my domains / zones.
For secondary DNS Server, i have a leased ISP Secondary DNS Server.
When my DNS Server goes down, all the Name Resolutions to my domains/zones are given by this Secondary Server.
When i install my Link Controller, first i was thinking to mantain this structure, and create a VIP for DNS Server, and on the DNS Server, i was delegating zones to my F5. (Listener IP Address = Floating Self IP Address)
In lab i created an inbound wide ip with a given url with 2 Virtual Servers, each one from diferent ISPs range.
That's working fine.
But when the link that is supporting DNS VIP address is broken, i lose all the conectivity to my DNS, and then there is no name resolution, in my DataCenter, and only the ISP DNS will responde, but then will responde with the same ip's from the link is down.
Can i simple "register" the Secondary and Terceary DNS Server, to an ip from each ISP Link from the LC and assign it as listeners?
Anyone already test this type of config ?
The point is that if the Link that supports my Vip DNS Server is down, then, ther is no redundancy/balancing of inbound traffic since there is no response to DNS queries.
Best Regards,
Bruno Petrónio
- Chris_Miller
Altostratus
When your link goes down, LinkController automatically disables any VSes associated to that link. I don't understand why you're trying to load balance your DNS servers...why not just have both DNS servers delegating zones to the F5 gear and leave it at that? 
BPetronio_11363Cript,
Im not trying to balance my DNS Servers (i only have the primary in my DC, and the Secondary is not mine).
My question was if anyone had done something similar, registring Sencondary/Terceary DNS servers with the corresponding IP for DNS_VS for the Real DNS Server.
Best Regards,
Bruno
