Slow DNS web resolution

I've noticed the DNS resolution for web services on our network has become a little slow.
The log is showing the below (for example):
success resolving 'www.jamesallenonf1.com/A' (in 'jamesallenonf1.com'?) after reducing the advertised EDNS UDP packet size to 512 octets
Any ideas what this could be caused by and if it would explain the slowing of web page resolution?
Thanks

Thanks - that was useful as was the below quote:
Quote by: MacTroll
Your DNS server is attempting to use DNS-SEC, for validated DNS lookups. This requires a larger UDP packet size, >512 bytes, than your firewall seems to like. It then has to wait to both decide it needs to reduce packet size /and/ to get a negative result on the lookup.
I would imagine that the DNS resolver on OS X client doesn't bother to do a DNS-SEC lookup, and hence no issue.
This was evident in another line of the log:
host unreachable resolving 'I.ROOT-SERVERS.NET/AAAA/IN': 198.41.0.0#53
I created a rule in the hardware firewall to forward port 53 to the SLS and its running fine now with no errors.

Similar Messages

  • For anyone who is experiencing slow DNS lookups...

    I finally worked out what was wrong with my network config last night and thought I'd share it with everyone in a simgle post in the hope it'll help someone else.
    I tried the BIND work around, but it wasn't all that much faster.
    I tried disabling IPv6, but that didn't do much...
    The solution?
    In 'System Preferences' -> 'Network'
    Go to configure the adaptor (Airport / Ethernet / etc)
    In 'DNS Servers' where you'd normally specify the DNS servers given to you by your ISP... don't do this! As crazy as it sounds don't
    Of course, if you're using newer routers you'd not be having this slow DNS lookup problem and specifying the ISPs DNS Servers would be appropriate... still
    What you want to specify here is your ROUTER's IP:
    eg. 192.168.0.1
    With this simple modifcation you'll be fine. Why? You ask?
    In Linux / OSX (I imagine in Unix as well) the way the lookups are carried out are different from Windows. I have other Windows computers on our network and they never had DNS lookup problems and they've been given the ISPs DNS IPs... anyway I think I'm talking out of my depth now heh.
    This works!
    Remember: Specify your router as the DNS Server!

    I've had this problem on a G4 PowerMac running Panther, and it still had it after a Tiger upgrade. I just replaced it with a Core Duo MacMini, 10.4.7, same problem of slow DNS lookups (i.e., slow initial start to loading a web page, then it goes quickly). Windows machines on the same subnet have no such problem. I've tried the various suggestions on various forums, none of which worked. I tried:
    - turn off IPv6 (no help)
    - directly enter my ISPs DNS servers (no help)
    - manually configure both IP and DNS (no help, went back to DHCP)
    - swear at the computer (a little help, mentally)
    After some more reading, I tried resolving some addresses using the host command from the Terminal:
    host -v www.apple.com 24.34.240.9
    where the IP address is one of the DNS servers for my ISP (Comcast). I got a no server found message! I then tried the second DNS server in the Comcast list (found from my router), also no server found. Tried the third one in Comcast's list of DNS servers, and it worked. Entered it in System Preferences -> Network as a DNS server, and now web browsing is zippy! I verified that the two DNS servers that MacOS couldn't see are also down as far as Windows was concerned (using the nslookup command in windows).
    What this tells me is that the OS X algorithm for handling unreachable or slow DNS servers is different from that in Windows. Maybe Windows remembers a bad experience with a DNS server and uses ones that it has success with, while OS X just keeps trying them in order, slowing timing them out until it finds one that works?
    This could also explain many of the puzzling symptoms people have been seeing (things work some times, other times not; some people have luck specifying the DNS server manually, others don't). It all depends on what DNS servers got distributed to the Mac via DHCP, and how far down the list you have to go to find one that is responsive.
    Anyone reading this forum with technical knowledge of both UNIX and Windows DNS lookup implementations? Is there some way to tweak in MacOS to make it perform more like Windows in this situation (like, maybe shortening the DNS server failure timeout)?

  • Why is my macbook air running slow while web browsing, why is my macbook air running slow while web browsing

      a few days ago my macbook pro that i recently purchesed for christmas started running really slow while web browsing. I looked at all the memory and all that and it was fine. any advice?

    Please answer as many of the following questions as you can. You may already have answered some of them. In that case, there's no need to repeat the answers.
    Have you restarted your router and your broadband device (if they're separate) since you first noticed the problem? If not, do that now and see whether there's any change.
    If your browser is Safari, then from the Safari menu bar, select
    Safari ▹ Preferences... ▹ Privacy ▹ Remove All Website Data
    and confirm. Any change?
    Quit and relaunch the browser. Any change?
    Log out and log back in. Any change?
    Enable Private Browsing in the Safari menu. Any change?
    Are any other web browsers installed, and are they the same? What about other Internet applications, such as iTunes and the App Store?
    If other browsers and Internet applications are also affected, follow these instructions and test. Any change?
    If only Safari is affected, launch the Activity Monitor application and enter "web" (without the quotes) in the search box. If a process named "Safari Web Content" is shown in red or is using more than about 5% of a CPU, select it and force it to quit by clicking the X or Quit Process button in the toolbar of the window. There may be more than one such process. Any improvement?
    Again, if only Safari is involved, open the iCloud preference pane and uncheck the box marked Safari, if it's checked. Any change?
    Are there any other devices on the same network that can browse the Web, and are they affected?
    If you can test Safari on another network, is it the same there?
    If you connect to your router with Wi-Fi and you can also connect with Ethernet, do that and turn off Wi-Fi. Any difference?

  • Retina is slow on web pages, true or wrong ?

    Retina is slow on web pages, true or wrong ?
    im still hesitating between retina andd classic, any advice ? is new MBP will arrive september ? Does it worth waiting ?

    Web page loading is really up to your internet connection unless you have a very old computer with low power CPU.

  • Slow DNS resolution

    Folks;
    *I have Mac OS X Leopard 10.5.6 up to date and since few days, the DNS resolution is very slow, about 5 seconds to resolve names.*
    *For example :*
    # ping test.com
    *(wait 5 seconds)*
    PING test.com (205.178.152.103): 56 data bytes
    *Of course it also happen in firefox and in all other internet applications. Each time I'm loading a web page, I have to wait 5 seconds...*
    *If I try a few seconds later, it answer immediately, but a few minutes later, it take again 5 seconds to resolve the name.*
    *I'm not sure, and maybe it's just a coincidence, but it came just after the installation of Adobe Photoshop 4.*
    *I think about a virus or some mysterious mac os parameters ...*
    *I try* dscacheutil -flushcache *with no effect.*
    *My /etc/hosts is :*
    nameserver 212.27.40.240
    *I only have 1 dns server, and when I try :*
    nslookup test.com 212.27.40.240
    *It answer immediately :*
    Server: 212.27.40.240
    Address: 212.27.40.240#53
    Non-authoritative answer:
    Name: test.com
    Address: 205.178.152.103
    *I tried with many others DNS and also with a local DNS server (bind) with the same result.*
    *The output of :*
    # dscacheutil -statistics
    Overall Statistics:
    Average Call Time - 1.298089
    Cache Hits - 1813
    Cache Misses - 1888
    Total External Calls - 2662
    Statistics by procedure:
    Procedure Cache Hits Cache Misses External Calls
    getpwnam 151 15 166
    getpwuid 842 34 876
    getpwent 0 0 2
    getgrnam 38 18 56
    getgrgid 15 16 31
    getgrent 0 0 2
    getservbyname 7 5 7
    getservent 0 0 6
    getprotobyname 0 2 2
    getfsent 0 0 14
    getaddrinfo 0 0 1117
    getnameinfo 53 189 242
    gethostbyname 537 591 42
    gethostbyaddr 16 71 87
    gethostbymac 5 4 9
    _flushcache 0 0 3
    *As you can see, "Average Call Time" is very high, it should be 0.0xxxxx*
    *ifconfig output :*
    lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
    inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
    inet 127.0.0.1 netmask 0xff000000
    inet6 ::1 prefixlen 128
    gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
    stf0: flags=0 mtu 1280
    en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    ether 00:1b:63:96:ab:e1
    media: autoselect status: inactive
    supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control> none
    fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
    lladdr 00:1c:b3:ff:fe:86:88:46
    media: autoselect <full-duplex> status: inactive
    supported media: autoselect <full-duplex>
    en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
    inet 192.168.0.10 netmask 0xffffff00 broadcast 192.168.0.255
    ether 00:1b:63:ca:a9:93
    media: autoselect status: active
    supported media: autoselect
    *dtruss output :*
    # dtruss ping itt.com
    SYSCALL(args) = return
    ioctl(0x3, 0x80086804, 0xBFFFE488) = 0 0
    close(0x3) = 0 0
    __sysctl(0xBFFFE35C, 0x2, 0xBFFFE364) = 0 0
    bsdthread_register(0x91CD1F30, 0x91D0A2A4, 0x1000) = 0 0
    open_nocancel("/dev/urandom\0", 0x0, 0x0) = 3 0
    read_nocancel(0x3, "\377~\360U\360\211\303\231l\2725\002\265\327\247\371N`#_\314.\323@\022u\323\34 6'\224\314\271\0", 0x20) = 32 0
    close_nocancel(0x3) = 0 0
    mmap(0x0, 0x3000, 0x3, 0x1002, 0x1000000, 0x100000000) = 0x1E000 0
    mmap(0x0, 0x200000, 0x3, 0x1002, 0x7000000, 0x100000000) = 0x21000 0
    munmap(0x21000, 0xDF000) = 0 0
    munmap(0x200000, 0x21000) = 0 0
    mmap(0x0, 0x3000, 0x3, 0x1002, 0x1000000, 0x100000000) = 0x21000 0
    getpid(0x0, 0x3000, 0x3) = 1436 0
    socket(0x2, 0x3, 0x1) = 3 0
    getuid(0x2, 0x3, 0x1) = 0 0
    setuid(0x0, 0x3, 0x1) = 0 0
    getuid(0x0, 0x3, 0x1) = 0 0
    getpid(0x0, 0x0, 0x0) = 1436 0
    __sysctl(0xBFFFE678, 0x3, 0xBFFFFA98) = 0 0
    issetugid(0xBFFFE678, 0x3, 0xBFFFFA98) = 0 0
    __sysctl(0xBFFFE534, 0x2, 0xBFFFE4FC) = 0 0
    __sysctl(0xBFFFE4FC, 0x2, 0xBFFFE57C) = 0 0
    sharedregion_checknp(0xBFFFFA78, 0x2, 0xBFFFE57C) = 0 0
    stat("/usr/lib/dtrace/libdtrace_dyld.dylib\0", 0xBFFFD6E8, 0xBFFFE57C) = 0 0
    open("/usr/lib/dtrace/libdtrace_dyld.dylib\0", 0x0, 0x0) = 3 0
    pread(0x3, "\312\376\272\276\0", 0x1000, 0x0) = 4096 0
    pread(0x3, "\316\372\355\376\a\0", 0x1000, 0x9000) = 4096 0
    mmap(0x19000, 0x1000, 0x5, 0x12, 0x3, 0x100000000) = 0x19000 0
    mmap(0x1A000, 0x1000, 0x3, 0x12, 0x3, 0x100000000) = 0x1A000 0
    mmap(0x1B000, 0x1000, 0x7, 0x12, 0x3, 0x100000000) = 0x1B000 0
    mmap(0x1C000, 0x1900, 0x1, 0x12, 0x3, 0x100000000) = 0x1C000 0
    fcntl(0x3, 0x2C, 0xFFFFFFFFBFFFBD54) = 0 0
    close(0x3) = 0 0
    stat("/usr/lib/libgcc_s.1.dylib\0", 0xBFFFD4E8, 0xFFFFFFFFBFFFBD54) = 0 0
    stat("/usr/lib/libSystem.B.dylib\0", 0xBFFFD4E8, 0xFFFFFFFFBFFFBD54) = 0 0
    stat("/usr/lib/system/libmathCommon.A.dylib\0", 0xBFFFD328, 0xFFFFFFFFBFFFBD54) = 0 0
    open("/dev/dtracehelper\0", 0x2, 0xBFFFE504) = 3 0
    PING itt.com (199.253.127.99): 56 data bytes
    sigaction(0x2, 0xBFFEF6E0, 0x0) = 0 0
    sigaction(0x1D, 0xBFFEF6E0, 0x0) = 0 0
    sendto(0x3, 0x5234, 0x40) = 64 0
    select(0x4, 0xBFFFF9DC, 0x0, 0x0, 0xBFFFFB30) = 1 0
    recvmsg(0x3, 0xBFFFFAC4, 0x0) = 153 0
    setsockopt(0x3, 0xFFFF, 0x400) = 0 0
    setsockopt(0x3, 0xFFFF, 0x1002) = 0 0
    setsockopt(0x3, 0xFFFF, 0x1001) = 0 0
    fstat64(0x1, 0xBFFEEE64, 0x1001) = 0 0
    ioctl(0x1, 0x4004667A, 0xBFFEEECC) = 0 0
    mmap(0x0, 0x1000000, 0x3, 0x1002, 0x2000000, 0x0) = 0x200000 0
    munmap(0x200000, 0x600000) = 0 0
    munmap(0x1000000, 0x200000) = 0 0
    write_nocancel(0x1, "PING itt.com (199.253.127.99): 56 data bytes\n\0", 0x2D) = 45 0
    select(0x4, 0xBFFFF9DC, 0x0, 0x0, 0xBFFFFB30) = 0 0
    sendto(0x3, 0x5234, 0x40) = 64 0
    ©select(0x4, 0xBFFFF9DC, 0x0, 0x0, 0xBFFFFB30) = 0 0
    sendto(0x3, 0x5234, 0x40) = 64 0
    select(0x4, 0xBFFFF9DC, 0x0, 0x0, 0xBFFFFB30) = 0 0
    sendto(0x3, 0x5234, 0x40) = 64 0
    ^C
    *tcpdump output (with # ping ita.fr) :*
    # tcpdump -i en1
    00:26:06.469246 IP 192.168.0.10.49985 > 192.168.2.1.domain: 64308+ A? ita.fr. (24)
    00:26:06.486473 IP 43.242.3.202.dial.dyn.mana.pf.22369 > 192.168.0.10.42567: UDP, length 85
    00:26:06.487552 IP 192.168.0.10.42567 > 43.242.3.202.dial.dyn.mana.pf.22369: UDP, length 35
    00:26:07.277453 IP 192.168.0.10.49938 > 192.168.2.1.domain: 44176+ PTR? 43.242.3.202.in-addr.arpa. (43)
    00:26:09.346380 IP 192.168.0.10.ntp > time4.euro.apple.com.ntp: NTPv4, Client, length 48
    00:26:09.541593 IP time4.euro.apple.com.ntp > 192.168.0.10.ntp: NTPv4, Server, length 48
    00:26:11.467716 IP 192.168.0.10.61034 > dns1.proxad.net.domain: 64308+ A? ita.fr. (24)
    00:26:11.469940 arp who-has 192.168.0.10 tell 192.168.0.254
    00:26:11.469996 arp reply 192.168.0.10 is-at 00:1b:63:ca:a9:93 (oui Unknown)
    ^C
    *ps aux output :*
    # ps aux
    $USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND
    root 15 4.2 0.0 599620 284 ?? Ss 10:27AM 0:23.20 /usr/sbin/update
    fanzila 330 3.1 0.8 302188 16000 ?? R 12:06PM 0:41.58 /Applications/Utilities/Terminal.app/Contents/MacOS/Terminal -psn0413797
    fanzila 994 2.6 8.2 486288 172048 ?? S 11:33PM 5:53.31 /Applications/Firefox.app/Contents/MacOS/firefox-bin -psn01122578
    _windowserver 54 2.5 4.6 405476 97200 ?? Ss 10:27AM 6:30.50 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/CoreGraphic s.framework/Resources/W
    fanzila 1092 1.2 3.2 473732 66856 ?? S 11:52PM 0:34.00 /Applications/Adobe Photoshop CS4/Adobe Photoshop CS4.app/Contents/MacOS/Adobe Photoshop CS4 -psn012
    root 33 1.1 0.2 78660 3796 ?? Ss 10:27AM 0:16.79 /usr/sbin/DirectoryService
    fanzila 23 0.5 0.4 298916 8368 ?? Ss 10:27AM 0:14.18 /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow console
    fanzila 130 0.5 0.6 305176 13164 ?? S 10:38AM 0:17.71 /System/Library/CoreServices/SystemUIServer.app/Contents/MacOS/SystemUIServer -psn053261
    fanzila 1332 0.0 0.1 2926604 2376 ?? S 12:20AM 0:00.10 /Applications/CrossOver.app/Contents/SharedSupport/CrossOver/lib/../bin/wineloa der C:\windows\system32
    fanzila 1328 0.0 0.1 79096 2432 ?? Ss 12:20AM 0:01.88 /Applications/CrossOver.app/Contents/SharedSupport/CrossOver/lib/../bin/wineser ver
    fanzila 1322 0.0 0.2 2928312 5072 ?? S 12:20AM 0:00.33 /Applications/CrossOver.app/Contents/SharedSupport/CrossOver/bin/wineloader winewrapper.exe --workdir
    fanzila 1321 0.0 0.1 217684 2364 ?? S 12:20AM 0:00.05 /Users/fanzila/Library/Caches/Cleanup At Startup/CrossOver CD Helper.app/Contents/MacOS/CrossOver CD H
    fanzila 1317 0.0 0.2 78124 4940 ?? Ss 12:20AM 0:00.11 /usr/bin/perl -w /Applications/CrossOver.app/Contents/SharedSupport/CrossOver/bin/cxmenu --bottle winx
    fanzila 1316 0.0 0.2 2928312 5072 ?? Ss 12:20AM 0:00.37 /Applications/CrossOver.app/Contents/SharedSupport/CrossOver/bin/wineloader winewrapper.exe --run -- /
    fanzila 1313 0.0 0.1 227052 2960 ?? Ss 12:20AM 0:00.10 /usr/bin/quartz-wm
    fanzila 1305 0.0 1.2 327344 25868 ?? S 12:20AM 0:01.48 /Applications/CrossOver.app/Contents/MacOS/CrossOver -psn01335622
    fanzila 1304 0.0 0.1 225336 3004 ?? S 12:20AM 0:00.13 /Users/fanzila/Applications/CrossOver/DHO.app/Contents/MacOS/CrossOver Helper with Feedback -psn0133
    fanzila 1097 0.0 0.2 91876 4644 ?? S 11:52PM 0:00.28 /System/Library/Services/AppleSpell.service/Contents/MacOS/AppleSpell -psn01212712
    fanzila 1094 0.0 0.7 327036 15668 ?? S 11:52PM 0:14.38 /Applications/TextEdit.app/Contents/MacOS/TextEdit -psn01208615
    fanzila 1093 0.0 0.1 76432 1540 ?? Ss 11:52PM 0:00.07 /Applications/Adobe Photoshop CS4/Adobe Photoshop CS4.app/Contents/Frameworks/AdobeCrashReporter.frame
    fanzila 993 0.0 2.9 430152 60324 ?? U 11:33PM 0:20.24 /Applications/Path Finder.app/Contents/MacOS/Path Finder -psn01118481
    fanzila 983 0.0 1.9 399876 39104 ?? S 11:32PM 0:19.28 /Applications/Skype.app/Contents/MacOS/Skype -psn01114384
    fanzila 982 0.0 1.1 339696 22972 ?? U 11:32PM 0:09.25 /Applications/Adium.app/Contents/MacOS/Adium -psn01110287
    fanzila 967 0.0 2.6 355348 53504 ?? S 11:32PM 0:08.98 /Applications/Mail.app/Contents/MacOS/Mail -psn01106190
    fanzila 921 0.0 0.0 600252 944 s001 S+ 7:07PM 0:00.06 /bin/bash
    fanzila 912 0.0 0.0 600252 756 s001 S 7:07PM 0:00.01 -bash
    root 911 0.0 0.1 76592 1104 s001 Ss 7:07PM 0:00.03 login -pf fanzila
    _mdnsresponder 646 0.0 0.1 77304 1164 ?? Ss 4:03PM 0:00.10 /usr/sbin/mDNSResponder -launchd
    fanzila 635 0.0 0.0 601896 804 ?? S 4:02PM 0:01.19 /usr/local/bin/gpg-agent --launchd --use-standard-socket --write-env-file
    root 596 0.0 0.0 600252 952 s000 S 3:55PM 0:00.43 /bin/bash
    fanzila 341 0.0 0.0 600252 944 s000 S 12:06PM 0:00.07 /bin/bash
    fanzila 332 0.0 0.0 600252 756 s000 S 12:06PM 0:00.02 -bash
    root 331 0.0 0.1 76592 1104 s000 Ss 12:06PM 0:00.03 login -pf fanzila
    fanzila 298 0.0 0.6 268748 12604 ?? U 11:54AM 0:00.91 /System/Library/CoreServices/Dock.app/Contents/Resources/DashboardClient.app/Co ntents/MacOS/DashboardC
    fanzila 297 0.0 0.4 264760 8108 ?? S 11:54AM 0:00.51 /System/Library/CoreServices/Dock.app/Contents/Resources/DashboardClient.app/Co ntents/MacOS/DashboardC
    fanzila 296 0.0 0.8 272252 16328 ?? S 11:54AM 0:01.51 /System/Library/CoreServices/Dock.app/Contents/Resources/DashboardClient.app/Co ntents/MacOS/DashboardC
    fanzila 295 0.0 0.6 270808 12488 ?? S 11:54AM 0:01.51 /System/Library/CoreServices/Dock.app/Contents/Resources/DashboardClient.app/Co ntents/MacOS/DashboardC
    fanzila 294 0.0 0.9 299344 17828 ?? S 11:54AM 0:03.26 /System/Library/CoreServices/Dock.app/Contents/Resources/DashboardClient.app/Co ntents/MacOS/DashboardC
    nobody 156 0.0 0.0 76776 632 ?? Ss 10:38AM 0:00.01 /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/A/Resources/u sbmuxd -launchd
    fanzila 151 0.0 0.1 223464 2408 ?? S 10:38AM 0:00.12 /Applications/iTunes.app/Contents/Resources/iTunesHelper.app/Contents/MacOS/iTu nesHelper -psn0118813
    fanzila 144 0.0 0.3 314696 7184 ?? S 10:38AM 0:03.93 /Library/PreferencePanes/Witch.prefPane/Contents/Resources/witchdaemon.app/Cont ents/MacOS/witchdaemon
    fanzila 137 0.0 0.1 214952 2960 ?? S 10:38AM 0:00.22 /Library/Printers/hp/hpio/HPEventHandler.app/Contents/MacOS/HPEventHandler -psn069649
    fanzila 129 0.0 0.6 279688 12996 ?? S 10:38AM 0:15.74 /System/Library/CoreServices/Dock.app/Contents/MacOS/Dock -psn049164
    fanzila 128 0.0 0.3 136856 6420 ?? S 10:38AM 0:08.23 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framewo rk/Support/ATSServer
    fanzila 127 0.0 0.0 76504 536 ?? S 10:38AM 0:00.01 /usr/sbin/pboard
    fanzila 126 0.0 0.1 220304 2248 ?? S 10:38AM 0:00.28 /usr/sbin/UserEventAgent -l Aqua
    fanzila 125 0.0 0.2 225908 3964 ?? S 10:38AM 0:00.26 /System/Library/CoreServices/Spotlight.app/Contents/MacOS/Spotlight
    fanzila 120 0.0 0.2 257568 3348 ?? S 10:38AM 0:00.17 /System/Library/CoreServices/AirPort Base Station Agent.app/Contents/MacOS/AirPort Base Station Agent
    fanzila 114 0.0 0.0 600820 560 ?? Ss 10:38AM 0:00.51 /sbin/launchd
    root 108 0.0 0.2 79644 3304 ?? Ss 10:29AM 0:01.10 /usr/sbin/coreaudiod
    root 95 0.0 0.1 77928 1388 ?? S 10:27AM 0:00.13 /Library/Printers/hp/hpio/HPIO Trap Monitor.app/Contents/MacOS/HPIO Trap Monitor
    root 87 0.0 0.0 76572 732 ?? Ss 10:27AM 0:00.12 /Library/Frameworks/HPServicesInterface.framework/Runtime/hpusbmond
    root 47 0.0 0.1 86716 1836 ?? Ss 10:27AM 0:00.16 /usr/sbin/blued
    root 45 0.0 1.3 116160 27116 ?? Ss 10:27AM 0:05.43 /System/Library/CoreServices/coreservicesd
    daemon 43 0.0 0.0 75356 808 ?? Ss 10:27AM 0:01.88 /usr/sbin/distnoted
    root 40 0.0 0.1 75704 1500 ?? Ss 10:27AM 0:00.61 /usr/libexec/ApplicationFirewall/socketfilterfw
    root 38 0.0 0.0 75388 672 ?? Ss 10:27AM 0:00.03 autofsd
    root 35 0.0 0.1 77000 2080 ?? Ss 10:27AM 0:13.02 /usr/sbin/configd
    root 32 0.0 0.1 75460 1104 ?? Ss 10:27AM 0:01.04 /usr/sbin/diskarbitrationd
    root 29 0.0 0.0 75376 700 ?? Ss 10:27AM 0:00.01 /sbin/dynamic_pager -F /private/var/vm/swapfile
    root 27 0.0 0.1 85768 1476 ?? Ss 10:27AM 0:01.70 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/
    root 26 0.0 0.0 75896 600 ?? Ss 10:27AM 0:00.01 /usr/libexec/hidd
    root 24 0.0 0.0 75448 644 ?? Ss 10:27AM 0:00.01 /usr/sbin/KernelEventAgent
    root 21 0.0 2.9 259112 61136 ?? Ss 10:27AM 2:08.30 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Support/mds
    root 19 0.0 0.1 77316 2248 ?? Ss 10:27AM 0:00.64 /usr/sbin/securityd -i
    root 16 0.0 0.0 75372 640 ?? Ss 10:27AM 0:00.01 /sbin/SystemStarter
    root 14 0.0 0.0 75900 824 ?? Ss 10:27AM 0:02.07 /usr/sbin/ntpd -c /private/etc/ntp-restrict.conf -n -g -p /var/run/ntpd.pid -f /var/db/ntp.drift
    root 12 0.0 0.0 601332 464 ?? Ss 10:27AM 0:00.57 /usr/sbin/syslogd
    root 11 0.0 0.0 600236 484 ?? Ss 10:27AM 0:00.69 /usr/sbin/notifyd
    root 10 0.0 0.1 75968 1228 ?? Ss 10:27AM 0:00.86 /usr/libexec/kextd
    root 1460 0.0 0.0 599788 452 s000 R+ 12:27AM 0:00.01 ps aux
    root 1 0.0 0.0 600820 564 ?? Ss 10:27AM 0:00.50 /sbin/launchd
    _spotlight 1453 0.0 0.1 89116 2000 ?? SNs 12:26AM 0:00.13 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdw
    fanzila 1425 0.0 0.2 122524 3432 ?? SNs 12:21AM 0:00.24 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdw
    fanzila 1365 0.0 0.3 2931372 6596 ?? Ss 12:21AM 0:00.36 /Applications/CrossOver.app/Contents/SharedSupport/CrossOver/lib/../bin/wineloa der C:\windows\system32
    fanzila 1362 0.0 0.1 78948 1364 ?? S 12:21AM 0:00.11 /System/Library/Frameworks/CoreMIDIServer.framework/MIDIServer
    *Many thanks for your help.*

    fanzila wrote:
    Thanks for your help nerowolfe.
    If I ping or put in browser any IP, it answer immediately. It's just the resolution.
    Then the problem lies with your DNS, perhaps your ISP DNS are simply slow.
    I use OpenDNS servers in my router and computer and have very little latency.
    Here is their webpage
    http://www.opendns.com/solutions/homenetwork/

  • Slow DNS Resolution using Time Capsule

    Hello,
    I'm using a time capsule as my main internet router and wireless access point, and I've noticed a significant delay before web pages begin to download.  In trying to troubleshoot this, I came across a very helpful utilitity called the Netalyzr from Berkley.  Using this tool, I'm able to see that there is a significant delay in name lookups using the time capsule DNS proxy capability.  There's not a lot of documentation on this, but it appears that instead of handing clients the designated DNS servers configured in DHCP, it hands out its own address to the clients as the DNS server and makes the DNS request to the configured servers.  I've included the verbage from the Netalyzer tool below.
    Your ISP's DNS resolver requires 2200 msec to conduct an external lookup. It takes 81 msec for your ISP's DNS resolver to lookup a name on our server.
    This is particularly slow, and you may see significant performance degradation as a result. 
    As you can see, this causes almost a 2.5 second "pause" before the lookup is even returned.  However, if I hard code the designated DNS servers into this client (Macbook air running Lion), I get the following result.
    Your ISP's DNS resolver requires 110 msec to conduct an external lookup. It takes 81 msec for your ISP's DNS resolver to lookup a name on our server. 
    This is a significant improvement over the lookup using the proxy capabilities of the Time Capsule.  This leads me to believe that the DNS "proxying" that the time capsule is doing is really slow.
    I'm using opendns as my provider in both scenarios.
    Is this a known issue, and if so, is there an existing fix or a planned fix for this?
    Best,
    Eric

    Frankly I just don't believe those analysers.. not until I can prove it myself.
    Do a very simple test..
    Open terminal  and ping a website you have never opened before.
    You should do this from a PC or Mac on the network using ethernet. Just to keep crummy wireless responses out of it. And do it without internet activity going on.
    Do it a second time, and it should be instantaneous now having the address resolved and held in the cache.
    If you get a significant lag before the address is resolved to actual IP, there maybe something wrong. And the first test then would be to change the DNS server to your local ISP not opendns.. because the routing to opendns might also be an issue.
    You can also test by removing the TC from the network..plug a computer directly to the modem and just browse.. compare that to speed with the TC. I know it isn't exactly scientific but a 2.5sec delay in dns resolution you will notice it. It is important to connect to stuff that is outside your normal pattern. Otherwise it should just be in the cache.
    Otherwise it is unlikely to really exist.

  • RV082 - Slow DNS Resolution

    Greetings Gang,
    Have an RV082 v1.1 FW 1.3.98-tm that has been rock solid for a couple of years and is now, suddenly, experiencing dead crawl DNS resolution.
    No changes in configuration prior to the behavior starting. Tried rebooting the unit, no changein behavior.
    There's an internal DNS server that resolves internal resources, but everything else gets pushed to the RV082.
    I've tried Comcast, Verizon and Google DNS servers at the router level, and the results are the same -- so that rules out the DNS servers themselves.
    Change the DNS servers at the NIC level on a wrokstation, and resolution occurs quickly and reliably.
    I'm looking to reset to Factory Default and reload the configuration and likely upgrade to FW 2.0.0.19-tm or 2.0.2.01-tm but I do see similar issues reported with those firmwares, and moreover, in a mixed Mac/PC environment.
    Was wondering if anyone else has experienced these issues, could identify a root cause and resolution.
    Thanks,
    Jorge

    Probably just corruption, which can happen every so often.  A couple of years in service rock-solid is really great.
    I experienced similar problems with my rv016s when my ISP changed their backend carrier equipment.  I was never able to fix the issue, so I had to reboot them every 8hrs.
    I wouldn't upgrade unless you HAVE to.  You'll more than likely run into other bugs that breaks your current configuration, even if it's just a site-to-site VPN (I've been there, done that).
    Huntsville's Premiere Car and Bike e-magazine: www.huntsvillecarscene.com

  • Slow loading web pages

    My iMac G5 used to perform just fine. But for the past 4-5 days any internet content seems to load at a "snails pace", even compared to my older Powerbook G4. I thought it my have had something to do with Simplify Media program for iPhone, so I deleted, but made no difference. I also ran all sorts of cleaning and maintenance with Onyx. Any ideas why my Mac has gotten "tired"???

    Try this:
    The following usually works on both Tiger and Leopard:
    Many, including me, have had success with adding DNS codes to their Network Settings, with good results in terms of speed-up:
    Open System Preferences/Network. Double click on your connection type, or select it in the drop-down menu. Click on TCP/IP and in the box marked 'DNS Servers' enter the following two numbers:
    208.67.222.222
    208.67.220.220
    Click on Apply Now and close the window.
    Restart Safari, and repair permissions.
    If that didn't do it, then try this as well:
    Empty Safari's cache (from the Safari menu), then close Safari.
    Go to Home/Library/Safari and delete the following files:
    form values
    download.plist
    Then go to Home/Library/Preferences and delete
    com.apple.Safari.plist
    Repair permissions (in Disk Utility).
    Start up Safari again, and things should have improved.
    Less likely, but possible, is that the slowness is caused by a Trojan such as the one called 'DNSChanger' or 'OSZ.RSPlug', which can alter the DNS settings of your network connection. This particular Trojan can be inadvertently installed if you have come across certain Quicktime movies where got a window stating that you have to download and install a particular codec in order to see the video.
    If you have agreed to that installation, your system can be infected and your DNS settings altered, which results in your system using the wrong DNS servers, which can slow web surfing to a crawl.
    This can be fixed by downloading and running a freeware utility called DNSChanger Removal Tool which you can download from here:
    http://www.versiontracker.com/dyn/moreinfo/macosx/33696
    Once you have run that utility you have to re-boot your Mac, then reset Safari, and re-enter your DNS settings in System Preferences/Network.

  • My iMac is slow accessing web sites.

    My iMac is slow accessing different web sites.  I also have a PC that doesn't seem to have the same problem.  Any suggestions.  All other programs on the computer run fine.  This has only started about a month ago.  Any suggestions?

    If Safari is getting very slow:
    (Presumably you regularly empty your Safari cache by deleting the following file:
    Home/Library/Caches/com.apple.Safari/cache.db
    and clear your History)
    Adding Open DNS codes to your Network Preferences, should give good results in terms of speed-up as well as added security, including anti-phishing and redirects) (Full information about Open DNS is here: http://www.opendns.com/home/nobloat )
    If you are using a single computer: Open System Preferences/Network. Double click on your connection type, or select it in the drop-down menu, and in the box marked 'DNS Servers' add the following two numbers:
    208.67.222.222
    208.67.220.220
    (You can also enter them if you click on Advanced and then DNS)
    Sometimes reversing the order of the DNS numbers can be beneficial in cases where there is a long delay before web pages start to load, and then suddenly load at normal speed:
    http://support.apple.com/kb/TS2296
    If your computer is part of a network:please refer to this page: http://www.opendns.com/start/best_practices/#your_network and follow the advice given.
    If you use a Router, make sure it has the latest firmware installed.
    One reason for a slowness in page loading may be the 'DNS Pre-fetching' feature of Safari 5.x as is described here:
    http://support.apple.com/kb/TS3408?viewlocale=en_US
    You can cancel DNS pre-fetching by going to Terminal and typing:
    defaults write com.apple.safari WebKitDNSPrefetchingEnabled -boolean false
    You have to restart Safari for it to take effect.
    If Safari seems to hang for ages:
    If you have a lot of tabs open and/or a lot of pages running Flash, Safari can sometimes 'hang', requiring a restart of Safari. This can often be inconvenient, and as it is rarely Safari itself that is hanging but merely one of its plug-ins, usually Flash, there is a way using Terminal to restart the plug-ins (without restarting Safari and losing your tabs) by quitting the WebPluginHost process:
    Open the Terminal from the Utilities folder in /Applications and type
    killall -9 WebKitPluginHost
    Note that this command kills all Safari plug-ins, not just Flash. All plug-ins should start back up when you reload the page.
    Then go back to Safari and refresh any pages that were using the Flash plug-in. This also fixes the Beachball of Death. Try this whenever Safari gets slow or freezes. The latest versions of Flash 10.1 appear to have improved the situation somewhat, but haven't completed eliminated it.
    For this and other reasons Apple switched their websites to HTML5 in January 2011:
    http://www.appleinsider.com/articles/11/01/26/apple_revamps_its_public_website_u sing_html5.html

  • Slow DNS lookup

    For the past two days, my internet has really slowed down.  The problem appears to be a "pokey" DNS server.  In many cases, it would take longer for the DNS server to work, than to download the web pages.  This morning, the problem seems fixed -- DNS lookup is pretty much "instantaneous" again.  I still have my DNS settings to let Comcast determine the server.  Is it OK if I change the settings to a specific DNS Server?  If so, does anyone have any recommendations about which one to use?  TIA ---

    Try using the Google or the OpenDNS offerings. Search google for info.

  • DNS/web-server hosted off-site. How to set up Leopard server for mail?

    Hey Everyone,
    Brand new xserve with leopard server 10.5.2. Currently, Our web and DNS server for our domain,"company.com" is co-located off-site with an MX record of "mail.company.com" pointed at the static IP of the office where our mail server is. I want to replace the mail server with the xserve. With that in mind, how do I configure the DNS on the xserve during initial configuration to reflect that? Give it a self-referencing FQDN like server.company.office and see if the mail service can handle the domain hosted elsewhere?
    I'm pretty new to servers and would love be able to keep this all in Standard but I'm not afraid to jump into Advanced if need be. I've created a test domain through GoDaddy of "company2.com" with an MX record of "mail.company2.com" pointing at the IP address of the xserve. Any help would be greatly appreciated!

    Hello,
    Have a look at this blog post:
    http://blogs.adobe.com/captivate/2010/08/reporting-the-quiz-results-to-a-local-server.html
    Lilybiri

  • My tx is so slow, the web cam is not working, the screen freezes and got color distortions

    - My tx is so slow, and heats up very fast... so i think that the advance is not working properly
    - the web cam is not working, since the 3th time iused... when i try to use it with my msn... got freezed, then y try ending the process and doesnt work, y     have to restart it but it stay just on logging off... and do nothing more... so i have to switch off directly from the power button
    - The screen freezes... some thimes the screen got freezed... and got color distortions too... so i have to to switch off again directly from the power button
    i was thinking that it was a software problem... but i restore my lap and it doesnt work cuz it still being with the same problems... so lately im thinking that its a hardware problem... i call to technical support from mexico... but they can do nothing for me cuz i bought my lap at circuitcity from el paso... and that store close a few months ago... so i need help before de warrantie expires...
    This is the second time that my lap gives me problems, last time I made the change at the store but this time it will be impossible cuz is now closed...
    that is why I seek your help...
    i will be grateful if you answer in Spanish because my English is not very good...
    thankyou so much...

    If your warranty has not yet run out get it serviced, now!  All of the comments seem to indicate that it is the motherboard>

  • New, Single Server - DNS, Web, Wiki, Mail Setup Issues

    I'm having some issues properly setting up 10.7.3 to host internal DNS and external Web, Wiki and Mail.  I'm having issues with the web and wiki hosting.  Since those are the most important right now, I haven't really had a chance to fully test the other features.  I was able to do some testing of the mail and iCal but it was limited.
    Long read below but I thought the specifics would be helpful...
    My goals and configuration are:
    ***GOALS***
    Primary:
    1) Host a public website: example.org and www.example.org
    2) Host a public wiki: main.example.org and www.main.example.org
    3) Host a public mail server: [email protected]
    4) Host a public, group calendar
    4a) Read only to majority - Read/Write to a group
    5) Host a global address book for authenticated users
    Secondary:
    6) Allow anonymous public access to a file share (read only)
    7) Allow authenticated access to the same file share (read/write)
    8) Do as much of this via GUIs as possible.
    ***SETUP AND CONFIGURATION***
    Physical:
    1) Business class Internet (no blocked ports)
    2) A single, public and static IP address
    3) Domain name and public DNS via GoDaddy
    4) Wildcard Cert: *.example.org from GoDaddy
    5) Late 2011 (bought in Jan 2012) MacMini Lion Server (the $1,000 one).
    5a) Upgraded the RAM to 16GB (need for VMware Windows clients)
    5b) Added two USB to Ethernet adapters.
    6) Using a new model AirPort Extreme Base Station (bought w/ the MM) as the main router.
    Initial Configuration:
    7) Setup a Mac Address reservation for the main and two USB Ethernet ports along with the wireless too.
    7a) Main port = 10.0.1.5 / Others are .6, .7 and .10
    8) During the setup, I chose the Host on the Internet (third) option and named my server: main.example.org
    9) After the setup completed, I upgraded the OS & Admin Tool to 10.7.3 from a clean install (on #5 now)
    DNS Config
    10) I used the admin tool to open DNS and change:
    11) "Primary Zone Name" from main.example.org to example.org.
    12) In the "Nameservers:" block, I changed the zone name there but left the nameserver name alone (zone: example.org /// Nameserver Hostname: main.example.org).
    13) The Machine Name and Reverse Zone was left alone.  RZ resolves to main.example.org.  sudo changeip -checkhostname is good.  dig on the example.org and main.example.org are good to go (NOERROR).
    OD Config
    14) From the server app, I clicked Manage/Network Accounts and setup the OD - No issues.
    SSL
    15) From the server app, I created self signed cert, generated a CSR, got a public Cert, then replaced the self-signed with the public one - No issues.
    16) Changed any service using the self-signed cert to the public one - No issues.
    17) Changed the cert in the OD to the public cert from server admin - No issues.
    In order: File Sharing, Mail, AB, iCal, Web, Wiki, Profile Manager, Network Groups, Network Users
    18) File Sharing was setup using the server app
    19) Setup mail using the server app to start it and the server admin app to configure it - No issues there (I think...)
    20) AB - Flipped the switch to on
    21) iCal - Flipped the switch to on - I setup the e-mail address to use after I added the network accounts.
    22) Web - Flipped the switch to on - Default site worked (main.example.org)
    23) Wiki - Flipped the switch to on - Default wiki worked. (main.example.org)
    24) PM - Checked the sign config profiles and enabled the device mgt.  I then flipped the switch to on - Default settings and pages worked.
    ***MY PROBLEMS***
    Website:
    Adding a website for example.org gave me the red dot in the server app.  To fix that, I added a Machine Name record to my primary zone (PZ = example.org Machine Name = example.org).  I first tried using the same 10.0.1.5 IP as the main.example.org and left the reverse mapping alone (still resolved to the NS of main.example.org).
    That gave me the green light in the server app when trying to add the website again.  From there, I changed the "Store Site Files In" to the location of my website files (and confirmed "Everyone" has Read Access in the folder's security settings).  I left the other info alone (all defaults accepted) and clicked done.
    Access to the website works on the server but external access doesn't (Network Error/timed out tcp_error).  Checked the AirPort settings using the AirPort utility (version 5.5.3) and the Port Mapping (under the "Advanced" icon) show serveral services all pointing to 10.0.1.5.  Thinking it could be DNS I tried main.example.org externally and it failed the same way.
    I ran the changeip command (good to go) and dig on example.org and main.example.org and they both resolved to 10.0.1.5 correctly.
    I removed the example.org Machine Record from the zone and it now looks like:
    PZ=example.org / ZONE=example.org / NS=main.example.org
    Machine Record=main.example.org / IP=10.0.1.5
    RM=10.0.1.5 / Resolves=main.example.org
    PLEASE HELP!

    The amount of users (if relevant):
    On site - 1 (Me)
    Off site - 16 (Windows clients - some have iOS devices too)
    Web site traffic - less than 50 regular visits per day (avg of 15) with a peek of ~125 once a month.
    This is for a 501c3 public nonprofit made of all unpaid volunteers (including the officers and directors).  All of us have paying day jobs and I just so happen to be the guy that knows just enough to get myself in trouble here.

  • [SOLVED] Slow DNS lookup, I think

    Hi
    I have a really annoying problem. My DNS lookup in Arch is painfully slow. I know it's not a network problem, as I don't have any problems in my Ubuntu installation. I have tried to run two simple tests to show you what I mean. The first is a simple ping google.
    ########### Ubuntu ###########
    carsten@carsten-laptop:~$ time ping -c 3 www.google.com
    PING www.l.google.com (216.239.61.104) 56(84) bytes of data.
    64 bytes from sn-in-f104.google.com (216.239.61.104): icmp_seq=1 ttl=245 time=17.4 ms
    64 bytes from sn-in-f104.google.com (216.239.61.104): icmp_seq=2 ttl=245 time=20.6 ms
    64 bytes from sn-in-f104.google.com (216.239.61.104): icmp_seq=3 ttl=245 time=11.4 ms
    --- www.l.google.com ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2002ms
    rtt min/avg/max/mdev = 11.465/16.529/20.641/3.809 ms
    real 0m2.290s
    user 0m0.000s
    sys 0m0.004s
    ########### Arch ###########
    carsten ~/Desktop $ time ping -c 3 www.google.com
    PING www.l.google.com (216.239.61.104) 56(84) bytes of data.
    64 bytes from sn-in-f104.google.com (216.239.61.104): icmp_seq=1 ttl=245 time=12.3 ms
    64 bytes from sn-in-f104.google.com (216.239.61.104): icmp_seq=2 ttl=245 time=10.7 ms
    64 bytes from sn-in-f104.google.com (216.239.61.104): icmp_seq=3 ttl=245 time=12.4 ms
    --- www.l.google.com ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2007ms
    rtt min/avg/max/mdev = 10.776/11.867/12.476/0.778 ms
    real 0m15.305s
    user 0m0.013s
    sys 0m0.007s
    Ubuntu: 0m2.290s vs. Arch: 0m15.305s.
    In the second test I tried to fake a pacman update by downloading the .db files from my primary server. On both Ubuntu and Arch I used this simple script
    repos=( core extra community )
    time for repo in ${repos[@]}
    do
    wget http://archlinux.unixheads.org/$repo/os/i686/$repo.db.tar.gz
    done
    When I run it in, I get this result
    ########### Ubuntu ###########
    carsten@carsten-laptop:~/Desktop$ ./updatetest
    --2008-11-10 07:58:23-- http://archlinux.unixheads.org/core/os/i686/core.db.tar.gz
    Resolving archlinux.unixheads.org... 204.152.186.174
    Connecting to archlinux.unixheads.org|204.152.186.174|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 32515 (32K) [application/x-gzip]
    Saving to: `core.db.tar.gz'
    100%[=============================================================>] 32.515 --.-K/s in 0,1s
    2008-11-10 07:58:23 (331 KB/s) - `core.db.tar.gz' saved [32515/32515]
    --2008-11-10 07:58:23-- http://archlinux.unixheads.org/extra/os/i686/extra.db.tar.gz
    Resolving archlinux.unixheads.org... 204.152.186.174
    Connecting to archlinux.unixheads.org|204.152.186.174|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 422622 (413K) [application/x-gzip]
    Saving to: `extra.db.tar.gz'
    100%[=============================================================>] 422.622 242K/s in 1,7s
    2008-11-10 07:58:25 (242 KB/s) - `extra.db.tar.gz' saved [422622/422622]
    --2008-11-10 07:58:25-- http://archlinux.unixheads.org/community/os/i686/community.db.tar.gz
    Resolving archlinux.unixheads.org... 204.152.186.174
    Connecting to archlinux.unixheads.org|204.152.186.174|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 369845 (361K) [application/x-gzip]
    Saving to: `community.db.tar.gz'
    100%[=============================================================>] 369.845 206K/s in 1,8s
    2008-11-10 07:58:27 (206 KB/s) - `community.db.tar.gz' saved [369845/369845]
    real 0m3.837s
    user 0m0.016s
    sys 0m0.036s
    ########### Arch ###########
    carsten ~/Desktop $ ./updatetest
    --2008-11-10 08:01:33-- http://archlinux.unixheads.org/core/os/i686/core.db.tar.gz
    Resolving archlinux.unixheads.org... 204.152.186.174
    Connecting to archlinux.unixheads.org|204.152.186.174|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 32515 (32K) [application/x-gzip]
    Saving to: `core.db.tar.gz'
    100%[==============================================================================>] 32,515 --.-K/s in 0.1s
    2008-11-10 08:01:47 (303 KB/s) - `core.db.tar.gz' saved [32515/32515]
    --2008-11-10 08:01:47-- http://archlinux.unixheads.org/extra/os/i686/extra.db.tar.gz
    Resolving archlinux.unixheads.org... 204.152.186.174
    Connecting to archlinux.unixheads.org|204.152.186.174|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 422622 (413K) [application/x-gzip]
    Saving to: `extra.db.tar.gz'
    100%[==============================================================================>] 422,622 253K/s in 1.6s
    2008-11-10 08:02:02 (253 KB/s) - `extra.db.tar.gz' saved [422622/422622]
    --2008-11-10 08:02:02-- http://archlinux.unixheads.org/community/os/i686/community.db.tar.gz
    Resolving archlinux.unixheads.org... 204.152.186.174
    Connecting to archlinux.unixheads.org|204.152.186.174|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 369845 (361K) [application/x-gzip]
    Saving to: `community.db.tar.gz'
    100%[==============================================================================>] 369,845 262K/s in 1.4s
    2008-11-10 08:02:17 (262 KB/s) - `community.db.tar.gz' saved [369845/369845]
    real 0m44.153s
    user 0m0.047s
    sys 0m0.017s
    Ubuntu: 0m3.837s vs. Arch: 0m44.153s
    I get the same update time whenever I update pacman normally.
    I have googled a lot to figure out an answer, but nothing helps, so I was hoping somebody could help me figure this out, as it's very annoying. My hosts file looks like this
    hosts:
    # /etc/hosts: static lookup table for host names
    #<ip-address> <hostname.domain.org> <hostname>
    127.0.0.1 localhost.localdomain localhost arch
    # End of file
    rc.conf:
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # HARDWARECLOCK: set to "UTC" or "localtime"
    # USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="en_US.utf8"
    HARDWARECLOCK="UTC"
    USEDIRECTISA="no"
    TIMEZONE="Asia/Singapore"
    KEYMAP="dk"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
    # MOD_BLACKLIST: Prevent udev from loading these modules
    # MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
    # NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
    MOD_AUTOLOAD="yes"
    #MOD_BLACKLIST=() #deprecated
    MODULES=(e100 mii iwl3945 fuse acpi-cpufreq cpufreq_ondemand cpufreq_conservative cpufreq_powersave loop !pcspkr !snd_pcsp)
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="arch"
    # Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
    # Interfaces to start at boot-up (in this order)
    # Declare each interface then list in INTERFACES
    # - prefix an entry in INTERFACES with a ! to disable it
    # - no hyphens in your interface names - Bash doesn't like it
    # DHCP: Set your interface to "dhcp" (eth0="dhcp")
    # Wireless: See network profiles below
    #eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
    eth0="dhcp"
    INTERFACES=(!eth0 !wlan0)
    # Routes to start at boot-up (in this order)
    # Declare each route then list in ROUTES
    # - prefix an entry in ROUTES with a ! to disable it
    gateway="default gw 192.168.0.1"
    ROUTES=(!gateway)
    # Enable these network profiles at boot-up. These are only useful
    # if you happen to need multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This now requires the netcfg package
    #NETWORKS=(main)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    DAEMONS=(syslog-ng !network hal !netfs crond fam wicd cups laptop-mode oss gdm)
    SPLASH="splashy"
    Thanks in advance!
    Last edited by Sharpeee (2008-11-15 10:39:42)

    Just tried to remove the "search..." line from my /etc/resolv.conf file, but nothing! It's okay if I remove the line after it connects right? Wicd overwrites the file anyways if I reconnect.
    I don't really think changing to a different network-manager will help me. It works perfectly fine in Ubuntu with both network-manager and wicd, do don't think that's the problem. It must be a configuration file somewhere.
    #### EDIT ####
    I just tried to disable wicd and enable the wired network in /etc/rc.conf. After a reboot and it's still the same, even on the wired, so it's got be some other settings somewhere that's messing things up!
    Also, for some reason my theme, in Gnome, isn't loaded after I disabled wicd? I have to manually run "gnome-appearance-manager"??
    Last edited by Sharpeee (2008-11-11 05:01:46)

  • Wireless Intermittent Super Slow DNS lookup bug in 10.6.4

    I don't normally post things on forums these days, as usually I can find just about any solution by searching long enough, but this issue has perplexed me to the point I actually had to come on here.
    Believe me, that's a big deal, I don't give up easily.
    I have spent -countless- hours searching, on here, on google, on any "solutions" or "technical" sites I could find, and the closest I can find to a solution are countless people complaining about the EXACT SAME PROBLEM that I have observed and, repeatedly, reproduced again and again, which in every single case boil down to this:
    You had 10.6.x (x being 3 or less) with a wireless connection on your home network and all is well.
    You upgraded to 10.6.4 and all seemed fine for maybe 24 hours or so... then it happens. You go to load a website, and it's "looking for site" or "waiting for site" in your status bar... hmm, maybe it's just this site you say, so you try another, or a few others in other tabs, but they all have the same problem.
    You try to ping the sites, but the network utility can't resolve the domain to even ping them.
    Your roommate, all the while, is surfing and gaming just fine on the exact same router you are on, so no, it's not the network hardware, it's not your ISP, hmm, what could it be?
    All of a sudden, ALL of the sites you had in like 20 tabs load up at screaming speeds, "WOW" you say, "guess there must have just been some gunk in the wires or something" (notice the irony of the situation: no wires)... anyway, all seems fine again suddenly, surfing is fine for a few minutes, you're back to normal... and it happens again, suddenly NO site will resolve, NO dns will resolve, you can't check email or ping any domain... and so the cycle begins. Of course, you can just plug an ethernet cable straight into the router, but doesn't that kind of defeat the purpose of having wireless networking in the first place?
    It continues like this, indefinitely, and it all starts roughly 24 hours after 10.6.4 has been installed.
    I have read reports of people on macbooks, people on imacs, people on all sorts of different wireless hardware, but the symptoms are the same.
    I know the problem is with the OS update, it's purely software. I know that it has nothing to do with hardware because simply reverting to 10.6.3 solves the problem -every single time- and then "upgrading" to 10.6.4 causes the problem to come back within 24 hours -every single time- (have been reverting using Time Machine to simplify this testing process), so no, where the problem is isn't what perplexes me; what perplexes me is that there are posts that started almost a few days after 10.6.4 came out, and so far there's STILL no fix? Are you freaking serious? Does the Apple programming team not have access to anything other than Apple-Branded Airport Extreme Base Stations to perform wireless network QA testing on?
    Get a Linksys guys, grab a D-Link, go get some of the hardware people actually USE and test it on that and see what happens, it doesn't take long to see what's happening.
    I blame the programmers because I am one myself and know how easy it is to screw up a rock-solid system with one little typo. Heck, which patch was it, 10.5.7 or 10.5.8 I think? Can't remember exactly, but it was supposed to be such a great "bug fix" patch... and it came with the config file for Apache set to DENY ALL INCOMING EXTERNAL CONNECTIONS by default (in a hidden file that can only be modified by the root user mind you... so much for the average user running a personal web server on THAT version), so yeah, one tiny mistake and it has huge consequences, my question is: what's taking so long to track down what's going on in 10.6.4 and fix it? Can we at least get a patch or something?
    I find it really lame and really such a cop-out to see so many irrelevant "solutions" offered, "try specifying different DNS servers" (doesn't matter, whatever causes this bug doesn't care which servers you have specified, it simply sits there and does NOTHING for 2-3 minutes, and THEN when it actually DOES do a dns lookup, it gets the results in the time expected: instantly), to more extreme matters, like resetting hardware, which again has absolutely nothing to do with this bug.
    Here is why anyone can see this is an obvious bug that the programming team needs to admit, investigate and correct:
    A. happens immediately after the software update
    B. happens to EVERYONE who uses traditional wireless routers for internet use
    C. is 100% repeatedly reproducible
    D. occurs on all different models of computers and all different ISP's and with all different DNS servers specified.
    E. has the same symptoms on every system (lightning fast internet for 2-3 minutes, then "waiting for site" for 1-3 minutes)
    F. affects EVERY network-using program on the computer (email, network utility, firefox, safari) SIMULTANEOUSLY
    G. does not affect surfing to or interacting with IP addresses directly, only with trying to perform DNS lookups from ANY program with ANY dns server (or no dns server) set in network preferences.
    Come on guys, just read it through, think about it for a few minutes, for anyone that has worked with and knows the underlying source code, and what changes went in between 10.6.3 and 10.6.4 specifically to networking, should have a light bulb pop up over their head and say "oh YEAH, we never uncommented that one line..." or something to that effect.

    I see a very similar issue, but it's been occurring on my laptop for 4 or 5 months, which must be way before 10.6.4. My roommate and friend's laptops all work fine on my network. And my laptop works fine on anyone else's network. But MY laptop on MY network always gives the abysmal DNS performance as described in the original post: 40% of requests time out. Wireless or wired, it doesn't matter. Exact same behavior.
    It also doesn't matter whether I use my Netgear router as DNS server, or my ISP, or OpenDNS, or Google. Exact same behavior.
    When I do a network trace, it looks like most DNS requests my computer sends out simply never get responded to. (Could they be malformed when they hit the wire? I don't even see an error reply) A few make it through. And when there's a IPv6 (AAAA) record sent, my computer returns a "port unreachable" ICMP message. A screenshot of all of this dialogue is here:
    http://img545.imageshack.us/i/screenshot20100913at114.png/
    I recently had opportunity to cancel my cable service, and reinstate it for a lower price. They came out, tested the line (strong signal), gave me a new cable box. Yet the issue persists. Exact same behavior.
    Firewall is disabled. I've deleted the network interfaces and added them back. Nothing helps.
    (As I recall, this issue may even have been present before I reinstalled 10.6 over 10.5, so I'm not too confident a total reinstall would help.)
    Any help? I'm about ready to buy a new laptop to fix this damned problem. Web browsing is nearly impossible, as is.

Maybe you are looking for