How to setup local domain in local network that everyone

[netboy]

@johnpoz said in How to setup local domain in local network that everyone:

Your client need to point to pfsense ip for host overrides to work.

I NOW understand what you are talking about.......how do I route the client to point to pfsense IP?

[johnpoz]

@netboy Out of the box it would of done that.. You must of changed your dhcp settings in pfsense, or you setup the IP on the box static?

Out of the box pfsense will point all dhcp clients to its own IP.

I on purpose point my clients to my pihole, the 192.168.3.10 address, but then my pihole asks pfsense. But if you didn't mess with those settings by default dhcp client of pfsense would point to pfsense IP as its dns.. And your host override would work.

btw - I noticed in your setup you had pfblocker installed. If clients do not point to pfsense for their dns - pfblocker isnt really going to work.

[netboy]

@johnpoz Got it!

Here is the screenshot of LAN

AND the SERVER portion of the screenshot

What you are saying is the SERVER portion should be BLANKED out so that all routes will be thru the pfsense router not thru google - Have I understaood the concept?

[netboy]

@johnpoz said in How to setup local domain in local network that everyone:

I noticed in your setup you had pfblocker installed. If clients do not point to pfsense for their dns - pfblocker isnt really going to work.

you are absolutely RIGHT! I was really ignorant.....I have NOW blanked out the server portion and rebooted my PC.

Now the nslookup returns the following:

C:> nslookup
Default Server: router2100.XXX.local
Address: 192.168.0.1

[netboy]

@johnpoz Resolver WORKS now....Thanks @johnpoz for hand holding me!!!

[johnpoz]

@netboy .local isn't a very good choice - that is a mdns domain.. You should use something like home.arpa which is the new recommended domain for local use, and is what pfsense now defaults too.

I am in the middle of moving over from my long term local.lan domain, .lan would never be a public tld. But home.arpa is best choice for local domains.

So your tv could be tv.home.arpa for example.. I just have some old ssl certs that have been changing when they expire.. So for example my nas uses home.arpa and my printer, etc..

$ dig nas.home.arpa +short
192.168.9.10

$ dig brother.home.arpa +short
192.168.2.50

[netboy]

@johnpoz said in How to setup local domain in local network that everyone:

.local isn't a very good choice - that is a mdns domain.. You should use something like home.arpa

I will try to understand what you are talking about and change it....

Quick question in the resolver....I have tv as below

Works fine but I have to enter so:

http://tv.home.com:9981/extjs.html

Is there a way tv.home.com resolves to /tv.home.com:9981/extjs.html?

[johnpoz]

@netboy no there isn't dns does not provide that ability. You would have to use a proxy to do something like that. Or whatever is serving up extjs.html - on that httpd make that the default document.

Most http servers serve like index.html or index.php as the default document.. But that can normally be changed to anything you want. Not sure exactly what your accessing, if it really is a tv then most likely not.

But what does it matter to be honest, create a bookmark and there you go..

if was any typical httpd you could also have it listen on the default 80 or 443 port if https and then you wouldn't have to use the port..

[netboy]

@johnpoz Got it!

Got it thx

[netboy]

@netboy I am posting a better method to accomplish my functiionality.

Say you have a local webserver and running NUT server.....the URL will be something like
http://192.168.X.XX/cgi-bin/nut/upsstats.cgi

I do NOT want to remember the full URL and by typing a shortcut say "ups" the browser must take me to http://192.168.X.XX/cgi-bin/nut/upsstats.cgi

This can be done in Chrome browser as follows:

Step 1 :
Type chrome://settings/searchEngines in chrome browser

Step 2: Add a site search
search engine: just make up some name
shortcut : ups
URL with %s in place of query : http://192.168.X.XX/cgi-bin/nut/upsstats.cgi

And Add!

Thats it! now if you type ups in the chrome browser the browser will take you to http://192.168.X.XX/cgi-bin/nut/upsstats.cgi

The netgate resolver only resoves to IP and not to the FULL url! Maybe Netgate can add this functionality

[johnpoz]

@netboy wouldn't bookmark just be easier???

if you goal is typing it out in your address bar, just set a tag or keyword.