6 Replies Latest reply: Aug 4, 2010 4:12 AM by Andrew-ACT-ACSA
dandoeskorea Level 1 Level 1 (5 points)
Hello all,

Could someone please tell me whether it's normal for the 'Search Domains:' box (System Preferences > Network > Airport > Advanced... > DNS) to be empty on all of my client Macs that are connecting locally to a DNS server (Mac Mini running OS X Server 10.6.3) on a LAN configured thus: -

Server (Mac Mini running OS X Server 10.6.3, hosting AFP, DNS, OD, SMB & VPN)
Manual IP: 10.0.0.254
Subnet: 255.255.255.0
Router: 10.0.0.1
DNS Servers: 10.0.0.254
Search Domains: mydomain.co.uk

Router (acting as the sole DHCP server)
LAN IP: 10.0.0.1
LAN Subnet: 255.255.255.0
DNS Servers: 10.0.0.254

Wireless access point (Apple Airport Extreme Base Station)
Manual IP: 10.0.0.11
Subnet: 255.255.255.0
Router: 10.0.0.1
DNS Servers: 10.0.0.254
Domain Name: mydomain.co.uk

Client machines (all Apple MacBook Pro laptops running OS X 10.6.3, connecting via Airport, using DHCP)
DNS Servers: 10.0.0.254 (auto-populated in grey)

Everything else works perfectly, however I would like the ability to type a short local URL - e.g. router, rather than router.mydomain.co.uk - at client level as well as server level (obviously with the server having a manually inputted search domain, the short URLs work within it's own web browser, but not at client level).

Is there a way to fix this? Am I missing something simple? Any help would be greatly appreciated.

Many thanks.

Dan.

13" MacBook Pro 2.26 GHz Intel Core 2 Duo, Mac OS X (10.6.3)
  • 1. Re: 'Search Domains:' box is blank on all client Macs
    MrHoffman Level 6 Level 6 (12,470 points)
    What did DHCP provide as the domain?
    Server Admin > select server > DHCP > Subnets > select a subnet > DNS
  • 2. Re: 'Search Domains:' box is blank on all client Macs
    dandoeskorea Level 1 Level 1 (5 points)
    Hi MrHoffman, thanks for responding.

    DHCP is being handled by the router however, if I add the DHCP service in Server Admin (but don't start it) the Subnets' DNS Search Domains entry is: no-dns-available.example.com

    I also notice that the DNS Servers shown here are incorrect (they show as my old ISP's DNS servers).

    So I now have a new question. If I change the entries here to the following: -

    DNS Servers: 10.0.0.254
    Search Domains: mydomain.co.uk

    ...and save these setting, even though the DHCP service will remain as stopped (I'd like it to continue running off the router) will it make a difference?

    Thanks again.

    Dan.
  • 3. Re: 'Search Domains:' box is blank on all client Macs
    MrHoffman Level 6 Level 6 (12,470 points)
    The Mac OS X Server DHCP server is not relevant here, and changing the settings there will not effect changes to your current client configuration issues.

    Your clients are acquiring their DHCP information from your firewall router.

    Your router's DHCP server is dispensing the problematic information, and you will want to reconfigure that device to match your current requirements, or you will want to migrate your DHCP services from the router to the DHCP server on Mac OS X Server or another DHCP server; to another DHCP server that has been configured to meet your needs.
  • 4. Re: 'Search Domains:' box is blank on all client Macs
    dandoeskorea Level 1 Level 1 (5 points)
    I understand. Yes, my firewall router is also my DHCP server and it seems there is no option to add a search domain within it's configuration. As long as I retain this setup I'll just live with it. If it becomes more of an issue I'll consider moving DHCP to the server instead.

    Thanks for all your help MrHoffman.

    Dan.
  • 5. Re: 'Search Domains:' box is blank on all client Macs
    Kostas B Level 1 Level 1 (90 points)
    You should definately move the DHCP to the server.
  • 6. Re: 'Search Domains:' box is blank on all client Macs
    Andrew-ACT-ACSA Level 2 Level 2 (350 points)
    What type of router is it? I doubt that it won't do search domains... it probably just doesn't offer a config for it in its DHCP setup. It's DHCP service will inherit the DNS domain set elsewhere within the router's config.

    While switching to using your OS X Server for DHCP opens up some possibilities it also gives you a single point of failure. So consider carefully if you really need what the OS X Server's DHCP offers.