D-Link fouls up DNS

I am running 10.5.1 on an iBook G4 with 1.5 GB Ram.
My flatmate purchased an ADSL2 router (I assume it is also a DSL modem, though it doesn't say this on the box). A telephone cable runs from the wall to this router. It is not wireless. When I plug my iBook into this router using a LAN cable all is well. A DNS server address of 192.168.1.254 shows up in my network prefs with 'home.gateway' as the search domain. TPC/IP settings are set to: 'using DHCP' with automatic address. Again, the internet works fine and the speed is fine.
Here's the thing...
I bought a D-Link wireless router (DI-524, 802.11g) thinking I could use it as a modem, that is, run the telephone cable from the wall into the D-Link router. Of course, I quickly realized you can't. So what I did was run a LAN cable from the first (non-wireless) router/modem to the D-link wireless router. It seemed to work flawlessly. My flatmates PC laptop works fine when connected wirelessly, in fact. And, I didn't even need to really tweak any of the details in the D-link settings, except to put a password on it on the connection.
But then when I connect to the wireless router I can't seem to open some web pages. This is particularly so for webpages that require some sort of info to be sent, such as signing on to hotmail. For example, the only way I can use this site (logging in, posting this question, etc.) is by connecting with a LAN cable to the ADSL non-wireless modem/router and bypassing the D-link. If I use the wireless D-link router then I get an error message on Safari saying:
"Safari can’t open the page “http://discussions.apple.com/post!default.jspa?forumID=1222” because the server unexpectedly dropped the connection, which sometimes occurs when the server is busy. You might be able to open the page later."
I also notice that, for example, when I type in www.hotmail.com, I get sent to a different MSN site, not the original hotmail sign-in. And then, when I try to sign it, it stalls again. So, this got me thinking that it might be the DNS. Under Airport, in my network prefs, I cannot change the DNS addresses. They are "grayed out" so as to make it impossible to remove them, or alter their order. This seemed suspicious to me, but I'm at a loss for how to fix any of this.
Bottom line is this: when using the wireless connection through the D-Link router my internet is sketchy, with some webpages (especially those requiring forms like ebay.com) not loading. When I bypass the D-link router, all is fine. Even more confusing is that my flatmates PC laptop loads all pages fine while connected to the D-link wireless router.
Any help is greatly appreciated...

Three Things come to mind immediately:
1. Make certain that your ADSL modem is in "bridged ethernet mode", not PPPOE. Turn OFF DHCP on the ADSL modem, then use your wired router setup to establish the PPOE connection with username and password. Usually you need to connect direct from the computer to the ADSL modem with an ethernet cable and navigate to 192.168.1.254 with your browser, but that address may vary. Bridged ethernet settings are usually under advanced settings.
2. Turn ON DHCP on the wired router
3. In the wireless router turn OFF DHCP.
You can only have one DHCP server on the LAN
Hope this helps
Peter

Similar Messages

Link aggregation and DNS

Brand new Xserve intel
link aggregation turn on two network cards works great.
DNS is running but when testing i dont' resolve his own adres
Link aggregation off DNS works
What goes wrong ?
thanks

You mean if the DNS server is running on the same machine you can no longer use it if bonding the interfaces?
I only know I saw a problem when I used 127.0.0.1 as the nameserver address in Network settings on the bonded interface. Users that always get the same "macaddress locked" static IP from the DHCP server, running in the same machine, got that as the nameserver IP (from the machine's Network setting) instead of from the ones in DHCP config.
(The DHCP server config also needed to be altered to serve on the bond0 interface).
And I think the info in /etc/named.conf "to only use 127.0.0.1" is, you should only allow for alterations of DNS server settings from that IP and maybe not that you should use it as the IP in Network settings.

Link Aggregate vs DNS

Recently, I installed Leopard Server on 3 XServes for our school. With Tiger Server, link aggregation on the XServe running DNS and ODM worked great. Once we migrated to Leopard Server, DNS just went flakey with a link aggregate bonded Ethernet setup. I am using a new HP ProCurve 2824 with the latest firmware applied to the switch.
The workaround was to split the link aggregate to the two separated Ethernet NICs.
I am wondering if this is a known bug in Leopard Server? My other Leopard Server setups not running DNS are performing great with link aggregation setup.

Just a NOTE of happenstance.

Link Aggregate and DNS

I have set up my Xserve with a Link aggregate to provide more bandwidth for my software updates. Part of the Link Aggregation is assigning each NIC with a self-assigned IP address. This server is also bound to an Windows 2003 Active Directory domain. My problem is that this self-assigned IP address is somehow getting published to our (Windows) DNS servers. Needless to say this causes a lot of resolution errors.
Is there a way to prevent this on the Xserve side, or is it a setting on the DNS server that needs to be changed?

As background, each test I did with Ling Aggregation set a self-assigned IP address on the NICs. The Configure field is set to DHCP on the NICs, while the bonded interface has a manually set IP. What can I set that field to without deactivating the NIC?
UPDATE:
OK, I never tried setting the NICs' Configure setting to OFF. I just did that on another machine and noticed that the bonded interface still worked.
Thanks
Message was edited by: Sean Mcgarrahan

Non-ISP DDNS with Apple DHCP and DNS Services

I have two questions about Dynamic DNS (DDNS) as it applies to Apple's DNS and DHCP services within my home network. I am not talking about DDNS in the context of making my external-facing router available by a domain name on the Internet using the dynamically-assigned IP from my ISP.
Starting with Snow Leopard Server, I attempted to use Apple's DNS and DHCP services (I have the firmware-based DHCP service in my router turned off.) The difficulty I immediately faced was that Apple's DHCP implementation didn't update the DNS service as IPs were handed out to DHCP clients. Because of this, it wasn't possible to access hosts by their hostname, since getting a DHCP-assigned dynamic IP at boot-up didn't do anything to automagically register the hostname-to-IP mapping in DNS. Manually registering the hostname in DNS was pointless, becuase over time the client IP address can and did change. I could create static IP assignments based on the MAC address, but doing that for all of the devices on my home network sort of defeated the purpose of using dynamic IPs.
The only solution I eventually found was to go out and get an open source DHCP server, compile it for my Mac, install it, and configure it. After doing this, everything worked great; every time a new host or other device was booted it got a dynamic IP through DHCP, and then the DHCP server automatically updated Apple's DNS serive with the hostname and assigned IP. I could immediately access every device on my network by hostname. As IP addresses changed over time, the hostname-to-IP mapping in DNS was automatically updated.
Except, Apple's point upgrades kept breaking my non-Apple DHCP install. Every time I applied software updates to my server I had to go back and re-finagle DHCP to get it to automatically start and run. By the time Lion Server came out, I drank the Kool-Aid and went back to Apple's DHCP implementation. I was disappointed that it still didn't seem able to update DNS with hostnames as it assigned IPs, but I was so tired of mucking about at the command prompt to fix DHCP every time Software Updates broke it, I just lived with the inconvenience of not being able to access devices on my network by hostname.
I'm sorry to say this, but Windows Server has had this capability since at least server 2003. In fact, until I dumped my Windows Server and switched to Snow Leopard Server, I was running Microsoft's DNS and DHCP services on Server 2003 and they did exactly what I'm describing brilliantly.
Can anyone offer any advice here? Does Mountain Lion's implementation of DHCP allow for DDNS updates to the DNS service? If not, how are other people handling this? Should I go back to running Windows Server for my DNS and DHCP services? My Netgear WNDR3700 router appears to have the standard, substandard DHCP server in firmware as most home routers, and no facility for DNS at all--much less the ability to update an on-site DNS sever with IP addresess it hands out. In fact, the only appliance I know of that does this is the InfoBlox my employer uses, but that's too expensive for a home solution.
As a Post Script, I'll add that I've been VERY unhappy that I lost the ability to bind Windows clients to Open Directory under Lion Server. Since I'm starting to see articles that say this capability hasn't been added back to Mountain Lion Server, I'm seriously considering implementing a Windows Server AD master and establishing a "magic triangle" or "golden triangle". If I end up having to do that, I wonder if I might as well just go back to using Microsoft's DNS and DHCP services.

Hi,
Whether to move your DHCP to another server depends on the workload of your server. If there are too many clients on the network, you should move your DHCP to another server.
Did the record which owned by the machine generate before you configure the DnsUpdateProxy group? You can try to regenerate the record and check the result.
For more detailed information, you can view the link below.
DNS best practices
http://technet.microsoft.com/en-us/library/cc778439(v=ws.10).aspx
Using DNS servers with DHCP
http://technet.microsoft.com/en-us/library/cc787034(v=ws.10).aspx
DNS registration changes for Windows Server 2003 based DHCP Servers
http://technet.microsoft.com/en-us/library/ee441167(v=ws.10).aspx
Hope this helps.
Steven Lee
TechNet Community Support

State of DNS after Domain rename

Hi all
Still learning DNS and want to add secondary DC
I initially set this up as a mydomain.local as I believed that was best practice. When researching SSL certificates I realised that it was now supposedly best practice to use mydomain.com. I did a Domain rename which was interesting and seemed to work reasonably
well.
2012 AD DC is :
IPv4: 192.168.1.105
Computer name: name
Full Computer name: name.mydomain.local
Domain name is: mydomain.com
2012 Server RDS is: (was secondary DNS when .local)
IPv4: 192.168.1.100
Computer name: remote
Computer name: remote.mydomain.com
Domain name is: mydomain.com
I want to install Secondary DNS to the RDS server or maybe a VM on it for redundancy but am concerned my DNS is possibly a little bit dodgy.
Only issues I have is sometimes from remote “mydomain.com” will resolve to 192.168.1.100 and don’t believe this should happen but may be wrong.
Every now and again from Remote Desktop which is on 192.168.1.100 (remote.mydomain.com) web sites won’t load and you need to refresh which will normally then resolve and load.
The only other issue is every now and again autodiscover will take a while to resolve and troubleshooting that implies a timeout. MS have looked at this and didn’t see any issues in my DNS however I think that was just due to the fact that it resolved eventually.
I have include some info ipconfig on 192.168.1.100 shows DNS 192.168.1.105.
NSLOOKUP
Name:    mydomain.com
Addresses: 192.168.1.100
          192.168.1.105
> remote.mydomain.com
Server: UnKnown
Address: 192.168.1.105
Name:    remote.mydomain.com
Address: 192.168.1.100
> mydomain.local
Server: UnKnown
Address: 192.168.1.105
Name:    mydomain.local
Address: 192.168.1.105
Pings from RDS
C:\Users\administrator.MD>ping mydomain.local
Pinging mydomain.local [192.168.1.105] with 32 bytes of data:
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
C:\Users\administrator.MD>ping mydomain.com
Pinging mydomain.com [192.168.1.100] with 32 bytes of data:
Reply from 192.168.1.100: bytes=32 time<1ms TTL=128
C:\Users\administrator.MD>ping mydomain.com
Pinging mydomain.com [192.168.1.105] with 32 bytes of data:
Reply from 192.168.1.105: bytes=32 time<1ms TTL=128
DCDIAG
         The DFS Replication Event Log.
         There are warning or error events within the last 24 hours after the
         SYSVOL has been shared. Failing SYSVOL replication problems may cause
         Group Policy problems.
         A warning event occurred. EventID: 0x800008A5
            Time Generated: 05/14/2014   01:30:50
            Event String:
            The DFS Replication service stopped replication on volume C:. This occurs when a DFSR JET database is not shut down cleanly and Auto Recovery is disabled. To resolve this issue, back up the
files in the affected replicated folders, and then use the ResumeReplication WMI method to resume replication.
            Additional Information:
            Volume: C:
            GUID: A3ABE3A7-A0E5-11E2-93E8-806E6F6E6963
            Recovery Steps
            1. Back up the files in all replicated folders on the volume. Failure to do so may result in data loss due to unexpected conflict resolution during the recovery of the replicated folders.
            2. To resume the replication for this volume, use the WMI method ResumeReplication of the DfsrVolumeConfig class. For example, from an elevated command prompt, type the following command:
            wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig where volumeGuid="A3ABE3A7-A0E5-11E2-93E8-806E6F6E6963" call ResumeReplication
* Replication Latency Check
            DC=ForestDnsZones,DC=mydomain,DC=com
               Latency information for 1 entries in the vector were ignored.
                  1 were retired Invocations. 0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc. 0 had no
latency information (Win2K DC).
            DC=DomainDnsZones,DC=mydomain,DC=com

Hi,
If I understand correctly, you have two computers with the following host names and IP addresses:
1. name (192.168.1.100)
2. remote (192.168.1.105)
The first server is a domain controller. The second server is a domain member server.
Your Active Directory domain was 'mydomain.local' and you changed this to 'mydomain.com'
DNS is installed on server #1.
To avoid confusion when talking about DNS and Active Directory, you can refer to mydomain.com as your Active Directory domain, which has users and groups in it and is hosted on a domain controller. You also have a DNS forward lookup zone mydomain.com that
is used to dynamically register computers that are members of the Active Directory domain. So - when referring to Active Directory - it is a domain but when referring to DNS it is a zone. These are two separate things that are linked.
The DNS zone should have at least three A (address) records:
mydomain.com (the root of the zone)
name.mydomain.com (the DC)
remote.mydomain.com (the member server)
You should see the .100 address for the first two and the .105 address for the third. Open up DNS Manager and view the zone to check it.
The pings you have listed in your post don't all make sense. Two of them are pinging the same FQDN but give different IP addresses (below):
What problem are you trying to solve?
-Greg

Backup DNS Records

Afternoon,
Is there a way to create a back-up A record in order to provide redundancy?
I'm currently in the middle of setting up a DR site and looking to find a way to have a set of DNS record pointing at existing servers host name but with different IP addresses so in the event that we require to bring a replicated server up at the DR site
the DNS record would automatic switch over after the TTL has expired on the primary link.
our DNS service runs on a windows server 2012 environment in a cluster of 3 servers for redundancy.
Thanks

To answer/address the question about the same records with different IPs, unfortunately it doesn't work that way with AD. The IPs registered are absolute for the service locations, and they must be consistent across the organization for AD DC to DC communications
including replication, and client to DC communications. If you attempt to alter them, it will cause numerous errors and additional headaches that I'm sure you do not want to deal with.
Just setup two DCs at the DR, do not make them GCs. Just make them GCs in case a down issue occurs. Depending if you have 3 or more sites, this may also require to make individual site links for each site and disable BASL. The reasons are long winded,
but it's technically how AD works. You can design around it, but you can't mess with DNS. And keep in mind, just because they are up, services and client apps may not be so forgiving to "see" the DR servers until they've been restarted.
So there's more to this than it appears.
You can read up in this stuff in the following link:
AD Site Design, DNS & the DC Locator Process, and Auto Site Link Bridging, or Bridge All Site Links (BASL)
http://blogs.msmvps.com/acefekay/2013/02/24/ad-site-design-and-auto-site-link-bridging-or-bridge-all-site-links-basl/
The blogs below discusses:
WINS NetBIOS, Browser Service, Disabling NetBIOS, & Direct Hosted SMB (DirectSMB). Troubleshooting the browser service.
Client side resolution process chart.
The DNS Client Side Resolver algorithm.
If one DC or DNS goes down, does a client logon to another DC or use the other DNS server in the NIC?
DNS Forwarders Algorithm and multiple DNS addresses (if you've configured more than one forwarders or more than one IP in the NIC's DNS list)
Client side resolution process chart
Published by Ace Fekay, MCT, MVP DS on Nov 29, 2009 at 10:28 PM 1764 1
http://blogs.msmvps.com/acefekay/2009/11/29/dns-wins-netbios-amp-the-client-side-resolver-browser-service-disabling-netbios-direct-hosted-smb-directsmb-if-one-dc-is-down-does-a-client-logon-to-another-dc-and-dns-forwarders-algorithm/
Ace Fekay
MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
This posting is provided AS-IS with no warranties or guarantees and confers no rights.

What is about rumors with DNS bug?

There a rumors about update 2008-5 that it is not solving problems with clients (›So Apple might have fixed some of the more important parts for servers, but is far from done yet as all the clients linked against a DNS client library still need to get the workaround for the protocol weakness.‹ in http://isc.sans.org/diary.html?storyid=4810)
I think, clients are not at all touched with this matter. Is this right?
Karl

Client caches can be poisoned. But this forum is for the server product, where DNS poisoning is more troublesome. That issue has largely been resolved with Apple's latest patch.

DNS Server in IOS?

Does any version of the IOS include a DNS server? To make a long story short, I just need one record to be resolved on a non-routed subnet and am hoping I have can have a router act as a DNS server.

see the following link for ios dns support for ns records:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1839/products_feature_guide09186a0080087ae3.html
(ios 12.2)

Help with DNS!!!

I'm tring to bulid a Domain Name Server...but I don't know where to start!! Any ideas would be gladly recieved.

To start visit this thread at DejaNews:
http://groups.google.com/groups?hl=en&safe=off&th=c1691ab94697983c,8&seekm=5KAXOAYZ5CvVBXqD9iFeQfWbVtkm%404ax.com#p
There's a link to a DNS implementation in java:
http://www.xbill.org/dnsjava
Kurta

Album arts with sharecenter pulse dns 320

Hello
first I love the new itunes 11 but i have one little issue and maybe someone knows the answer to it,
i Have itunes 11 and e NAS, D-Link Sharecenter pulse dns-320, everything works fine except the album arts, none of the arts are visible in de little tiles, when i click large it does show (see image), anyone has the same problem, or knows a solution

Try these troubleshooting steps:
A] With the help of Cisco Connect Software (if at all you have installed the router with the help of this software)
1] Open the software and go to the option which says "Router Settings"
2] Then click on the option which says "Advanced Settings" which will take you to the router's configuration page.
3] In that setup page reduce the MTU size to 1400 from auto. Save the settings
4] Click the security tab and uncheck 'Filter Anonymous Internet Requests' and SPI firewall..Save the settings..
B] If you haven't installed Cisco Connect then you can log on to the router's user interface using it's default IP address in the browser which is 192.168.1.1 and type in 'admin' as the password leaving the username field blank. This will take you to the router's web interface and then follow steps as mentioned above to make the changes.
Then check the wireless connection status.

