• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 39 subscribers
  • Views 1014 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Secondary DNS Server CC3100

Brian Costabile1
Prodigy 100 points
Other Parts Discussed in Thread: CC3100

I can see from the API to get/set Static IP configuration in Simplelink that there is only a primary DNS server. Is that true internally on the CC3100? If DHCP provides a secondary DNS server is it dropped by the CC3100? If CC3100 supports a backup DNS then is there a plan to add an API to get/set it?

  • 0
    TI__Mastermind 18455 points
    Hi Brian,

    Internally we support up to two DNS server addresses received in the DHCP process.
    However, in static configuration we only provide the option to set one address.
    As of today, we don't have any plans to change it.
    I would be interested of knowing if this is causing a problem with your implementation, as we didn't hear of such an issue till now.

    Thanks,
    Alon
  • 0 in reply to Alon Srednizki
    Prodigy 100 points
    The product I'm developing is a ZigBee-Wifi replacement of a ZigBee-Ethernet Gateway. The old product supports DHCP or static IP configuration and will display the settings (either Statically set or received via DHCP) on a simple LCD display.

    The CC3100 API is limited (for no apparent reason) on what data can be set or read back with regards to DNS. I can set/get the Primary DNS server and the domain name, but not the secondary DNS server or domain search list. As you mentioned, the data is there and supported internally, then why restrict access to it externally.

    I wouldn't say this is an "issue" per se, more like an oversight. It's obvious that you need to support methods to set/get DNS primary server, but it should be just as obvious to do the same with the secondary (and any other parameters received via DHCP) otherwise you don't truly support static network configuration.