Two utilities worth noting here, changeip and scutil. You can check if your name and hostname match using changeip. It will look at the DNS and look at the name your system has for itself and let you know if they match: changeip -checkhostname You can also use scutil to see what the hostname is: scutil –getHostName If you want to change the hostname: scutil –setHostName <new hostname> With the DNS, if the name server runs on the system you’re sitting at then you can edit the zone files on that system. Use dig to check whether the name matches the hostname. Think FQDN here btw, with Server…
-
-
Network Solutions Zone File Corruption
If you see a lot of subdomains that are actually other people’s domain names in your DNS records for NetSol then you can either delete them or call and open a ticket with NetSol. This is zone file corruption on their side.
-
Xsan: Unresponsive Xsan Admin
There are times with Xsan when the admin utility sits unresponsive (the pinwheel at the bottom of the screen spins annoyingly to no end). When the Admin tool gets unresponsive you are typically staring down the barrel of some kind of naming issue. In these cases I almost universally have DNS administrators tell me that everything is fine without first bothering to actually look at the records for the hosts on the SAN. The easy way to verify this hypothesis is to build a custom hosts file (/etc/hosts). This bypasses the DNS resolver and if everything loads up correctly then you do indeed have a DNS/host naming issue.
-
Xsan Admin slow to respond?
It’s probably a naming or DNS issue… As a temp test, create a hosts file with all the systems in it. If it works fine then try and isolate that DNS issue…
-
Dual Chroot'd DNS Servers
Sweet: http://www.etherboy.com/dns/chrootdns.html