Auto discovery DNS

I have ADSL connection and I get my IP address via DHCP from my ISP. Is there a command to enable auto discovey DNS on the
ATM interface to pick which DNS server to use from my ISP?

check the following link for configuring DNS on a router :
http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a00800c525f.shtml

Standalone server mDNS vs DNS

I'm having trouble connecting to my standalone server via its mDNS name. It seems to respond immediately after booting but then disappears. My questions are:
What's the relationship between mDNS and DNS in the server?
Is mDNS always on independent of the DNS in the server admin?
Where are the relevant logs for it?
Thanks
Tom

mDNS is 2 things together; DNS Service Discovery AND Multicast DNS.
DNS Service Discovery is a way of using standard DNS programming interfaces, servers, and packet formats to browse the network for services.
Multicast DNS is a way of using familiar DNS programming interfaces, packet formats and operating semantics, in a small network where no conventional DNS server has been installed. This is also know as the Zero-Conf initiative.
read your manual page on mDNSResponder for more 'quasi-specific Info' and here are a few links.
http://www.dns-sd.org/
http://www.multicastdns.org/
Oh, to answer your question. mDNS will help you find other machines on your local subnet by their name+.local domain. So, if mDNS is working properly, you should ALWAYS be able to find your machine by its name.local. You can find your hostname by opening terminal and typing 'hostname -s'
Hope that Helps.
Peter

