View Issue Details

IDProjectCategoryView StatusLast Update
0000972unrealircdpublic2003-11-20 19:43
ReporterByte Assigned Tosyzop  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version3.2-beta16 
Summary0000972: [IPv6] DNS Resolver uses replies incorrectly
DescriptionUsing IPv6 support, it checks for 'ANY' records, isntead of 'A' without IPv6 support.
'ANY' returns 'SOA' and 'NS' (if the hostname is also a domain) or 'MX' (if the hostname has a mailserver associated with it).

Steps To ReproduceUse a hostname which is a domain or has an MX record.

localhost. 604800 IN SOA proxima.lan. sa3.macs.hw.ac.uk. 2002081602 28800 14400 604800 86400
localhost. 604800 IN NS proxima.lan.
localhost. 604800 IN A 127.0.0.1
it seems to see SOA and decide it can't resolve the hostname (which the ip resolved to)

proxima.lan. 3600 IN MX 0 proxima.lan.
proxima.lan. 3600 IN A 172.16.0.4
Additional InformationThis problem can't occur if IPv6 support is disabled
3rd party modules

Activities

syzop

2003-05-11 15:14

administrator   ~0002747

Last edited: 2003-05-11 15:20

I'll take a look why that causes a "conflict". [*edit*] hehe it gets pretty confused, I'll find out ;p.

edited on: 05-11-03 15:20

syzop

2003-05-11 16:41

administrator   ~0002748

I think I've fixed this in CVS (.1794). Thanks for reporting.

[cvs instructions pasted below in case you didn't know them]
cvs -d :pserver:[email protected]:/home/cmunk/ircsystems/cvsroot login
(press return when asked for the password)
cvs -d :pserver:[email protected]:/home/cmunk/ircsystems/cvsroot co -r devel -d Unreal3.2 unreal

Issue History

Date Modified Username Field Change
2003-05-11 10:02 Byte New Issue
2003-05-11 15:13 syzop Summary DNS Resolver uses replies incorrectly => [IPv6] DNS Resolver uses replies incorrectly
2003-05-11 15:14 syzop Note Added: 0002747
2003-05-11 15:20 syzop Note Edited: 0002747
2003-05-11 16:41 syzop Status new => resolved
2003-05-11 16:41 syzop Resolution open => fixed
2003-05-11 16:41 syzop Assigned To => syzop
2003-05-11 16:41 syzop Note Added: 0002748
2003-11-20 19:43 syzop Status resolved => closed