Wireless Access

last person joined: 23 hours ago 

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

DNS not working from controller CLI

This thread has been viewed 16 times
  • 1.  DNS not working from controller CLI

    Posted Feb 10, 2017 09:31 AM

    I have a pair of 7220 controllers that are performing local controller functions at a large campus.  Both controllers are configured with name servers and have ip domain lookup enabled.  They also both have the same default route.  However, the secondary controller can resolve DNS correctly (tested via the ping www.cnn.com command) but the primary controller cannot.  When testing using the ping command and a name, I get the following response:

    #ping www.cnn.com
    Incorrect input! Use 'ping <target-ip-address>'

     

    Any ideas on how to get DNS working?  This is preventing our BLE beacons from talking through the controller correctly.  Thank you.



  • 2.  RE: DNS not working from controller CLI

    EMPLOYEE
    Posted Feb 10, 2017 09:36 AM

    What version of ArubaOS is this?

     

    How are the beacons involved?



  • 3.  RE: DNS not working from controller CLI

    Posted Feb 10, 2017 09:38 AM

    This is 6.4.4.2.

    The beacons have a URL in the system profile that currently isn't resolvable as DNS isn't functioning (not as far as I can tell).  In Meridian, I can see the beacons only talk to MEridian through my beacons app, not through the controller.



  • 4.  RE: DNS not working from controller CLI

    EMPLOYEE
    Posted Feb 10, 2017 09:50 AM

    ip domain lookup could require a controller reboot:

     

    (Aruba7005-US) #configure t
    Enter Configuration commands, one per line. End with CNTL/Z
    
    (Aruba7640-US) (config) #ip domain?     
    domain                  IP DNS Resolver
    domain-name             Define the default domain name
    
    (Aruba7640-US) (config) #ip domain ?
    lookup                  Enable IP Domain Name System hostname translation 
                            for clients
    
    (Aruba7640-US) (config) #ip domain lookup 
    Operation may not take effect until a reboot
    
    

     

     



  • 5.  RE: DNS not working from controller CLI

    Posted Feb 10, 2017 10:22 AM

    I will try and reboot off hours to see if this resolves.  However, both controllers were configured with the same settings (name-servers and ip domain lookup) and neither were rebooted, yet the secondary resolves successfully and the primary doesn't.  

     

    Again, will reboot and let you know.



  • 6.  RE: DNS not working from controller CLI

    Posted Apr 08, 2019 06:17 AM

    How to configure A record of clearpass hostname in controller ?

    The main target is to resolve URLs from external DNS like 8.8.8.8 and enable guests to access CPPM Captive portal page (private ip), don't want to allow guests access internal DNS for security concerns.