An error occurred while configuring your server

The following actions failed or were not attempted:
Configuring network
Starting push notification server.
DNS is killing me. I am an accountant.
I have a new out of the box mac mini server.
I want clients (real people with pcs and macs) to have external internet access to wiki, email and other nice services.
I do not want to serve DNS to the world; I just want to get past the installation configuration with a suitable DNS.
I am not at all clear whether I want Open Directory and from that whether I need DNS at all.
When this machine is set up it will be accessed only from outside on the public internet, including for admin matters by me; no "internal/local" users at all.
I do have a choice of domain names. I was trying papakilo.net and server as the machine name.
I can go in to change the papakilo.net domain records - though whether I can set up a reverse dns I am not clear.
I will buy a time machine if that is what it takes to have the firewall security managed by the server itself; I am assuming this would remove a level of expertise I do not want to acquire more than already.
I have spent many hours on here and in google, reading, watching videos etc looking for the answer to what to enter into "Primary DNS name"?
Where I am working right now has a dynamic IP but it doesn't change often and is fine for testing because I can keep checking what it is.
The final location will have (does have) a fixed ip address.
I bought Max Server many years ago, perhaps version one or two or whatever and had the same experience: within minutes I was unable to use the system.
So. The adverts said this was now easy. (I never learn).
If I knew what to type in to the DNS boxes and what to change on papakilo's domain DNS would I be further along?
I was looking forward to the joys of VPN set up and the like, not this.
Somewhat disappointedly as I had high hopes only to find extensive DNS reading is required to know what to type into the very first dialogue box.
Wonder if I should set up the canonical server.papakilo.net in the internet based DNS record so that the install routine can find it... is that the first problem?
And is the second problem to point the external i.p address back to the dynamic one in use at this location?
And will that facilitate the reverse lookup?
And will I have to wait for the propagation time to find out if this works -
or can I use actual i.p. addresses while I wait?
Some sympathetic help would be much appreciated please, and I promise I won't tell everyone how simple tax is.
Best wishes,
Anthony

