Name does not resolve error / DNS issue

F

freesbsd

I am unable to ping google.com, but able to ping multiple other IP address including google with no problem.
1714257119137.png


This is my resolv.conf file
1714257159348.png


rc.conf file
1714257189235.png
 
So, either find out why 192.168.54.71 does not resolve hostnames (you did not specify what lives at that address), or use your gateway IP (which is usually a router/modem with a resolver built in), or change your nameserver to 8.8.8.8 and see if resolving works then.
 
You need to add the -4 command switch so that it will only try IPv4:
ping -4 google.com
Otherwise, ping will use whatever address the target resolves to, IPv4 or IPv6.
You can create an alias for this in your profile.
 
I tried doing this, but I still seem to be getting the same error. The screenshots are from vmware, and yes it seems to work when I resolve the nameserver to use google's server within resolv.conf. I'm just now realizing the issue lies in my openbsd, the 192.168.54.71 address, which is now also unable to ping google.com, even though it was able to before.
1714342254338.png


I feel as though the issue lies in this file, and I have on idea how I'd be able to fix it.
1714342745626.png
 

Attachments

  • 1714342548520.png
    1714342548520.png
    61.3 KB · Views: 8
freesbsd said:
vmware
Click to expand...

Thanks.


OT, I learnt to ignore ping not working in VirtualBox guests – if the failing ping was for a website that concurrently worked normally with a web browser in the same guest (somewhat contrary to the ping). I was, still am, too lazy to investigate properly :)
 
You must log in or register to reply here.
Back
Top