You'll notice that /etc/resolv.conf contains dire warners on most Linux Desktops. # This file is managed by man:systemd-resolved(8). Do not edit. # # This is a dynamic resolv.conf file for connecting local clients to the # internal DNS stub resolver of systemd-resolved. This file lists all # configured search domains. # # Run "resolvectl status" to see details about the uplink DNS servers # currently in use........

Create your netplan file vi /etc/netplan/01-netcfg.yaml network: version: 2 renderer: networkd ethernets: ens3: dhcp4: no ........

First we need to create dhclient.conf if it doesn't exist or edit it: vi /etc/dhclient/dhclient.conf #add this line at the top add the IPs as commas they will be the highest priority nameservers and whatever your ISP gives you will be used after these one (good for DNS backup) prepend domain-name-servers 127.0.0.1,10.10.25.8; After you restart your network or run dhclient again you should see the contents of........

Go to: "Server Configuration" -> Basic cPanel & WHM Setup Scroll to: "Nameservers" (at the bottom) From there you can set the names of the nameserver and their IPs. It's very weird and confusing that nothing under IP Functions/DNS has or links to this.........

CPanel ->Basic cPanel &WHMSetup At the bottom you'll see them, set the nameservers you want to use and the corresponding A record if needed. Then all new domains will use those settings/nameservers. It's strange that there's no section for this specifically.........

http://support.godaddy.com/help/article/668/registering-your-own-nameservershosts?pc_split_value=1 Log in to your GoDaddy Account. Click on "My Account" at the top left. Click on "Domains". Click on the "Launch" button for the domain you want to create the nameservers for. Find........

I don't expect this to be solved soon but some of Yahoo's DNS servers are out of whack. I changed the IPs of some nameservers of some domains and now most Yahoo users can't e-mail to those domains! As you can see below by the "No MX or A records for mychangedomain.com", now Yahoo's DNS/mailserver DNS cache is wrong. You would think they would at least have cached the old incorrect records, but instead for some reason their DNS cache has no entry and doesn't seem........

genuine.com/IN: loading master file genuine.com.zone: file not found _default/genuine.com/IN: file not found I always found it silly that no one really talks about this and apparently many like me and even control panels like Plesk were still using hard paths. I always thought "why can't I just specify the name of the zone file and have bind find it". Surely the default search path must be /var/named or somewhere else but there is no such thing.........