Solved FreeBSD behind Router-PC fails resolving Name

Hi Folks,
new here. I've searched and searched incl. the Manuals, but i couldn't find a working sample.
I'm completely new to FreeBSD, so i'm kind of stumped.
I have a setup as seen in Figure 1 here: https://www.freebsd.org/doc/el_GR.ISO8859-7/books/handbook/network-natd.html
(Is that Greek? - I couldn't find that graphic in the english version)
That graphic describes my setup to the dot.
Problem: My FreeBSD-Machine is "Client A" acc. to that image (All examples i could find pertain to Client B and how to set up FreeBSD to act as router)
Client B (the "Gateway") is a Debian-Machine, and i know for a fact, that that one is correctly configured, since my other Linux-Machines (imagine them being Client A) can reach the Internet with, say ping www.google.de
NIC "re0" has DHCP in /etc/rc.conf and it gets a valid IP-Address 192.168.3.53/24 from my Debian-Machine (which runs ISC-DHCP-Server)
On my FreeBSD-Machine (Client A) i can ping by IP-Address my debian-machine (192.168.3.1) as well as my Internet-Router (192.168.2.1).
I can also ping 8.8.8.8 (meaning it can reach out), but ping www.google.com fails

As i said: On my other Machines i can ping www.google.com, and it resolves correctly the names.

Help?
In the first step, what i can't figure out, if it's a Problem on my Debian or on my FreeBSD-Machine.

FreeBSD 12.1-p2 on Client A
Debian 10 on Client B
 
Last edited:
Woah!!
I definitely had entries in /etc/resolv.conf, but they are gone?!?!!?
And yes, i did save (nano - CTRL+O)

But any way: Thank you for pointing me in the right direction. After some research i found out:
I wasn't aware, that dhclient overwrites my /etc/resolv.conf with a kinda "blank" file (just the "search"-Entry)
An entry in /etc/dhclient.conf
Code:
interface "re0" {
    supersede domain-name-servers 192.168.3.1, 192.168.2.1;}
Solved it!
Thanx!
 
Last edited:
Sir Dice, thx.
Sorry for late reply. was busy with real life --> anyone familiar with it? ;-)
I know that with the DNS settings.
My current setup is local at home, where my router only has wifi and no LAN, and the old rustbucket i'm running FreeBSD on has no Wifi (yes, i know about USB-WIfi-Dongles), so i've been running it with my Laptop as Router/Gateway.
At the location the machine will be running at in the future, it will be connected via LAN-wire directly with the router, and will get all necessary settings from it (DHCP with fixed IP-Address, DNS, all the toys).
 
Back
Top