Lotsa Shell BNC's won't resolve with Unreal3.2.3 :\

[r3mbr4ndt]

Noticed after upgrading lots of BNC's from shell co's won't resolve. Anyone else seeing this?

[Syzop]

It would be nice if you could give some real technical proof[1].
That is.. _on the same box_ do:
- 'host <ip>'
- 'host '<hostname that ip resolved to>'
and show us the results.

[1] Unlike the person who reported something similar on the bugtracker that seemed to have next to no technical knowledge and could hardly speak english :P.

[r3mbr4ndt]

I personally don't use a bnc but...

This host used to resolve on 3.2.2:

---

nslookup 66.252.15.40
Server: proxy1.mad.wi.charter.com
Address: 24.196.64.39

Name: iced.out.like.a.truethug.net
Address: 66.252.15.40
Aliases: 40.15.252.66.in-addr.arpa

---

nslookup iced.out.like.a.truethug.net
Server: proxy1.mad.wi.charter.com
Address: 24.196.64.39

Non-authoritative answer:
Name: iced.out.like.a.truethug.net
Address: 66.252.15.40

---

and now with 3.2.3 it doesn't. This is on Win2k3 and is also happening on a friend's Mandrake.

P.S. 24.196.64.39 is the dns server I have configured in the conf.

[Syzop]

Thanks.

Code: Select all

$ host 66.252.15.40
40.15.252.66.IN-ADDR.ARPA is a nickname for 40.15.252.66.digitalshell.net
40.15.252.66.digitalshell.net domain name pointer iced.out.like.a.truethug.net

so: 40.15.252.66.IN-ADDR.ARPA -CNAME-> 40.15.252.66.digitalshell.net -PTR-> iced.out.like.a.truethug.net

It could very well be that such a configuration was broken in 3.2.3, because I fixed a cname caching bug.
I think I only tested cname's in hostnames, not for reverse records.

[r3mbr4ndt]

It seems that a lot of shell co's use similar configurations because that isn't the only host won't resolve after the upgrade. Thanks for checking into this and I hope to see a fix in the near future

[Syzop]

Will do, could take a few days however.
Bug added as #2431.