Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

Avatar for Username

Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Firefox incorrectly resolves DNS of local servers

  • 2 risposte
  • 0 hanno questo problema
  • 4 visualizzazioni
  • Ultima risposta di leosenko

leosenko
leosenko
more options

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?

Modificato da leosenko il

Tutte le risposte (2)

markwarner22
markwarner22
more options

VPN issues connection should contact VPN support.

È stato utile?

leosenko
leosenko Utente che ha posto la domanda
more options

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

È stato utile?

Richiedi supporto

Bisogna accedere al proprio account per rispondere nelle discussioni. Se non si possiede ancora un account, inserire una nuova richiesta.