Resolver reverse DNS brokeness?
Rick Murray (539) 13840 posts |
Hi, So I visit my website, and I later on test the resolver’s ability to reverse DNS (simply by calling it with an IP address as the input hostname and looking to see what the output hostname says (or it’ll abort with R0 = -1 if there’s no name for that IP address). The result? The primary name for my host is “www.heyrick.co.uk” (no it isn’t, that’s a virtual host!) and the aliases are… empty. I’m going to have to reboot my machine now, as reinitialising Resolver leads to abort on data transfer (so I will need to save this message and send it afterwards). Right, rebooted to a fresh system. It will now correctly look up the true name of the host, but has no aliases at all. On the other hand, if I look at some of the alternative hostnames, then Resolver will return those (with the first seen as the ‘primary’) without actually bothering to look up the hostname correctly. Some code:
If you repeat the above on a freshly booted machine but do a…
(replace StupidBloodyTextile with “www” in the above) beforehand, then that’s what will be returned for that IP address, not the correct (fi1…) domain. Not a big deal really, but it does look broken… |
Steve Pampling (1551) 8170 posts |
Yup. Now you know one of the reasons I keep banging on about needing to have a new resolver (and probably much of the IP stack as socket handling is a bit erm …. too) |