搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Failed DNS queries when port specified

  • 2 回覆
  • 0 有這個問題
  • 10 次檢視
  • 最近回覆由 FabienB

more options

Hi,

I'm having an issue with Firefox (on CachyOS, but i'm pretty sure that is not relevant) when I try to hit domain with PORT number.

To be clear, I have a "service" I am locally hosting on a more widely available "domain.com" (those are examples of course...) I am using this typology to still be able to generate Let's Encrypt certs for domains (that I own) not accessible outside my network for those sub-domains, and am using therefore Pi-hole to serve the few IPs of my few "service123.domain.com"

When I use a Chromium based browser (or FF ESR v128) the only DNS query is for "https://service.domain.com:8000" is "service.domain.com" (as seen on pihole queries and in FF-ESR/Chromium DNS cache), whereas FF 135 there is first a "service.domain.com" (righfully answered by my local DNS), and then a second query "_8000._https.service.domain.com" is sent, but my pihole doesn't seem to recognize (and shouldn't have to interpret anything concerning ports), so it sends it to upstream DNS (which are unable to answer)

I have disabled DoH, and every extensions. So I am really lost on what as changed in FF that would explain this, or if it's a pihole config problem (weirdly only affecting FF 135+ ...)

Feel free to ask anything, I may have omitted important info. Thanks in advance

Hi, I'm having an issue with Firefox (on CachyOS, but i'm pretty sure that is not relevant) when I try to hit domain with PORT number. To be clear, I have a "service" I am locally hosting on a more widely available "domain.com" (those are examples of course...) I am using this typology to still be able to generate Let's Encrypt certs for domains (that I own) not accessible outside my network for those sub-domains, and am using therefore Pi-hole to serve the few IPs of my few "service123.domain.com" When I use a Chromium based browser (or FF ESR v128) the only DNS query is for "https://service.domain.com:8000" is "service.domain.com" (as seen on pihole queries and in FF-ESR/Chromium DNS cache), whereas FF 135 there is first a "service.domain.com" (righfully answered by my local DNS), and then a second query "_8000._https.service.domain.com" is sent, but my pihole doesn't seem to recognize (and shouldn't have to interpret anything concerning ports), so it sends it to upstream DNS (which are unable to answer) I have disabled DoH, and every extensions. So I am really lost on what as changed in FF that would explain this, or if it's a pihole config problem (weirdly only affecting FF 135+ ...) Feel free to ask anything, I may have omitted important info. Thanks in advance

被選擇的解決方法

The problem might not have been perceived by anyone else, or it might not have been clearly expressed, but it is resolving itself has each of my problematic config (cachyos and third of my android devices) are updated to FF 136. I am still waiting for the last device to be updated, but I'm pretty confident

從原來的回覆中察看解決方案 👍 0

所有回覆 (2)

more options

Just as a quick footer note : same URL with no PORT specified works perfectly fine (still served by pihole)

有幫助嗎?

more options

選擇的解決方法

The problem might not have been perceived by anyone else, or it might not have been clearly expressed, but it is resolving itself has each of my problematic config (cachyos and third of my android devices) are updated to FF 136. I am still waiting for the last device to be updated, but I'm pretty confident

有幫助嗎?

問個問題

如果您還沒有帳號,您必須先登入帳號 來回覆文章。還沒有帳號的話,只能發問新問題