Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Αναζήτηση στην υποστήριξη

Προσοχή στις απάτες! Δεν θα σας ζητήσουμε ποτέ να καλέσετε ή να στείλετε μήνυμα σε κάποιον αριθμό τηλεφώνου ή να μοιραστείτε προσωπικά δεδομένα. Αναφέρετε τυχόν ύποπτη δραστηριότητα μέσω της επιλογής «Αναφορά παραβίασης».

Μάθετε περισσότερα
Αυτό το νήμα αρχειοθετήθηκε. Κάντε νέα ερώτηση αν χρειάζεστε βοήθεια.
Αρχειοθετήθηκε

Firefox incorrectly resolves DNS of local servers

Firefox Συμβατότητα ιστοτόπων
leosenko απαντήθηκε
leosenko
leosenko

When my resolv.conf contains domain mydom.local search mydom.local nameserver 192.168.1.18 nameserver 192.168.2.10

I encounter that I cannot access s1.mydom.local in firefox. However, I can access it in safari, chrome, via ssh, it responds to ping etc. On firefox says the server cannot be found. If i enter the server IP address, it works. So I go to about:networking#dns and see that DNS suffix is set to mydom.local attlocal.net

I go to DNS search and enter s1.mydom.local to get NS_ERROR_UNKNOWN_HOST. Then i enter only s1 and it spits out the correct IP address. And from there on, if I put into the address bar only https://s1 then it works.

It seems like a bug that when I enter s1.mydom.local firefox for some weird reason might be resolving s1.mydom.local.mydom.local which i just wrong. Is this a bug? No other browsers behave like this. Is there a workaround?

When my resolv.conf contains domain mydom.local search mydom.local nameserver 192.168.1.18 nameserver 192.168.2.10 I encounter that I cannot access s1.mydom.local in firefox. However, I can access it in safari, chrome, via ssh, it responds to ping etc. On firefox says the server cannot be found. If i enter the server IP address, it works. So I go to about:networking#dns and see that DNS suffix is set to mydom.local attlocal.net I go to DNS search and enter s1.mydom.local to get NS_ERROR_UNKNOWN_HOST. Then i enter only s1 and it spits out the correct IP address. And from there on, if I put into the address bar only https://s1 then it works. It seems like a bug that when I enter s1.mydom.local firefox for some weird reason might be resolving s1.mydom.local.mydom.local which i just wrong. Is this a bug? No other browsers behave like this. Is there a workaround?

Τροποποιήθηκε στις από τον/την leosenko

Όλες οι απαντήσεις (2)

markwarner22
markwarner22

VPN issues connection should contact VPN support.

leosenko
leosenko Ιδιοκτήτης ερώτησης

This is not VPN issue this is very clearly firefox issue.