# New ngx\_resolver changes breaks modules

**URL:** <https://www.ruby-forum.com/t/new-ngx-resolver-changes-breaks-modules/238060>\
**Category:** NGINX\
**Created:** [December 14, 2013, 7:12pm UTC](https://www.ruby-forum.com/t/new-ngx-resolver-changes-breaks-modules/238060 "2013-12-14T19:12:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![musicdenotation](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/ea666f/32.png) [@musicdenotation](https://www.ruby-forum.com/u/musicdenotation)\
**Post date:** [December 14, 2013, 7:12pm UTC](https://www.ruby-forum.com/t/new-ngx-resolver-changes-breaks-modules/238060/1 "2013-12-14T19:12:20Z")

</div>

While back porting ngx\_resolver changes by Ruslan E. I get these  
errors:

error C2039: ‘type’ : is not a member of ‘ngx\_resolver\_ctx\_s’  
error C2440: ‘=’ : cannot convert from ‘ngx\_addr\_t’ to ‘ULONG’

Has this been intentional or did a glitch happened throughout the  
changes ?

Posted at Nginx Forum:

> **[new ngx\_resolver changes breaks modules](https://forum.nginx.org/read.php?2,245532,245532#msg-245532)**
>
> While back porting ngx\_resolver changes by Ruslan Ermilov I get these errors: error C2039: 'type' : is not a member of 'ngx\_resolver\_ctx\_s' error C2440: '=' : cannot convert from 'ngx\_addr\_t' to 'ULONG' Has this been intentional or did a glitch...

---

<div class="post-metadata">

**Author:** ![itpp2012](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/i/f05b48/32.png) [@itpp2012](https://www.ruby-forum.com/u/itpp2012)\
**Post date:** [December 14, 2013, 9:36pm UTC](https://www.ruby-forum.com/t/new-ngx-resolver-changes-breaks-modules/238060/2 "2013-12-14T21:36:37Z")

</div>

On Sat, Dec 14, 2013 at 01:11:45PM -0500, itpp2012 wrote:

> While back porting ngx\_resolver changes by Ruslan E. I get these  
> errors:
> 
> error C2039: ‘type’ : is not a member of ‘ngx\_resolver\_ctx\_s’  
> error C2440: ‘=’ : cannot convert from ‘ngx\_addr\_t’ to ‘ULONG’
> 
> Has this been intentional or did a glitch happened throughout the changes ?

The API changes were minimal and intentional. The “type” field  
no longer exists, and the “addrs” array now holds ngx\_addr\_t’s.
