Bad DNS resolving using NTLM auth

UNCONFIRMED
Unassigned

Status

()

P3
normal
UNCONFIRMED
9 years ago
a year ago

People

(Reporter: olivier.toupin, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [ntlm][necko-backlog])

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6
Build Identifier: 

*No full DNS resolving

Network.automatic-ntlm-auth.trusted-uris="domain.org"

A. If accessing http://portal in Intranet no auth.
B. I have to do http://portal.domain.org. FF should be able to resolve with A


Reproducible: Always

Steps to Reproduce:
1.Add your domain to -> network.automatic-ntlm-auth.trusted-uris="domain.org"
2.Go to page in your domain not using all the address. Like portal instead of portal.domain.org
3.Your prompted for your password because FF doesn't recognize portal as in the domain. IE is able to do it, ping is able to do it, so don't say it not possible.


Expected Results:  
It should resolve portal correctly and understand it's in domain.org even if it has to redirect to full adress

Comment 1

7 years ago
I was about to create the same bug report. Windows resolves bare hostnames by successively trying the domains in the DNS suffix search list (use "ipconfig /all" from the command prompt to see the list). Firefox should follow the same process when checking the NTLM white list. 

Why after two years is this still "unconfirmed"?

I'm using Firefox 10.0.2, running on Windows 7 Enterprise x64 version "6.1.7601 Service Pack 1 Build 7601"
Jim, is this within your NTLM-fu, or should we find someone else to fix?

Updated

7 years ago
Assignee: nobody → jmathies

Comment 3

7 years ago
(In reply to Jason Duell (:jduell) from comment #2)
> Jim, is this within your NTLM-fu, or should we find someone else to fix?

I really don't have the time for this currently.

Updated

5 years ago
Assignee: jmathies → nobody
Whiteboard: [ntlm][necko-backlog]
You need to log in before you can comment on or make changes to this bug.