Dns resolver
-
- Restart the resolver on pfS.
- Run ipconfig /flushdns on the Windows box.
-
Hello doctor,
I did but 192.168.0.4 doesn't work still -
Well, then try from a different box or reboot Windows.
-
I did doctor and I continue to have same problem…
I don't want to bore you more so I use same without dns per switch.thanks!!!!
-
Can you please post a pic what you have under Services: DHCP server
-
sure
-
For me, I have no host over rides in DNS Resolver.
I do have the two buttons checked for "DHCP Registration" and "Static DHCP"also…
iIn DHCP server on lan tab I have a DNS range starting at 192.168.0.100 - 192.168.0.200 (using your subnet as example)
Then all the host that are mine and I always have connected, at the bottom of this DNS Server page on LAN tab, I have their MAC, IP reservation and hostname listed there starting at .2 and going no higher than .99
that leaves .100 - .200 available for DNS for visitors, for example.
Then I have .201 - .245 free incase I want to make more static reservations.
What kind of switch do you have? is it allowing ICMP? (ping)
-
-
I also have a switch getting its IP from DHCP on pfsense - Just gave it a static reservation at the bottom of my DHCP server LAN page that was below my normal DHCP leases. (so .2-.99)
You might try setting your switch up this way. And sice its your switch thats the issue, still would like to know the model number and manufacturer.
(FYI - In most situations, static IP configured at the machine is best. Its just that I'm far away from that equipment so wanted to leave things getting DHCP as much as possible incase something ever breaks any idiot easily deal with it)
-
Hello kejianshi doktor and phil
I found the solution…. in attachments you can see my setup
thanks for all!!!
bye
rob
-
Looks better now…