Cisco WLC and Cloudflare

[NelsonGuedes]

Hi,

Anyone have problems with WLC captive portal, after 1.1.1.1 Cloudflare dns have been launch?

I have 1.1.1.1 as my virtual web portal, and after the relase from cloudflare 1.1.1.1 dns, my captive portal stop to redirect after accept disclaimer.

Anyone have a similar problem?

[Scott Fella]

Nelson,

I think many others have moved away from using 1.1.1.1 a while ago to be honest. If your DNS is internal then it should be fine. I’m also assuming that you have installed a certificate to resolve the dns name to 1.1.1.1?

[NelsonGuedes]

Hello @Scott Fella,

This is for guest only, so the DNS is public.

Regarding the certificate, yes I have it for 1.1.1.1

Tonight i will change the address 1.1.1.1, to see if it solve the problem.

This just happen today, which is strange, since CloudFlare launch yesterday the new 1.1.1.1 public dns.

[Scott Fella]

When I have used a public DNS, I typically will use on of the public ip for the virtual and then have an a-record with the hostname to resolve to the public/VIP ip. That should work for you. You will need to reboot the controller for the VIP to take as it will prompt you for that.

[NelsonGuedes]

Ok. I will try that. However i need to generate on WLC a new certificate for that VIP right?
I will do it tonight and i will reply tomorrow with na update.