CODEWITHSUNDEEP
linuxmacosfirefox
atapaka
atapaka

Reputation: 1356

Firefox incorrectly resolves local DNS names

Consider the following situation: resolv.conf contains

domain mydom.local
search mydom.local
nameserver 192.168.1.18
nameserver 192.168.2.10

In that case s1.mydom.local is inaccessible in firefox (server not found). However, safari, chrome, ssh, ping, all resolve that address correctly.

If i enter the server IP address, it works.

about:networking#dns shows that DNS suffix is set to

mydom.local
attlocal.net

I go to about:networking DNS search and enter s1.mydom.local to get NS_ERROR_UNKNOWN_HOST. However, when 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, obviously, i get certificate errors.

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 is just wrong.

Is this a bug? No other browsers behave like this. Is there a workaround? For me this is a serious problem as I cannot work e.g. connected to a VPN, I either get server not found or certificate errors.

Upvotes: -2

Views: 28

Answers (0)

Related Questions