Alright I’m back (a day late). We’re trying to move fast with this so I’ve gone ahead and began building the FOG server on our production side. Again though, I’m stuck on breaking DNS once DNSMasq is installed. I don’t remember how I got around this before to do the DNSMasq build/upgrade to 2.76 unfortunately…
You had mentioned disabling dnsmasq from taking over DNS through ltsp.conf. Here is my current running ltsp.conf:
Don't function as a DNS server: port=0 # Log lots of extra information about DHCP transactions. log-dhcp # Set the root directory for files available via FTP. tftp-root=/tftpboot # Disable re-use of the DHCP servername and filename fields as extra # option space. That's to avoid confusing some old or broken DHCP clients. dhcp-no-override # inspect the vendor class string and match the text to set the tag dhcp-vendorclass=BIOS,PXEClient:Arch:00000 dhcp-vendorclass=UEFI32,PXEClient:Arch:00006 dhcp-vendorclass=UEFI,PXEClient:Arch:00007 dhcp-vendorclass=UEFI64,PXEClient:Arch:00009 dhcp-match=set:ParallelsEFI,97,00:ef:e3:6d:16:10:6f:46:9d:87:12:5a:12:c2 # Set the boot file name based on the matching tag from the vendor class (above) dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,,10.100.10.22 dhcp-boot=net:UEFI,ipxe.efi,,10.100.10.22 dhcp-boot=net:UEFI64,ipxe.efi,,10.100.10.22 dhcp-boot=tag:UEFI,tag:ParallelsEFI,intel.efi,10.100.10.22,10.100.10.22 # The boot filename, Server name, Server Ip Address dhcp-boot=undionly.kpxe,,10.100.10.22 # PXE menu. The first part is the text displayed to the user. The second is t$ pxe-prompt="Booting FOG!",1 pxe-service=X86PC, "Boot to FOG", undionly.kpxe pxe-service=X86-64_EFI, "Boot to FOG UEFI", ipxe.efi pxe-service=BC_EFI, "Boot to FOG UEFI PXE-BC", ipxe.efi dhcp-range=10.100.10.22,proxy
Here is my NetworkManager.conf where I removed the “DNS=DNSMASQ” line:
[main] plugins=ifupdown,keyfile,ofono [ifupdown] managed=false
I noticed that I get a new connection named en32 when I install DNSMasq (or somewhere along the lines of installing FOG and DNSMasq). I went in that connections settings and saw 127.0.0.1 as the DNS entries so I updated them to our proper DNS entries, reset networkmanager and dnsmasq services, but still could not ping google but 220.127.116.11 pinged fine. Any ideas?