Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Firefox only request HTTPS type 65 DNS Records

  • 1 답장
  • 0 이 문제를 만남
  • 20 보기
  • 최종 답변자: Buco

more options

I noticed that sometimes (not everytime) I had "Server Not Found" error on some of my website. Since i have a DNS server at home i thought it was probably related to that so I opened Wireshark to see what was happening.

to better understand I have 2 dns records

server.lan that point to 192.168.1.61 and *.mydomain.com that points to server.lan with a CNAME.

In wireshark i saw that generally firefox does A and HTTPS(TYPE 65) queries but sometimes it only does HTTPS.

In case of a Type 65 query my dns server only answers with the CNAME so server.lan The issue is that Firefox doesnt try to resolve the CNAME.

When firefox do both A and Type65 it seems to work probably because it takes the A answer wich contains both cname and the IP of the CNAME but when it doesn't do both it just stop after the HTTPS one without trying to resolve the CNAME.

Google chrome seems to always do Both A and Type 65 query.

I noticed that sometimes (not everytime) I had "Server Not Found" error on some of my website. Since i have a DNS server at home i thought it was probably related to that so I opened Wireshark to see what was happening. to better understand I have 2 dns records server.lan that point to 192.168.1.61 and *.mydomain.com that points to server.lan with a CNAME. In wireshark i saw that generally firefox does A and HTTPS(TYPE 65) queries but sometimes it only does HTTPS. In case of a Type 65 query my dns server only answers with the CNAME so server.lan The issue is that Firefox doesnt try to resolve the CNAME. When firefox do both A and Type65 it seems to work probably because it takes the A answer wich contains both cname and the IP of the CNAME but when it doesn't do both it just stop after the HTTPS one without trying to resolve the CNAME. Google chrome seems to always do Both A and Type 65 query.

모든 댓글 (1)

more options

Seems like setting network.dns.native_https_query to false disable the use of type 65 query. It fix my problem since the IP is retrieve successfuly but i'm still curious regarding if the previous behaviour is normal or not.

도움이 되셨습니까?

질문하기

글에 답글을 달기 위해서는 계정으로 로그인해야만 합니다. 계정이 아직 없다면 새로운 질문을 올려주세요.