DNS resolution
-
So I moved to a headless old pc from a virtualized pfsense. I have 4 eth's ports configured of intel pcie device, where eth1 is WAN, and the rest 3 are LAN.
Lan1 - connects to my MAC directly
Lan2 - Wifi AP
Lan3 - to my serverNow have given hostname to my server as "myserver" and to pfsense as "pfsense". The domain name being "my home". I know silly names. But was was trying to access the devices from web browser through these names, i.e, myserver.myhome and pfsense.myhome and they do not work. But if i use the IP's instead it all works fine.
Anyone please help me with this issue, also i am trying to set the server to be connected whenever i start my PC. When i was using a generic TPlink router it worked fine but now it does not connects,i.e, when i try set the FINDER->GO-> connect to server. But through URL and ping it is all fine.
-
"the rest 3 are LAN. "
So you bridged these interfaces?
how do you have a domain name with a space in it??? "my home"
Not a fan of single label domain.. .myhome you could use say my.home would be a better domain but I think home is going to be a future official tld.. Why not something like myhome.local ? or myhome.lan ?
what are you devices using for dns? Are they using a proxy? If they are not pointed to pfsense for dns then no they are not going to be able to resolve them. Are you registering dhcp into pfsense? Do you have dhcp reservations set for these and have them registered? Did you create host overrides?
Are you using the default resolver or did you change it to forwarder mode or are you using the forwarder?
-
"the rest 3 are LAN. "
So you bridged these interfaces?
No, I think. I have assigned all the 3 different IP's, 192.168.1.x, 192.168.2.x and 10.10.10.x
I am not sure how to bridge and will help in what i am trying since the above work except the name resolution..how do you have a domain name with a space in it??? "my home"
Not a fan of single label domain.. .myhome you could use say my.home would be a better domain but I think home is going to be a future official tld.. Why not something like myhome.local ? or myhome.lan ?
Sorry my mistake. Its just and example of the latest trial and it was one word "myhome".
what are you devices using for dns? Are they using a proxy? If they are not pointed to pfsense for dns then no they are not going to be able to resolve them. Are you registering dhcp into pfsense? Do you have dhcp reservations set for these and have them registered? Did you create host overrides?
Are you using the default resolver or did you change it to forwarder mode or are you using the forwarder?
Let me clear that i am not very sure of how the DNS is suppose to work with pfsense and how to configure it. I have never played with it even when i had simple router, always left as default.
A little history with pfsense of what i did so far:
During the initial setup, i have given a DNS server IP as 8.8.8.8 and 8.8.4.4. I did this because LAN2 and LAN3 were not reachable to internet, but though LAN1 works fine when i do not give the explicit DNS server IPs. I have still not figure what i am doing wrong in this case..
When i created static ip for the server, i had given hostname to it with the assumption that will do the job.No proxy is being used.
I am not sure how point everything to pfsense for dns to work. So i am guessing this would be the mistake i am doing. How can i check this? On the server I have mention DNS server as "pfsense LAN3 IP"
When you say registering DHCP into pfsene , do you mean the option to enable "DHCP Registration - Register DHCP leases in the DNS Resolver", if so yes, else i do not know what you talking about.Do you have dhcp reservations set for these and have them registered?
How do i do this?
No host overrides were done.
DNS forwarder is not enabled.
-
So you have your 3 devices on 3 different network segments. Do you want that? Doesn't seem like the fastest way to connect your MAC to your server.. Why would you not just use a switch? I can understand wanting your wifi on another segment.
What firewall rules did you create on these opt interface your wifi and server would be on?
dhcp server running on each interface would point to pfsense for dns. Putting in 8.8.8.8 would be pointless if running pfsense unbound default out of the box which is a resolver.
As to putting in a reservation - click the lease for the device to add a reservation. Or just use an override on the bottom of the dns resolver.
-
Well i did not go for switch because, i din't want to invest more for basic home setup..
No i really do not need 3 segments.. may be 2 segments with the wifi separate from the wired. But since i am still getting to know pfsense, i might do that in the future. I was not sure if briding at NIC where pfsense is running will make the through bad or good or no diff, so never considered it.The rules are for WAN and LAN were the default rules as existed never changed them yet.. On LAN 2 and 3 I had added rules for basic traffic to and from respective network to any..
When you say "just use an override on the bottom of the dns resolver.", does this mean configuring myrouter.myhome to the server IP and i can use http://myrouter.myhome url in web browser?
-
invest more for a basic home setup.. A $25 8 port gig switch going to break the budget?? What device are you running pfsense on? Is it gig interfaces? Is it routing/firewalling at full gig speeds? If you want best possible speed between devices that normally would be on the same network in a home setup, ie your machine and the server your storing files and stuff on you will want a switch. If your going to move to the next level from a soho wifi router your prob going to want the ability at some point to do vlans as well. So when you get a switch - get a "smart" one that does vlans they are really not any more expensive than a dumb one at the entry level.
Either set your machines to static IPs or set a reservation for them. Then either register the static reservation or setup an override… Do you need a picture???
1 - enter a static lease/reservation on the dhcp server by clicking the add button
2 - click the little button on a current lease to make static entry for that device
3 - add an override for whatever you want to resolve on the resolver tab on the bottom - click the add button
-
actually i did not invest at all.. I tried pfsense on VM but it was giving all weird behaviors also when server shutdown the whole routing failed and when my wifi router finally failed , i just used a very old system(pentium4 with 1G ram) and got it working. I was looking for a switch but was never sure if the one i was looking for were managed switches.. For example is this TL-SG108E a managed switch or not and if not is it fine to use because they do mention vlan is supported.. Another reason i did not go for a switch was i had very few systems to support so i assumed i could handle with existing PCIe port connection..
Like i said using Intel pentium 4 LGA 775 based montherboard with 1G ram and Intel PCIe I340T(not original got it from ebay)..
Yes right now all but wifi devices are static IPs.Thanks a lot for your help Johnpoz..
Let me play around a bit for couple more days and see what i can do and understand and your steps might help ..
