Search Results

Search found 4 results on 1 pages for 'notpeter'.

Page 1/1 | 1 

  • Simple recursive DNS resolver for debugging (app or VM)

    - by notpeter
    I have an issue which I believe is caused by incorrect DNS queries (doubled subdomains like _record.host.subdomain.tld.subdomain.tld) when querying for SRV records. So I need to an alternate DNS server with heavy logging so I can see every query (especially stupid ones), acting as a recursive resolver with the ability create records which override real DNS records so I can not only find the records it's (wrongly) looking for, but populate those records as well. I know I could install a DNS server on yet another linux box, but I feel like this is the sort of thing that someone may already setup a simple python script or single use vm just for this purpose.

    Read the article

  • Mac OSX Server - Mac Mini to XServe Migration

    - by notpeter
    If I build out a Mac OSX Server install on a Mac Mini and then when it's ready for production I image the disks to an XServe, is there any reason the resulting system won't just work? Assuming I'm able to keep the same IP address are there any other issues I should be aware of? I'll be running minimal services, just AFP, SMB and Open Directory. TMI: My Intel XServe is full of cruft. Was originally a G4 XServe running 10.3, upgraded to 10.4 then migrated to 10.5 on the Intel XServe. I'd like a clean start, but can't spare the XServe downtime while I build out the install, can I just use a Mac Mini for dev and then switch to the XServe for production.

    Read the article

  • Netboot Intel Macs without BSDP

    - by notpeter
    I have a netboot setup with DeployStudio that works great in my lab, but doesn't work on our main network. After some digging, I believe it's because our network admins are filtering BSDP (Boot Service Discovery Protocol) on our subnet at the switch level. Is it possible to hard code which server my clients (early 2007 iMac Core2Duos) should boot from without relying on BSDP? Perhaps relevant details: I do not have control over switch configs or DHCP settings. Client and server are running 10.6 Snow Leopard. The clients see the netboot server advertising itself in the 'Startup Disk' system preferences pane, but when I go to netboot it just leaves me with a flashing globe.

    Read the article

  • Disk names in Solaris 10 for ZFS: SAS WWN instead of c0t0d0

    - by notpeter
    I currently have a server running Solaris 10u9 with a SAS enclosure (Dell PowerVault MD1000) filled with SATA disks attached to an SAS card (LSI 3801E). It happily recognizes the 15 disks in the MD1000 and presents them each disk in the traditional solaris form (c1t12d0, c1t13d0, c1t15d0, etc). My home ZFS setup (Nexenta CP3 + LSI 9200-16E + directly cabled SATA disks) presents disks as their SAS WWN ID (ex: c3t600039300001EA56d0). Although this ID is longer, I've found it much easier to troubleshoot because the cabling/slot is irrelevant, ZFS just identifies the disk by ID, if it's connected it finds it. Most manufacturers print the WWN right on the disk's top label, can't get much easier than that. So how can I get Solaris to identify disks by SAS WWN instead of by the cXtXdX?

    Read the article

1