BugTraq
common dns misconfiguration can lead to "same site" scripting Jan 18 2008 04:40PM
Tavis Ormandy (taviso sdf lonestar org) (2 replies)
Re: common dns misconfiguration can lead to "same site" scripting Jan 21 2008 08:25AM
Florian Weimer (fweimer bfk de) (1 replies)
Re: common dns misconfiguration can lead to "same site" scripting Jan 21 2008 05:04PM
David Malone (dwmalone maths tcd ie) (1 replies)
On Mon, Jan 21, 2008 at 09:25:08AM +0100, Florian Weimer wrote:

> | Note that all domains that contain hosts should have a "localhost" A
> | record in them.

> That RFC was obsoleted by RFC 1912 in 1996, so there's no RFC
> conformance issue if you omit the domain names. But it explains why
> there are so many zones that contain them.

I've always assumed that the reasoning for this is as "localhost"
looks like an unqualified domain name, the search path in resolv.conf/...
will be applied. To avoid having to walk the entire search path
every time localhost is resolved, it is easier to make sure that
localhost is in the domain that is looked up first. This still seems
like a valid thing to do, rather than a misconfiguration.

Would it make sense to update RFC 2109's rules to special case
records resolving to 127.0.0.1 or ::1 (or, more generally, any
address space that is not considered globally unique) unless both
names resolve to addresses in the same block.

David.

[ reply ]
Re: common dns misconfiguration can lead to "same site" scripting Jan 21 2008 05:19PM
Florian Weimer (fweimer bfk de)
Re: common dns misconfiguration can lead to "same site" scripting Jan 19 2008 12:02AM
Kurt Grutzmacher (grutz jingojango net)


 

Privacy Statement
Copyright 2010, SecurityFocus