Opened 8 months ago

Closed 7 months ago

#1115 closed System Defect (3rdpartybug)

Manual DNS configuration is not applied correctly

Reported by: Peter2121 Owned by: ken
Priority: major Milestone:
Component: Network Manager Version: 10.0-RELEASE
Keywords: Cc: trac-bugs@…

Description

I have two NICs on my PC, only one is enabled.
I have the static IP v4 at the active NIC. The configuration has done using PCBSD Control Panel application. DNS servers, search domain and custom gateway are configured. IP v6 is disabled.

The DNS parameters (IP addresses of DNS servers) and Search Domain are not applied after the reboot of PC. The parameters are still present in Network Manager but not in resolv.conf:
cat /etc/resolv.conf
# Generated by resolvconf
search localdomain

DNS name resolution does not work.

Change History (2)

comment:1 Changed 7 months ago by joshms

  • Owner set to ken

comment:2 Changed 7 months ago by kenmoore

  • Resolution set to 3rdpartybug
  • Status changed from new to closed

I just tested this out after a new installation of 10.0.2-PRELEASE, and the network manager appears to be working properly.
I have tried multiple variations of custom DNS values, custom gateway (which goes in /etc/rc.conf), and custom search domain.

The only strange thing I noticed was that after a reboot of the computer, the custom DNS settings were intact but the custom search domain was lost (probably because something in the network stack determined that the search domain was junk and removed it during bootup).
After repeating the procedure with the custom search domain set to "localdomain" (as you had in your report) I was able to repeat this behavior.

This seems to imply that it is something in the base FreeBSD network stack that is changing the settings as it deems appropriate rather than an error in the PC-BSD network configuration utility.

Please open a ticket with the FreeBSD network team about this, or ask about it on one of the FreeBSD mailing lists.

Here was my /etc/resolve.conf files before/after rebooting in case anyone wants to replicate this behavior.

pre-reboot:

# Generated by resolvconf
nameserver 8.8.8.8
nameserver 208.67.220.220

search localdomain

post-reboot:

# Generated by resolvconf
nameserver 8.8.8.8
nameserver 208.67.220.220
Note: See TracTickets for help on using tickets.