Jump to content
Posted 07 November 2014 - 22:44
Posted 08 November 2014 - 02:03
Posted 08 November 2014 - 10:30
Why would you think hostname should resolve? That is not fully qualified. That is BAD habit to think that a host name should resolve like that.
from a cmd line using say did or nslookup do your hosts resolve? Where is extract from wireshark? I don't see anyting?
Now pfsense will answer those, if they are in your host file in pfsense, and those get added in via different ways, over ride, dhcp reservation, etc.
But what I would suggest you do is just create a bookmark that is FQ to your pfsense, or any other hosts you want to resolve on your local network - and use FQDN when you want to access stuff.
So validate that fqdn resolves
Pinging pfsense.local.lan [192.168.1.253] with 32 bytes of data:
Reply from 192.168.1.253: bytes=32 time<1ms TTL=64
When you use fqdn does it resolve??
I think that because that is how it has always worked up until recently.
Using nslookup from my mac the hostname 'pfsense' resolves. Apologies the wireshark screen grab apparently didn't work. Sending this from my mac atm so don't have it on here. Will edit the original post later when I have access to my pc again.
I do have bookmarks setup, I just tend to use keyboard and type where I want to go in the command bar. No reason for this, just the way I apparently prefer to navigate.
From my mac (and presumably everything else) both 'ping pfsense' and 'ping FQDN' work.
Yeah, always try to use the FQDN of a device, because it stops Safari (And probably every other browser now) doing searches for them.
Safari and Firefox show the exact same behaviour now, entering a bare hostname does a Google search. If you want to connect you either need to tell it that it's a hostname (So they look it up via DNS) or use the FQDN variant.
When you say 'now', has there been a change in the way the browser handles this recently? I use firefox and as I said, previously, I had always got to the server using just the hosname.
It's really not a massive issue, it's just I had gotten used to that way of working, and I thought I had messed up something in my setup to cause the change!
Posted 08 November 2014 - 10:56
Posted 08 November 2014 - 11:30
Posted 08 November 2014 - 15:48
Thanks both of you. Perhaps I should use this to get out of my bad habit!
Why do you have a subdomain for your lan? I think mine is just hotname.localdomain, you seem to be using hostname.local.lan. Just curious.
Posted 08 November 2014 - 16:10
sorry budman, I can't seem to edit my earlier post. Here is the sireshark screen grab I tried to post last time.
Posted 09 November 2014 - 13:45
so you did a query for pfsense.localdomain. And got a response. So did add a search suffix, is it correct is the ??
is localdomain your domain? That is single label domain and again a bad habit.. Use something better like pfsense.local.domain or pfsense.home.localdomain or pfsense.home.lan or pfsense.rancid.lannet, when you use single label your at a tld, and can have issues just using tld.