[Bug network/11950] res_send fails with ETIMEDOUT on successful DNS UPDATE

[Bug network/11950] res_send fails with ETIMEDOUT on successful DNS UPDATE

[jsm28 at gcc dot gnu.org]

http://sourceware.org/bugzilla/show_bug.cgi?id=11950

Joseph Myers <jsm28 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|libc                        |network

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug network/11950] res_send fails with ETIMEDOUT on successful DNS UPDATE

[schwab@linux-m68k.org]

http://sourceware.org/bugzilla/show_bug.cgi?id=11950

Andreas Schwab <schwab@linux-m68k.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|drepper.fsp at gmail dot    |unassigned at sourceware
                   |com                         |dot org

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug network/11950] res_send fails with ETIMEDOUT on successful DNS UPDATE

[fweimer at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=11950

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com

--- Comment #3 from Florian Weimer <fweimer at redhat dot com> ---
I don't think it's reasonable to expect that res_send can be used to send
anything that isn't a DNS query.  If you want to send DNS UPDATE messages, you
have to implement that on top of the socket API.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug network/11950] res_send fails with ETIMEDOUT on successful DNS UPDATE

[dos at scarff dot id.au]

https://sourceware.org/bugzilla/show_bug.cgi?id=11950

--- Comment #4 from Dean Scarff <dos at scarff dot id.au> ---
Thanks Florian - I realize it's a little optimistic expecting the resolver
library to work for non-QUERY messages.

However, I think there's already some separation in the resolver's high-level
routines (res_query and res_search) and res_send; the latter seems intended to
be message-agnostic.  I think it's valuable for users of glibc if res_send can
preserve its generality - and doing so here is a small change.  Please consider
this patch. :)

For portability I ended up implementing my own code for sending DNS messages
over sockets (years ago - this is quite an old bug!), just as you suggested. 
But it's a shame since it duplicates much of the functionality already present
in most implementations of res_send.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug network/11950] res_send fails with ETIMEDOUT on successful DNS UPDATE

[neleai at seznam dot cz]

https://sourceware.org/bugzilla/show_bug.cgi?id=11950

Ondrej Bilka <neleai at seznam dot cz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |neleai at seznam dot cz

--- Comment #5 from Ondrej Bilka <neleai at seznam dot cz> ---
A more reasonable approach than adding update functionality to res_send would
be adding a high level routine, say res_update. Do you want to work on this?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug network/11950] res_send fails with ETIMEDOUT on successful DNS UPDATE

[fweimer at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=11950

--- Comment #6 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Ondrej Bilka from comment #5)
> A more reasonable approach than adding update functionality to res_send
> would be adding a high level routine, say res_update. Do you want to work on
> this?

I think upstream already has support for DNS UPDATE, but we have been out of
sync for a long, long time.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug network/11950] res_send fails with ETIMEDOUT on successful DNS UPDATE

[neleai at seznam dot cz]

https://sourceware.org/bugzilla/show_bug.cgi?id=11950

Ondrej Bilka <neleai at seznam dot cz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #7 from Ondrej Bilka <neleai at seznam dot cz> ---
> I think upstream already has support for DNS UPDATE, 
> but we have been out of sync for a long, long time.

If there is equivalent functionality it should be used instead relying on
res_send which may not be portable.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug network/11950] res_send fails with ETIMEDOUT on successful DNS UPDATE

[fweimer at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=11950

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |security-

-- 
You are receiving this mail because:
You are on the CC list for the bug.