Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

Redirect to Captive Portal does not work to internal dns-records

This thread has been viewed 12 times

  • 1.  Redirect to Captive Portal does not work to internal dns-records

    Posted Nov 28, 2012 04:57 AM

    Hello!


    Our baseimage has the address to our intranet as the default homepage.

    When I try to connect to our open network with captive portal, it tries to go to http://intranet but it does not get redirected, instead the browser says that the page could not be displayed. But if I try to search for example google.com, it does get redirected to the captive portal.

    Is there any way to solve this issue?

     

    Thanks,

    Johan

     



  • 2.  RE: Redirect to Captive Portal does not work to internal dns-records

    EMPLOYEE
    Posted Nov 28, 2012 07:37 AM

    Are you using an internal DNS server?

     



  • 3.  RE: Redirect to Captive Portal does not work to internal dns-records

    Posted Nov 28, 2012 08:05 AM

    Yes. I do use an internal DNS server.



  • 4.  RE: Redirect to Captive Portal does not work to internal dns-records

    EMPLOYEE
    Posted Nov 28, 2012 08:13 AM

    Can you do an nslookup for "internal" from that client?  Does it resolve?

     



  • 5.  RE: Redirect to Captive Portal does not work to internal dns-records

    Posted Nov 28, 2012 09:28 AM
    @cjoseph wrote:

    Can you do an nslookup for "internal" from that client?  Does it resolve?

     

    Nope. We got one prod-DNS and one guest-DNS.

    In the prod we do have the intranet-record, but not in the guest-DNS that we use on the captive portal vlan.



  • 6.  RE: Redirect to Captive Portal does not work to internal dns-records

    EMPLOYEE
    Posted Nov 28, 2012 09:31 AM
    Being able to resolve DNS before bringing up a webpage is required for Captive Portal to work. If it cannot resolve, that Captive Portal will not be displayed.


  • 7.  RE: Redirect to Captive Portal does not work to internal dns-records

    Posted Nov 28, 2012 09:45 AM

    If I put the intranet-address into the guest-DNS it will be okey? Eventho if that VLAN cant reach the webpage?



  • 8.  RE: Redirect to Captive Portal does not work to internal dns-records

    Posted Nov 28, 2012 09:49 AM

    Hmm, it was not so simple... Any suggestions to get around this problem?



  • 9.  RE: Redirect to Captive Portal does not work to internal dns-records

    EMPLOYEE
    Posted Nov 28, 2012 09:51 AM
    Do guests need to reach the intranet?


  • 10.  RE: Redirect to Captive Portal does not work to internal dns-records

    Posted Nov 28, 2012 10:10 AM
    @cjoseph wrote:
    Do guests need to reach the intranet?

    No. And i dont want to.

     

    I just tried to put up a fake address to intranet, but it still display "could not display".



  • 11.  RE: Redirect to Captive Portal does not work to internal dns-records

    Posted Nov 28, 2012 10:42 AM

    The issue ends up being related to not automagically appending the dns suffix.  If the browser homepage was bookmarked as http://internal.domain.com this would work.  However as noted, http://internal is not a valid DNS response ans would never make it to they hooked.  Many times the browser can complicate this more.



  • 12.  RE: Redirect to Captive Portal does not work to internal dns-records

    Posted Nov 29, 2012 06:15 AM
    @DougR wrote:

    The issue ends up being related to not automagically appending the dns suffix.  If the browser homepage was bookmarked as http://internal.domain.com this would work.  However as noted, http://internal is not a valid DNS response ans would never make it to they hooked.  Many times the browser can complicate this more.

    Hey DougR

     

    The homepage is bookmarked as http://intranet.domain.com not http://intranet in the internet browser.

    And I made a new zone in the DNS, domain.com, and a a-record there that points to "intranet" and ip: 0.0.0.0

     



  • 13.  RE: Redirect to Captive Portal does not work to internal dns-records

    EMPLOYEE
    Posted Nov 29, 2012 06:33 AM

    If you are using a public DNS server, you will not be able to resolve any addresses for domains that you do not have control over globally.  If you are using a private DNS server, you can make this happen.



  • 14.  RE: Redirect to Captive Portal does not work to internal dns-records

    Posted Nov 29, 2012 09:27 AM
    @cjoseph wrote:

    If you are using a public DNS server, you will not be able to resolve any addresses for domains that you do not have control over globally.  If you are using a private DNS server, you can make this happen.

    I do have an private DNS server. And I have added "intranet" to domain.com.

    But the redirect still not work, and I have successfully resolved intranet, with the command nslookup intranet.domain.com.

     



  • 15.  RE: Redirect to Captive Portal does not work to internal dns-records

    EMPLOYEE
    Posted Nov 29, 2012 09:36 AM

    Is the DHCP server providing the suffix "domain.com" to all of its clients?

     



  • 16.  RE: Redirect to Captive Portal does not work to internal dns-records

    Posted Nov 29, 2012 10:04 AM
    @cjoseph wrote:

    Is the DHCP server providing the suffix "domain.com" to all of its clients?

     


    No, is that really nessisary if the default homepage is bookmarked as http://intranet.domain.com ? when i run a nslookup it successfully resolve the address.

     

    But I till try it.



  • 17.  RE: Redirect to Captive Portal does not work to internal dns-records

    EMPLOYEE
    Posted Nov 29, 2012 10:09 AM
    Nslookup sends a raw DNS lookup. Entering a URL in a browser will add the dhcp domain suffix if none is provided.


  • 18.  RE: Redirect to Captive Portal does not work to internal dns-records

    Posted Nov 29, 2012 10:18 AM
    @cjoseph wrote:
    Nslookup sends a raw DNS lookup. Entering a URL in a browser will add the dhcp domain suffix if none is provided.

    Yes I know. And the URL is http://intranet.domain.com in the browser :) So there should be no need to add an additional dhcp domain suffix, i guess?



  • 19.  RE: Redirect to Captive Portal does not work to internal dns-records
    Best Answer

    EMPLOYEE
    Posted Nov 29, 2012 10:30 AM
    Put the IP address 1.1.1.1 into the browser. If the captive portal comes up, DNS resolution is your problem, period.


  • 20.  RE: Redirect to Captive Portal does not work to internal dns-records

    Posted Nov 29, 2012 11:02 AM
    @cjoseph wrote:
    Put the IP address 1.1.1.1 into the browser. If the captive portal comes up, DNS resolution is your problem, period.


    I understood that it was a dns resolution problem, but did not know how to solve it.

    But i changed the a-record from 0.0.0.0 to something random. After that it redirected. 

    Thanks alot cjoseph, you are awsome! There is a few forums with helpfull gurus like you.. :)

     

    Best regards,

    Johan