Special thanks to JeroenHolland for this post
http://discussions.apple.com/thread.jspa?threadID=2357325&start=0&tstart=15
where he says this: (I have edited in my own data to replace previous content)
So:
< External DNS server of your ISP >
------------Time Capsule--------------
< Local DNS server running on your Mac Mini >
I think the above is truly brilliant for its clarity of presentation. It is simple, but attempt writing that description in words and see how the caveats make it look complex.
snip/snip/ I haven't done the time capsule stuff yet. Clearly I need DNS set up and here below is the clearest description I have found:
Then the next step is to setup the DNS Service in Server Admin.
First the Settings tab:
"Accept recursive queries" basically is a whitelist of which computers are allowed to use the DNS server. In a local DNS server, 'localnets' is okay. Localnets allows all IP adresses in the same range as the IP adress of the DNS server to access it.
Actually all that was already entered by default, so ok was all I needed click.
"Forwarder IP Adresses" are the IP addresses of the DNS servers that should be used if the requested URL-name (hostname/domainname/etc) is NOT in the list of the DNS server.
(So if the DNS server gets a request for "www.google.com", and the zone "google.com" isnt in its Zone list, the request gets forwarded to those Forwarder DNS servers.)
Again sheer simplicity or presentation in words I understand (and not Dutch this is where I understand that I can use my isp's DNS numbers from standard Network setup in system prefs, so this is the link between internal DNS and external DNS - I just could not see it before. "Forwarder" means "my isp's DNS numbers".
The last thing is the Zones.
I understand that you're setting up your own webserver. With subdomains.
Primary Zone Name should be: papakilo.net.
Nameserver Zone should be: papakilo.net.
Nameserver Hostname should be: news.papakilo.net
Machine:
* Machinename: new.papakilo.net.
* Ip Address: 192.168.1.103
CNAME Alias:
* Alias name: www
* Destination: news.papakilo.net.
Clearly I have populated the quotation with my own data to see if I can and for later reference.
So with my broken system I have no Open Directory so when I click Groups it says I have to set up Open Directory first and now with the above entered I do that and create some users.
The only thing remaining seems to me external access as I can access using local ip addresses.
Anthony
Message was edited by: Anthony Mellor

WGM Home directory full path not populating properly

I'm setting up WGM with mobility as all of my network users are on laptops. For some reason some of the users are working and others not. When I try to log in with some I just get told that the user couldn't log on because an error occured. As far as I can work out this is because the home directory for the user on the network can't be found and so a local one can't be created either.
The only difference I can see between the users (bearing in mind this is a brand new network set up so I haven't made many changes) is that for the users that do work when I select the SharePoint I want to use under the home tab in user settings, the Full Path has ...er ...well the full path in it: /network/servers/mynetwork/Volumes/myharddrive/myfolder/myuser
whereas ones that don't work just have the folder name: myuser
This not only happens when I use the auto populated list as well as when I create one from scratch.

You're right, DNS implementation in Leopard server is very poor, especially considering how critical it is.
Time Machine for every user is a bit of a tricky one - I've been thrashing this one out in another thread, and there is an answer, but it's not ideal.
Here's the thread: http://discussions.apple.com/thread.jspa?threadID=2034769&start=0&tstart=0
The answer on how to do it is at the end of the thread, but make sure Time Machine isn't used as the only method of Disaster Recovery on a corporate network, it's really only good for a useful extra.
As for an internal and external DNS server, the answer I'm afraid is "not really". The way you have it set up is pretty good, from a redundancy point of view. However, if you have to use an external DNS server, it's always going to be slower, because of the extra distance over slower links that the DNS request has to travel.
Bear in mind, it has to go through your router and/or firewall, all the way out to a busy DNS server somewhere out on the net (probably over a number of routers on the way), then it has to come back the same way before your client can actually resolve the URL to an IP address.
Compare that to internal where it has to travel a matter of metres over a (I assume) 100mbps network to a DNS server that's not processing very many requests.
The only workaround I could suggest would be to employ a second DNS server (perhaps a proxy?) within your network assuming you can separate it from whatever causes your primary DNS server to go down. The costs aren't prohibitive - you could do it on a Mac Mini + cost of a second Leopard Server license.
Oh, and your English is just fine, lol.
Message was edited by: MattLucas1505

D-Link fouls up DNS

Similar Messages

Maybe you are looking for