Something is definitely wrong because normally when updating a TXT
record, it should replace the older TXT record in the cache, but for
some reason that isn't happening for you. Can you run "dns-sd -U" on
the Windows machine and then redo your experiment. That will test
TXT record updating.
Thanks.
-Marc
On Jun 29, 2005, at 3:53 PM, Mark Smith wrote:
I'm getting strange behavior when updating my service's TXT
record. I'm running Bonjour 1.0 on XP using the DLL.NET bindings.
My call to DNSService.UpdateRecord() passes null for the record
reference and 0 for the timeout, so my understanding is that it
should just update the TXT record and give it the default timeout.
When other clients resolve my service, they get all the previous
TXT records, not just the latest updated version. If I run
"killall -info mDNSResponder", before and after a record update, it
looks like this:
Assuming the first numeric value after the colon is the timeout, it
seems to have added another record and bumped up the timeout for
the old ones. Am I fundamentally misunderstanding how this is
supposed to work? How do I just update the TXT record so that
browsers see only the new contents?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bonjour-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/bonjour-dev/email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bonjour-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/bonjour-dev/email@hidden
