Dns resolver

[robertog]

Hello guys!
Im using version 2.2 pfsense, I have problem to resolve name dns.

In attachment u can see dns resolve correct:
192.168.0.1 (pfsense)
192.168.0.10 my notebook

192.168.0.4 NO
I have hp switch with this fix ip.

So I think something I have to setup….but I don't know...
thanks to everybody your support
bye
roberto

[kejianshi]

Looks like maybe DNS Forwarder is off, DNS Resolver is off, no DNS listed in system > general and getting no DNS from WAN DHCP.

That would be my first guess.

[robertog]

hello kejianshi
thanks for your reply but I continue to have same problem…
I did what you suggest and u can see in attachments.
Do u have other suggestion?

Thanks a lot
roberto

[kejianshi]

You see the one that says DNS forwarder?  Turn that off.  Click save.

Yous see the one that says DNS resolver?  leave that ON.  Click save.

You see where you listed 127.0.0.1 in system > general?  Remove 127.0.0.1  Click save.

Reboot pfsense and all your computers.

Let me know how that works for you.

[robertog]

Hello kejianshi,
sorry I did your suggestion but I have problem still..

if u have other idea let me to know.

thanks a lot!
roberto

[doktornotor]

The ARP table is kinda irrelevant when it comes to DNS… Kinda at a loss what's the screenshot supposed to illustrate. Does 192.168.0.4

• get a static lease from pfSense, or dynamic one - and are those enabled to get registered in DNS?
• if not, you have some host override in place?

[robertog]

Yes,  just to show you this ip is working…do you have suggestion?

thanks a lot
roberto

[doktornotor]

Yes what??? Suggestions are above.

[phil.davis]

The switch at 192.168.0.4 has a fixed IP.
The other devices are known to pfSense DNS Resolver because they got their IP address with pfSense DHCP, or it is pfSense itself.

You need to add a host override entry for the switch - pfSense cannot guess the name of the switch.

[robertog]

hello phil.
I did but I have problem still…

My final setup is this in attachment.

thanks for other suggestion

roby

[doktornotor]

• Restart the resolver on pfS.
• Run ipconfig /flushdns on the Windows box.

[robertog]

Hello doctor,
I did but 192.168.0.4 doesn't work still

[doktornotor]

Well, then try from a different box or reboot Windows.

[robertog]

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!!!!

[kejianshi]

Can you please post a pic what you have under Services: DHCP server

[robertog]

sure

[kejianshi]

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)

[doktornotor]

@robertog:

so I use same without dns per switch.

No idea what you mean…

[kejianshi]

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)

[robertog]

Hello kejianshi doktor and phil

I found the solution…. in attachments you can see my setup

thanks for all!!!

bye
rob