New installation, but no DNS with DHCP

darkcorner

I made a fresh installation of pfSense on a PC.
In the console I can ping 8.8.8.8 and google.com
From a PC on a LAN I can only ping 8.8.8.8 and obviously I cannot surf the Internet.
I solved it by putting 8.8.8.8 and 8.8.4.4 in the DNS section of the DHCP Server, but I don't understand why it shouldn't work without it as it was never needed before.

the other

Hey there,
So, what are your settings...
...under sytem > general setup > dns servers?
...services > DNS resolver? (Active? )

Gertjan

@darkcorner said in New installation, but no DNS with DHCP:

I made a fresh installation of pfSense on a PC.

Or, do a fresh install again.
And I give you a special task :
You are allowed and advised to change the pfSense host name and domain name.
You are allowed and advised to change the default password.
Every where else : no exception : change./add nothing.

Keep the LAN network settings on 192.168.1.1/24 - if you sue an upstream (ISP) router, and it is also using 192.168.1.1/24 on its LAN, then change the (ISP) router I to, for example, 192.168.2.1/24.

Without any surprise : your issue is gone. DNS works perfectly well now.
( live becomes easier as soon as you forget about "8.8.8.8 and 8.8.4.4" etc ^^ )

You will see that a device connected on the pfSense LAN gets an IP from 192.168.1.x/24 and the gateway and DNS will be 192.168.1.1 == pfSense.
On pfSense, the Resolver will listen on 192.168.1.1, port 53, UDP and TCP.
The Resolver will do its work just fine (and no, it doesn't need 8.8.8 or whatever to do so).

darkcorner

@gertjan
I made several attempts, all reinstalling pfSense from scratch.
I cannot change the IP address of the router because other devices are connecting to this one.
So I am forced to leave 192.168.1.254 as the router address and its DHCP assigns 192.168.1.2 to the MAC Address of the NIC WAN (Intel I211).
But too many strange things happen and I can't figure out if it's the responsibility of Win11 or the router of the new ISP.
Sometimes the gateway of pfSense is "pending" and other times the NIC LAN of the PC is not passed the DNS (in pfSense it is 192.168.1.254 + 8.8.8.8 + 8.8.4.4).
The only way to stabilize the connection is to enter the two Google DNS in the LAN DHCP Server.
And I am also tempted to set the WAN address as static.

the other

@darkcorner
hey there,
just to clarifiy it...
you have another router besides pfsense (ISP > Router 1 > pfsense on PC?)

You should indeed handle WAN (and other interfaces) with fixed IPs.

So:
your router 1 has IP 192.168.1.1?
your pfsense WAN has 192.168.1.254?

It should work out of the box, just as @Gertjan said...

darkcorner

@the-other
ISP Router has IP Address 192.168.1.254.
At the bottom there is the Win IPConfig when I am connected both to the LAN cable (the network managed by pfSense), and with the WiFi directly to the router.
The pfSense DHCP assigns the IP address 192.168.1.2 to the NIC WAN and 192.168.18.51 to my PC , while the router assigns the IP address 192.168.1.3 to the WiFi card of my PC.
The nexxt name you see in "Elenco di di ricerca suffissi DNS" is the router name.

I usually only use the LAN cable. I also have WiFi access for emergencies or when I want to create separate access to virtual machines.

ipconfig /all

Configurazione IP di Windows

  Nome host . . . . . . . . . . . . . . : PC-X570
  Suffisso DNS primario . . . . . . . . :
  Tipo nodo . . . . . . . . . . . . . . : Ibrido
  Routing IP abilitato. . . . . . . . . : No
  Proxy WINS abilitato . . . . . . . .  : No
  Elenco di ricerca suffissi DNS. . . . : mydomain.local
                                          nexxt

Scheda Ethernet Ethernet:

  Stato supporto. . . . . . . . . . . . : Supporto disconnesso
  Suffisso DNS specifico per connessione:
  Descrizione . . . . . . . . . . . . . : Intel(R) 82576 Gigabit Dual Port Network Connection
  Indirizzo fisico. . . . . . . . . . . : 00-1B-21-26-94-ED
  DHCP abilitato. . . . . . . . . . . . : Sì
  Configurazione automatica abilitata   : Sì

Scheda Ethernet Ethernet 2:

  Stato supporto. . . . . . . . . . . . : Supporto disconnesso
  Suffisso DNS specifico per connessione:
  Descrizione . . . . . . . . . . . . . : Intel(R) 82576 Gigabit Dual Port Network Connection #2
  Indirizzo fisico. . . . . . . . . . . : 00-1B-21-26-94-EC
  DHCP abilitato. . . . . . . . . . . . : Sì
  Configurazione automatica abilitata   : Sì

Scheda sconosciuta OpenVPN Wintun:

  Stato supporto. . . . . . . . . . . . : Supporto disconnesso
  Suffisso DNS specifico per connessione:
  Descrizione . . . . . . . . . . . . . : Wintun Userspace Tunnel
  Indirizzo fisico. . . . . . . . . . . :
  DHCP abilitato. . . . . . . . . . . . : No
  Configurazione automatica abilitata   : Sì

Scheda Ethernet Ethernet 3:

  Suffisso DNS specifico per connessione: mydomain.local
  Descrizione . . . . . . . . . . . . . : Intel(R) I211 Gigabit Network Connection
  Indirizzo fisico. . . . . . . . . . . : A8-A1-59-AE-48-4C
  DHCP abilitato. . . . . . . . . . . . : Sì
  Configurazione automatica abilitata   : Sì
  Indirizzo IPv6 locale rispetto al collegamento . : fe80::148:f4d6:80e6:8de1%16(Preferenziale)
  Indirizzo IPv4. . . . . . . . . . . . : 192.168.18.51(Preferenziale)
  Subnet mask . . . . . . . . . . . . . : 255.255.255.0
  Lease ottenuto. . . . . . . . . . . . : venerdì 12 agosto 2022 12:34:32
  Scadenza lease . . . . . . . . . . .  : venerdì 12 agosto 2022 16:41:34
  Gateway predefinito . . . . . . . . . : fe80::1278:d2ff:fee8:d2b5%16
                                          192.168.18.1
  Server DHCP . . . . . . . . . . . . . : 192.168.18.1
  IAID DHCPv6 . . . . . . . . . . . : 279486809
  DUID Client DHCPv6. . . . . . . . : 00-01-00-01-2A-80-2F-4D-20-C1-9B-8B-45-4D
  Server DNS . . . . . . . . . . . . .  : 8.8.8.8
                                          8.8.4.4
  NetBIOS su TCP/IP . . . . . . . . . . : Attivato
  Elenco di ricerca suffissi DNS specifici della connessione:
                                          mydomain.local

Scheda sconosciuta Connessione alla rete locale (LAN):

  Stato supporto. . . . . . . . . . . . : Supporto disconnesso
  Suffisso DNS specifico per connessione:
  Descrizione . . . . . . . . . . . . . : TAP-Windows Adapter V9
  Indirizzo fisico. . . . . . . . . . . : 00-FF-13-E7-BE-0E
  DHCP abilitato. . . . . . . . . . . . : Sì
  Configurazione automatica abilitata   : Sì

Scheda LAN wireless Connessione alla rete locale (LAN)* 9:

  Stato supporto. . . . . . . . . . . . : Supporto disconnesso
  Suffisso DNS specifico per connessione:
  Descrizione . . . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
  Indirizzo fisico. . . . . . . . . . . : 20-C1-9B-8B-45-4E
  DHCP abilitato. . . . . . . . . . . . : Sì
  Configurazione automatica abilitata   : Sì

Scheda LAN wireless Connessione alla rete locale (LAN)* 10:

  Stato supporto. . . . . . . . . . . . : Supporto disconnesso
  Suffisso DNS specifico per connessione:
  Descrizione . . . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
  Indirizzo fisico. . . . . . . . . . . : 22-C1-9B-8B-45-4D
  DHCP abilitato. . . . . . . . . . . . : Sì
  Configurazione automatica abilitata   : Sì

Scheda Ethernet VMware Network Adapter VMnet1:

  Suffisso DNS specifico per connessione:
  Descrizione . . . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1
  Indirizzo fisico. . . . . . . . . . . : 00-50-56-C0-00-01
  DHCP abilitato. . . . . . . . . . . . : Sì
  Configurazione automatica abilitata   : Sì
  Indirizzo IPv6 locale rispetto al collegamento . : fe80::30df:582f:710a:5453%9(Preferenziale)
  Indirizzo IPv4. . . . . . . . . . . . : 192.168.131.1(Preferenziale)
  Subnet mask . . . . . . . . . . . . . : 255.255.255.0
  Lease ottenuto. . . . . . . . . . . . : venerdì 12 agosto 2022 12:33:38
  Scadenza lease . . . . . . . . . . .  : venerdì 12 agosto 2022 15:56:38
  Gateway predefinito . . . . . . . . . :
  Server DHCP . . . . . . . . . . . . . : 192.168.131.254
  IAID DHCPv6 . . . . . . . . . . . : 1073762390
  DUID Client DHCPv6. . . . . . . . : 00-01-00-01-2A-80-2F-4D-20-C1-9B-8B-45-4D
  NetBIOS su TCP/IP . . . . . . . . . . : Attivato

Scheda Ethernet VMware Network Adapter VMnet8:

  Suffisso DNS specifico per connessione:
  Descrizione . . . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8
  Indirizzo fisico. . . . . . . . . . . : 00-50-56-C0-00-08
  DHCP abilitato. . . . . . . . . . . . : Sì
  Configurazione automatica abilitata   : Sì
  Indirizzo IPv6 locale rispetto al collegamento . : fe80::7806:4ca0:e717:7589%7(Preferenziale)
  Indirizzo IPv4. . . . . . . . . . . . : 192.168.230.1(Preferenziale)
  Subnet mask . . . . . . . . . . . . . : 255.255.255.0
  Lease ottenuto. . . . . . . . . . . . : venerdì 12 agosto 2022 12:33:41
  Scadenza lease . . . . . . . . . . .  : venerdì 12 agosto 2022 15:56:42
  Gateway predefinito . . . . . . . . . :
  Server DHCP . . . . . . . . . . . . . : 192.168.230.254
  IAID DHCPv6 . . . . . . . . . . . : 1090539606
  DUID Client DHCPv6. . . . . . . . : 00-01-00-01-2A-80-2F-4D-20-C1-9B-8B-45-4D
  Server WINS primario . . . . . . . .  : 192.168.230.2
  NetBIOS su TCP/IP . . . . . . . . . . : Attivato

Scheda LAN wireless Wi-Fi:

  Suffisso DNS specifico per connessione: nexxt
  Descrizione . . . . . . . . . . . . . : Intel(R) Wi-Fi 6 AX200 160MHz
  Indirizzo fisico. . . . . . . . . . . : 20-C1-9B-8B-45-4D
  DHCP abilitato. . . . . . . . . . . . : Sì
  Configurazione automatica abilitata   : Sì
  Indirizzo IPv6 . . . . . . . . . . . . . . . . . : 2001:b07:6472:8daf:f134:a567:8ac1:aed3(Preferenziale)
  Indirizzo IPv6 temporaneo. . . . . . . . . . . . : 2001:b07:6472:8daf:60cd:86c4:c64e:1b74(Preferenziale)
  Indirizzo IPv6 locale rispetto al collegamento . : fe80::f134:a567:8ac1:aed3%17(Preferenziale)
  Indirizzo IPv4. . . . . . . . . . . . : 192.168.1.3(Preferenziale)
  Subnet mask . . . . . . . . . . . . . : 255.255.255.0
  Lease ottenuto. . . . . . . . . . . . : venerdì 12 agosto 2022 12:35:47
  Scadenza lease . . . . . . . . . . .  : sabato 13 agosto 2022 15:32:16
  Gateway predefinito . . . . . . . . . : fe80::4a3e:5eff:fe22:b3b0%17
                                          192.168.1.254
  Server DHCP . . . . . . . . . . . . . : 192.168.1.254
  IAID DHCPv6 . . . . . . . . . . . : 287359387
  DUID Client DHCPv6. . . . . . . . : 00-01-00-01-2A-80-2F-4D-20-C1-9B-8B-45-4D
  Server DNS . . . . . . . . . . . . .  : 2001:b07:6472:8daf:4a3e:5eff:fe22:b3b0
                                          192.168.1.254
  NetBIOS su TCP/IP . . . . . . . . . . : Attivato

darkcorner

I did a fresh installation from scratch and also asked my ISP to intervene on its configuration.
No useful results.
The only way to have DNS on PCs is to report it in the DHCP server configuration.
Or alternatively it is to set DNS Query Forwarding to "Enable Forwarding Mode"