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.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox incorrectly resolves DNS of local servers

  • 2 replies
  • 0 have this problem
  • 4 views
  • Last reply by 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?

Modified by leosenko

All Replies (2)

markwarner22
markwarner22
more options

VPN issues connection should contact VPN support.

Helpful?

leosenko
leosenko Question owner
more options

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

Helpful?

Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.