View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002608 | unreal | ircd | public | 2005-07-31 11:32 | 2005-08-19 11:51 |
| Reporter | Daedalon | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | duplicate | ||
| Product Version | 3.2.3 | ||||
| Summary | 0002608: DNS not working in UIRCd with many hosts that work otherwise fine | ||||
| Description | This has been a problem with many hosts. When connecting, after a longish wait time only *** Couldn't resolve your hostname; using your IP address instead comes up and the user gets only his IP displayed as his/her hostname. The hostnames work perfectly in non-UnrealIRCd networks, with host and so on. Even on the servers that run UnrealIRCd, host command in shell resolves everything fine (just the way to test that UnrealIRCd FAQ http://www.vulnscan.org/UnrealIrcd/faq/ suggests). So as /etc/resolv.conf is and has always been fine, host and other shell commands find the domain->IP and IP->domain reverses correctly, the hostname works in other IRC networks but none of our UnrealIRCd's can resolve it even if the resolve timeout is as large as 45 sec (normally 2 sec), I don't think the fault can be anywhere but in UnrealIRCd. And mind you, this is not the case with just one host. | ||||
| Steps To Reproduce | /reconnect (if you host happens to be among those that UnrealIRCd cannot resolve for some reason even if host command in the server's shell can) and /whois yourself | ||||
| 3rd party modules | |||||
|
|
And for clarity I'd like to point out that none of these non-working hosts seems to be a CNAME. host -t a hostname returns the correct IP and host -t a IP returns the hostname. I checked also with host -a hostname that there's an A or ANY field, no CNAMEs. Just to make sure this isn't a duplicate of the fixed bug number 2431: http://bugs.unrealircd.org/view.php?id=2431 |
|
|
I think this is a duplicate of 0002431. Did you download the CVS and try? |
|
|
Just want to confirm what has been said: try latest CVS and see if that fixes it. |
|
|
For some reason the tested hosts worked with one CVS version we set up and running. Though I can't find any CNAMEs involved there, maybe the fix in 2431 applies to more than CNAMEs or maybe I was just missing something there. Thanks anyways, we're eagerly waiting for the next stable release to get the hostnames correct in our IRC network. |
|
|
Could you paste a few (or 1) of these IPs that had this problem? ( or mail them to [email protected] ) Also... just to confirm: it all works fine now, right? Because you said you would wait for a new release.. you can just use the patch from http://www.vulnscan.org/tmp/downgrade.resolver.patch already, which means you can just have 3.2.3 + the dns fix. 3.2.4 is not even in a testing phase yet, so it's not like it would be released in 2 weeks or something like that. |
|
|
(noresponse) .. but apparently fixed |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2005-07-31 11:32 | Daedalon | New Issue | |
| 2005-07-31 11:39 | Daedalon | Note Added: 0010296 | |
| 2005-07-31 14:19 | Stealth | Note Added: 0010298 | |
| 2005-07-31 17:47 | syzop | Note Added: 0010300 | |
| 2005-08-08 14:24 | Daedalon | Note Added: 0010318 | |
| 2005-08-08 14:47 | syzop | Note Added: 0010319 | |
| 2005-08-08 14:47 | syzop | Note Edited: 0010319 | |
| 2005-08-08 14:49 | syzop | Note Edited: 0010319 | |
| 2005-08-08 14:50 | syzop | Note Edited: 0010319 | |
| 2005-08-19 11:51 | syzop | Status | new => closed |
| 2005-08-19 11:51 | syzop | Note Added: 0010352 | |
| 2005-08-19 11:51 | syzop | Resolution | open => duplicate |
