Avatar for Username

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Firefox only request HTTPS type 65 DNS Records

  • 1 réponse
  • 0 a ce problème
  • Dernière réponse par Buco

Buco
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.

Toutes les réponses (1)

Buco
Buco Auteur de la question
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.

Cela vous a-t-il été utile ?

Poser une question

Vous devez vous identifier avec votre compte pour répondre aux messages. Veuillez poser une nouvelle question, si vous n’avez pas encore de compte.