# DNS name resolution, dynamic IP vs static IP

**URL:** <https://forums.digi.com/t/dns-name-resolution-dynamic-ip-vs-static-ip/10257>\
**Category:** Rabbit\
**Created:** [February 22, 2009, 10:45pm UTC](https://forums.digi.com/t/dns-name-resolution-dynamic-ip-vs-static-ip/10257 "2009-02-22T22:45:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![baldy672](https://avatars.discourse-cdn.com/v4/letter/b/c68b51/32.png) [@baldy672](https://forums.digi.com/u/baldy672)\
**Post date:** [February 22, 2009, 10:45pm UTC](https://forums.digi.com/t/dns-name-resolution-dynamic-ip-vs-static-ip/10257/1 "2009-02-22T22:45:42Z")

</div>

I have an application that will periodically go off to the internet to get config data and stuff. I call resolve() with a name like “[configdata.mysite.com](http://configdata.mysite.com)” to get back the address to which I want to open a socket connection.

If I have the device running DHCP it works perfectly. If I have it running with a static IP address and the DNS is set to a valid DNS server, it fails most of the time. I’m using both 9.40 (which is know is not the best DC version) and 9.50 and I see exactly the same behavior.

Is there a known issue with resolve() and static IP addresses?

---

<div class="post-metadata">

**Author:** ![baldy672](https://avatars.discourse-cdn.com/v4/letter/b/c68b51/32.png) [@baldy672](https://forums.digi.com/u/baldy672)\
**Post date:** [February 23, 2009, 3:39pm UTC](https://forums.digi.com/t/dns-name-resolution-dynamic-ip-vs-static-ip/10257/2 "2009-02-23T15:39:07Z")

</div>

I found the problem after many happy hours of rooting through library source. There was a rogue #define in our code which was causing the resolve code to ignore the manually set servers. I removed that and all seems well so far.