Security

last person joined: yesterday 

Forum to discuss Enterprise security using HPE Aruba Networking NAC solutions (ClearPass), Introspect, VIA, 360 Security Exchange, Extensions, and Policy Enforcement Firewall (PEF).
Back to discussions
Expand all | Collapse all

Onboarded Android devices and internal dns issues

This thread has been viewed 0 times

  • 1.  Onboarded Android devices and internal dns issues

    Posted Aug 28, 2014 10:33 AM

    Seems we have something odd going on which seems to affect some androids and not others, so wondering OS versions or operator customisations may be too blame.  My device can connect to inernal resources ok, using hostname, but some others are requiring the fqdn, or even IP as they report dns related problems.

     

    The fact this problem is inconsistant across devices makes me think it is due to the many variations of OS and customisations, but its leaving us with a bit of an issue. 

     

    Wondered if anyone else had experience any similar issued with android devices not using internal dns correctly?



  • 2.  RE: Onboarded Android devices and internal dns issues

    EMPLOYEE
    Posted Aug 28, 2014 10:35 AM
    You should always be using FQDNs. Are you expecting WINS functionality


  • 3.  RE: Onboarded Android devices and internal dns issues

    Posted Aug 28, 2014 10:37 AM

    Unfortuantely Im not familiar with WINS, I think that something the server guys look after!

     

    Works fine on Ipads, and my android, but not on 3 others we have tried, but apparantly is a known bug since 2010...

     

    http://code.google.com/p/android/issues/detail?id=8030

     

    Shortly: When connected on WiFi to a network which specifies a domain
    name, hostnames in that domain do not resolve without appending the domain
    to the hostname.

     

     But as you say, using FQDN would resolve this anway...