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

Chromecast DNS Hard-code

This thread has been viewed 1 times

  • 1.  Chromecast DNS Hard-code

    Posted Feb 19, 2014 05:02 PM

    I have a user who wants to use chromecast, but our network design currently requires users on our network to use our DNS servers. Apparantly, the DNS settings are hard-coded to Google's on the Chromecast.

     

    Does anyone have any suggestions for strategies to counter this in my current design? I don't see a way out.



  • 2.  RE: Chromecast DNS Hard-code

    EMPLOYEE
    Posted Feb 19, 2014 05:49 PM

    The only thing I've seen is that you can change the DNS server if you root the Chromecast (which is obviously not feasible).



  • 3.  RE: Chromecast DNS Hard-code
    Best Answer

    Posted Feb 19, 2014 06:29 PM

    You should be able to setup a policy to dst-nat DNS requests from Google's servers to yours.  For example:

     

    user host 8.8.8.8 svc-dns dst-nat ip x.x.x.x

    user host 8.8.4.4 svc-dns dst-nat ip x.x.x.x

     

    you could also setup a netdestination for all Google's servers and use that instead

     

    netdestination google-dns

      host 8.8.8.8

      host 8.8.4.4

    user alias google-dns svc-dns dst-nat ip x.x.x.x



  • 4.  RE: Chromecast DNS Hard-code

    Posted Feb 20, 2014 10:55 AM

    Thanks for the information, clembo! I will give this a try and report back!



  • 5.  RE: Chromecast DNS Hard-code

    Posted Sep 24, 2014 05:45 PM

    OP delivers! 7 months later now that I have PEF licensed, I went ahead and implented the following:

     

    user host 8.8.8.8 svc-dns dst-nat ip x.x.x.x

    user host 8.8.4.4 svc-dns dst-nat ip x.x.x.x

     

    and applied it to the role the chromecasts land on, and it worked perfectly!

     

    Thanks clembo!

     

    P. S. - This is all going to be invalided by DNSSEC, isn't it? :)



  • 6.  RE: Chromecast DNS Hard-code

    Posted Sep 27, 2014 08:00 AM
    @alamey wrote:

    P. S. - This is all going to be invalided by DNSSEC, isn't it? :)

    not really sure it would be. DNSSEC is mainly active between the DNS server that actually has the authoritive DNS record and its higher levels. that you get there via different DNS servers shouldn't really matter.