Resolving DNS issues!

When I type "changeip" to change the host name of one of my Servers in school I get and error saying that there is no DNS server associated with the ip address of my server. Also when I type host command I get also an error saying the server can't be found. How do I approach these issues so I can resolve all the DNS problems and I can correctly connect to my server? Thanks

If it's an OD master and hosting it's own zone file locally, it's better (in my opinion) to configure BIND to use your ISP nameservers as forwarders, and put 127.0.0.1 into the DNS Servers field, in System Prefs > Network. To setup BIND forwarding, open your "/etc/named.conf" file (back it up first!) and look for:
zone "." IN {
type hint;
file "named.ca";
...and replace with...
zone "." IN {
//type hint;
//file "named.ca";
type forward;
forwarders {
1.2.3.4;
5.6.7.8;
...where 1.2.3.4 and 5.6.7.8 are the DNS server IP's you got from the admins. Then, as mentioned above, put "127.0.0.1" in the server Network configuration as the only resolver.
Reboot the server for good measure, and then try (from the server):
host yourdomain.com 127.0.0.1
host x.x.x.x 127.0.0.1 (where x.x.x.x is the local IP address of your server).
Both should resolve properly - if not, you probably have a DNS zone file configuration error.
At this point, you should be able to use the "changeip" command properly.
MacBook Pro   Mac OS X (10.4.8)  

Similar Messages

  • Resolving DNS Issues & Kerberos

    Server Admin reports that kerberos is disabled for both my master and replica OD servers. In trying to correct this, I found that your DNS has to be working completely before kerberos will function. However, I hit a snag when trying to fix the DNS problems on both servers.
    Our master and replica servers are in a windows dominated network. Our windows PDC serves as the DNS server for the whole network, including the mac servers. Since the PDC didn't contain DNS entries for the mac servers I added them. After this, I read that a FQDN needs to be used, but both mac servers were *.local. I assumed that the changeip command would let me change this, so I peformed the following command on the master OD server:
    +changeip /ldapv3/127.0.0.1 10.0.10.141 10.0.10.141 xserveg5.local xserveg5.OurWindowsDomain.net+
    *note that I'm purposely omitting the name of our windows domain for privacy.
    This is what terminal then shows:
    +Updating Local node+
    +Updating node /LDAPv3/127.0.0.1+
    +Enter admin name for node /LDAPv3/127.0.0.1: **enters admin name**+
    +Password: **enters password**+
    +Updating Password Server config+
    +Updating OPen Directory config+
    +Updating hostconfig file+
    +Updating smb.conf file+
    +Updating smb.conf file+
    +Updating Kerberos Service Principals and keytabs+
    +Please enter the name of the administrator account for OurWindowsDomain.net: **enters a domain admin username**+
    +Please enter the password for [email protected]: **enters password**+
    +Authenticating as principal [email protected] with password.+
    +Password for [email protected]:+
    +Password for [email protected]:+
    Terminal just sits there and does not continue on. I am not sure if it doesn't like my domain admin username and maybe I need to use the administrator user, although I assume it would be the same. Any way, I'm hesitating to try the admin username as I'm not sure what will happen if it's successful. Will the changeip command attempt to modify active directory or anything on the Windows side? I can't afford for this to mess anything up on the Windows side of the network.
    I'm assuming that I need to make the FQDN of the mac servers part of the windows domain by using it in the changeip command. Is this necessary? The macs are not being accessed by any windows computer or vice versa. Could I just make up my own FQDN for the macs or will that not work?
    Thanks.

    You can make up your own FQDN for your Mac servers and clients and setup DNS on your Mac server. If you try to integrate your Macs with the AD and two different FQDN's, you may run into some road blocks. If you're happy to run your own OD network, you should be fine. Your Macs will still be able to access services on the Windows servers, but I don't think you'd be able to bind Macs to AD services in this setup. Even if you did, the .local suffix will cause headaches in an OD.
    hth
    Jeff

  • So my airport extreme recently had some nat/dns issue and in the airport utility displayed a warning about it and to correct it. I wasn't sure what to do so i pressed the resolve icon and now my guest network is not working.

    So my airport extreme recently had some nat/dns issue and in the airport utility displayed a warning about it and to correct it. I wasn't sure what to do so i pressed the resolve icon and now my guest network is not working.

    Anytime you change networking hardware, it is always a good idea to perform a complete power recycle of your networking components.
    I would recommend that you do the following as a minimum:
    Power-down the modem, AirPort base station, and computer(s).
    Disconnect the AirPort base station from the Internet broadband modem.
    While all of the devices are powered-down, perform a "factory default" reset on the base station. This will get it back to its "out-of-the-box" configuration and make setting it up much easier, especially if you use the "Assist me" process within the AirPort Utility. (ref: Resetting an AirPort Base Station or Time Capsule)
    After the base station resets, go ahead and power it back down.
    Reconnect the AirPort base station to the Internet broadband modem. For the Extreme and Time Capsule, be sure to connect the cable to the base station's WAN (circle-of-dots) port.
    Power-up the modem; wait at least 10-15 minutes to allow it adequate time to initialize.
    Power-up the AirPort base station; wait at least 5-10 minutes. Note: The AirPort's status light may continue to flash amber after it has intialized. That is because, there may be some additional configuration items necessary, like setting up wireless security, before the overall setup is completed to get a green status.
    Power-up your computer(s).
    In this basic configuration, the AirPort base station will broadcast an unsecured wireless network with a Network Name (SSID) of Apple Network NNNNNN. Network clients, connected to the base station either by wire or wireless, should now be able to access the Internet through the ISP's modem. Once Internet connectivity has been verified, you can use the AirPort Utility to configure the base station for wireless security and any other desired options. Please post back your results.

  • Dns issues with one domain (Resolved)

    i'm currently having dns issues with one domain, in that it won't resolve when I use bt's dns servers.
    The domain is owned by a friend in the US who runs his own server for irc, web, and I also have a server that is on his connection, and resolves fine from other machines on different networks, and also resolves fine when I set windows to use the opendns servers, but when it's set to either my routers ip (using bt's dns), or set to automatic (using bt's dns via the homehub), this one domain will not resolve.
    I'm pretty certain it's not a windows issue, as it's a clean install of windows 7 that I did yesterday. I've tried rebooting the homehub, and also flushing my dns on windows, but this has not solved the issue.
    As I say, it resolves fine on other networks, and also when I use the opendns servers, so I know it's definately a dns issue.
    Using bt's dns servers:
    C:\Users\admin>ping chatnsn.com
    Ping request could not find host chatnsn.com. Please check the name and try agai
    n.
    Using opendns:
    C:\Users\admin>ping chatnsn.com
    Pinging chatnsn.com [68.51.24.74] with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Ping statistics for 68.51.24.74:
        Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
    (The timeouts are normal...he has his router set to not respond to ping requests).
    Has anyone got any ideas on how to sort this out? Preferably without having to phone the helpdesk...lets just say i've done it in the past, and according to the poeple I spoke to in india, I knew nothing about my own systems, and it was a problem at my end...which was not the case, and I proved this several times.
    Edit: This issue appears to have resolved itself, and the domain is now resolving again using the homehub for dns resolution.

    Hi,
    When NSLOOKUP starts, before anything else, it checks the computer's network configuration to determine the IP address of the DNS server that the computer uses.
    Then it does a reverse DNS lookup on that IP address to determine the name of the DNS server.
    If reverse DNS for that IP address is not setup correctly, then NSLOOKUP cannot determine the name associated with the IP address.
    http://support.simpledns.com/kb/a90/nslookup-cant-find-server-name___-default-server-unknown.aspx
    Also refer to:
    How to fix NSLOOKUP Default Server: UnKnown?
    http://www.randika.info/2013/01/how-to-fix-nslookup-default-server.html
    Regards.
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • How to resolve network issue or dns to access web page on snow leopard server?

    I have my network setup like as follows:
    internet > router 1 > ethernet ports > switch > router 2
    I have a mac osx snow leopard server connected to "router 1", but it is so slow when accessing a web page hosted on the server from a browser on a workstation connected to either router 1 or router 2?
    Is there a problem with my network setup or maybe because I changed the name to newservername.local?

    @Jeff and @Camelot,
    I think it is a DNS issue.  I completely reset the DNS settings on server and the local name with the steps below, but now cannot access the site hosted on the server at all
    I used a modified version of http://www.mkahn.com/2010/09/configuring-dns-on-mac-os-x-10-6-snow-leopard-serve r-for-hosting/ to reset the server set
    1.  Stop DNS Service in Server Admin
    2.  Close Server Admin
    3.  Obtain 10.6 DNS Default files (below)
    4.  Overwrite the DNS files with DNS Default files:
    /etc/dns/loggingOptions.conf.apple
    /etc/dns/options.conf.apple
    /etc/dns/publicView.conf.apple
    /var/named/named.ca/etc/named.conf
    /var/named/named.local
    /var/named/localhost.zone
    5. Restart your server
    All machines have 1ms ping responses within the network including this snow leopard server that I am trying to setup.  There is another test web server that return pages instantly within this network so I doubt it is a network issue, but a DNS issue.

  • Windows 7 Pro DNS issue with static IP

    0
    down vote
    favorite
    I have been unable to solve a DNS problem I am having as follows:
    I have a Windows 7 Professional (64 bit) computer running VirtualBox with a couple of Windows XP guests (not sure if this bit is relevant). After heavy file copying/transfer on both of the Windows XP machines, both the guest machines AND the host loose anything
    DNS related, so I cannot call anything by name, but by direct IP works fine. The only resolution is to reboot the (host) machine and it will then work OK for a while until it happens again. The only trigger to make it seem to happen quicker is to re-initiate
    the heavy file transfer and this then causes the DNS resolution to stop working again.
    The machine has a fixed IP address, so it isn't related to DHCP.
    I've tried the machine connected wired and wireless, no difference.
    The IP settings are manual and I have tried giving it the DNS settings of the router (normal settings) and I have also tried giving it Google's DNS servers (8.8.8.8 & 8.8.4.4). No difference.
    It seems to happen (sooner) during heavy traffic.
    Other Windows 7 machines in the network work fine (though they are Home version, not Pro).
    ONLY DNS fails, direct IP works OK.
    Reboot seems only solution at the moment.
    I am now lost as to what to try to resolve this issue, I do not really want to reload Windows 7 as it is a relatively new install... I have read about issues with wired connections on my router (BT Home Hub 2.0) so tried a wireless connection, still the
    same.
    Here is my ipconfig /all (it shows the BT Home Hub router DNS settings, but it also failed with Google's 8.8.8.8 and 8.8.4.4 entered here and also with the routers 192.168.1.254 (default).
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.
    C:\Users\G>ipconfig /all
    Windows IP Configuration
    Host Name . . . . . . . . . . . . : e1
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    Ethernet adapter Local Area Connection:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
    Physical Address. . . . . . . . . : 30-85-A9-AD-07-81
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::59f:484a:827f:42ba%11(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.87(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.1.254
    DHCPv6 IAID . . . . . . . . . . . : 238060969
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-39-2B-4D-30-85-A9-AD-07-81
    DNS Servers . . . . . . . . . . . : 217.32.171.21
    213.120.234.30
    NetBIOS over Tcpip. . . . . . . . : Enabled
    Ethernet adapter VirtualBox Host-Only Network:
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
    Physical Address. . . . . . . . . : 08-00-27-00-28-56
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::8d2d:7418:381b:8dc0%15(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . :
    DHCPv6 IAID . . . . . . . . . . . : 336068647
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-39-2B-4D-30-85-A9-AD-07-81
    DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
    fec0:0:0:ffff::2%1
    fec0:0:0:ffff::3%1
    NetBIOS over Tcpip. . . . . . . . : Enabled
    Tunnel adapter isatap.{486D4DCC-9CB7-417E-A796-596E0E6B1D54}:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft ISATAP Adapter
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Tunnel adapter Teredo Tunneling Pseudo-Interface:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    Tunnel adapter isatap.{67455999-75A5-436E-9EAC-12B093363132}:
    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    C:\Users\G>
    Any ideas where to look, or what other info to provide for any assistance?
    Many thanks in advance.

    Hi,
    This has just happened again, here is the content of the netstat results as requested...
    If I kill the VirtualBox virtual machines, it starts working again. It is as if there are no ports left, but I am not occupying that many? Surely Windows 7 can cope with this?
    I feel I am missing something important, but cannot put my finger on it...
    Further below, I have re-run the netstat command AFTER I have closed the VirtualBox machines and the system works OK.
    netstat results DURING ISSUE:
    Active Connections
      Proto  Local Address          Foreign Address        State           PID
      TCP    0.0.0.0:21             0.0.0.0:0              LISTENING       1444
     [FileZilla Server.exe]
      TCP    0.0.0.0:25             0.0.0.0:0              LISTENING       1692
     [MESMTPC.EXE]
      TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       4
     Can not obtain ownership information
      TCP    0.0.0.0:110            0.0.0.0:0              LISTENING       1660
     [MEPOPS.EXE]
      TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       752
      RpcSs
     [svchost.exe]
      TCP    0.0.0.0:143            0.0.0.0:0              LISTENING       1524
     [MEIMAPS.exe]
      TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4
     Can not obtain ownership information
      TCP    0.0.0.0:1221           0.0.0.0:0              LISTENING       4796
     [VirtualBox.exe]
      TCP    0.0.0.0:2199           0.0.0.0:0              LISTENING       4820
     [VirtualBox.exe]
      TCP    0.0.0.0:3306           0.0.0.0:0              LISTENING       1756
     [mysqld.exe]
      TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING       1104
      CryptSvc
     [svchost.exe]
      TCP    0.0.0.0:6901           0.0.0.0:0              LISTENING       4636
     [WinVNC.exe]
      TCP    0.0.0.0:6901           0.0.0.0:0              LISTENING       4636
     [WinVNC.exe]
      TCP    0.0.0.0:8300           0.0.0.0:0              LISTENING       3464
     [sc_serv.exe]
      TCP    0.0.0.0:8301           0.0.0.0:0              LISTENING       3464
     [sc_serv.exe]
      TCP    0.0.0.0:8360           0.0.0.0:0              LISTENING       3080
     [sc_serv.exe]
      TCP    0.0.0.0:8361           0.0.0.0:0              LISTENING       3080
     [sc_serv.exe]
      TCP    0.0.0.0:9022           0.0.0.0:0              LISTENING       4804
     [VirtualBox.exe]
      TCP    0.0.0.0:9023           0.0.0.0:0              LISTENING       4804
     [VirtualBox.exe]
      TCP    0.0.0.0:9080           0.0.0.0:0              LISTENING       4804
     [VirtualBox.exe]
      TCP    0.0.0.0:10001          0.0.0.0:0              LISTENING       4828
     [VirtualBox.exe]
      TCP    0.0.0.0:10002          0.0.0.0:0              LISTENING       4828
     [VirtualBox.exe]
      TCP    0.0.0.0:10003          0.0.0.0:0              LISTENING       4828
     [VirtualBox.exe]
      TCP    0.0.0.0:10011          0.0.0.0:0              LISTENING       4780
     [VirtualBox.exe]
      TCP    0.0.0.0:10012          0.0.0.0:0              LISTENING       4780
     [VirtualBox.exe]
      TCP    0.0.0.0:10013          0.0.0.0:0              LISTENING       4780
     [VirtualBox.exe]
      TCP    0.0.0.0:25566          0.0.0.0:0              LISTENING       3648
     [TerrariaServer.exe]
      TCP    0.0.0.0:30001          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30002          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30003          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30004          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30005          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30006          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30007          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30020          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30021          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30039          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30080          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30081          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30082          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30083          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30084          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30085          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30086          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30087          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30088          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30089          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30090          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30091          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30092          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30093          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30094          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30095          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30096          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30097          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30098          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30099          0.0.0.0:0              LISTENING       4788
     [VirtualBox.exe]
      TCP    0.0.0.0:30101          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30102          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30103          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30104          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30105          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30106          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30107          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30108          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30109          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30110          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30111          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30112          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30113          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30114          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30115          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30116          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30117          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30118          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30119          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30120          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30121          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30139          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30180          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30181          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30182          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30183          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30184          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30185          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30186          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30187          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30188          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30189          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30190          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30191          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30192          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30193          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30194          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30195          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30196          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30197          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30198          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30199          0.0.0.0:0              LISTENING       4812
     [VirtualBox.exe]
      TCP    0.0.0.0:30201          0.0.0.0:0              LISTENING       4796
     [VirtualBox.exe]
      TCP    0.0.0.0:30239          0.0.0.0:0              LISTENING       4796
     [VirtualBox.exe]
      TCP    0.0.0.0:33306          0.0.0.0:0              LISTENING       4796
     [VirtualBox.exe]
      TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING       440
     [wininit.exe]
      TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING       880
      eventlog
     [svchost.exe]
      TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING       1000
      Schedule
     [svchost.exe]
      TCP    0.0.0.0:49156          0.0.0.0:0              LISTENING       508
     [lsass.exe]
      TCP    0.0.0.0:49157          0.0.0.0:0              LISTENING       500
     [services.exe]
      TCP    0.0.0.0:49158          0.0.0.0:0              LISTENING       3048
      PolicyAgent
     [svchost.exe]
      TCP    127.0.0.1:8361         127.0.0.1:49364        ESTABLISHED     3080
     [sc_serv.exe]
      TCP    127.0.0.1:14147        0.0.0.0:0              LISTENING       1444
     [FileZilla Server.exe]
      TCP    127.0.0.1:14147        127.0.0.1:49162        ESTABLISHED     1444
     [FileZilla Server.exe]
      TCP    127.0.0.1:49162        127.0.0.1:14147        ESTABLISHED     3156
     [FileZilla Server Interface.exe]
      TCP    127.0.0.1:49212        127.0.0.1:49213        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49213        127.0.0.1:49212        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49214        127.0.0.1:49215        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49215        127.0.0.1:49214        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49216        127.0.0.1:49217        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49217        127.0.0.1:49216        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49218        127.0.0.1:49219        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49219        127.0.0.1:49218        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49220        127.0.0.1:49221        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49221        127.0.0.1:49220        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49222        127.0.0.1:49223        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49223        127.0.0.1:49222        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49224        127.0.0.1:49225        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49225        127.0.0.1:49224        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49226        127.0.0.1:49227        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49227        127.0.0.1:49226        ESTABLISHED     4288
     [java.exe]
      TCP    127.0.0.1:49364        127.0.0.1:8361         ESTABLISHED     3100
     [Instore_Radioboss.exe]
      TCP    192.168.1.87:139       0.0.0.0:0              LISTENING       4
     Can not obtain ownership information
      TCP    192.168.1.87:3389      217.156.134.12:22971   ESTABLISHED     1104
      CryptSvc
     [svchost.exe]
      TCP    192.168.1.87:8360      81.148.248.221:1026    ESTABLISHED     3080
     [sc_serv.exe]
      TCP    192.168.1.87:25565     0.0.0.0:0              LISTENING       4288
     [java.exe]
      TCP    192.168.1.87:50644     37.139.0.151:8233      ESTABLISHED     4796
     [VirtualBox.exe]
      TCP    192.168.1.87:51019     81.27.96.46:21         TIME_WAIT       0
      TCP    192.168.1.87:53126     192.168.1.86:445       ESTABLISHED     4
     Can not obtain ownership information
      TCP    192.168.1.87:60462     192.168.1.86:445       CLOSE_WAIT      4
     Can not obtain ownership information
      TCP    192.168.1.87:65029     37.139.0.151:8231      ESTABLISHED     4796
     [VirtualBox.exe]
      TCP    192.168.56.1:139       0.0.0.0:0              LISTENING       4
     Can not obtain ownership information
      TCP    [::]:21                [::]:0                 LISTENING      
    1444
     [FileZilla Server.exe]
      TCP    [::]:25                [::]:0                 LISTENING      
    1692
     [MESMTPC.EXE]
      TCP    [::]:80                [::]:0                 LISTENING      
    4
     Can not obtain ownership information
      TCP    [::]:135               [::]:0                 LISTENING      
    752
      RpcSs
     [svchost.exe]
      TCP    [::]:445               [::]:0                 LISTENING      
    4
     Can not obtain ownership information
      TCP    [::]:3306              [::]:0                 LISTENING      
    1756
     [mysqld.exe]
      TCP    [::]:3389              [::]:0                 LISTENING      
    1104
      CryptSvc
     [svchost.exe]
      TCP    [::]:30239             [::]:0                 LISTENING      
    4796
     [VirtualBox.exe]
      TCP    [::]:49152             [::]:0                 LISTENING      
    440
     [wininit.exe]
      TCP    [::]:49153             [::]:0                 LISTENING      
    880
      eventlog
     [svchost.exe]
      TCP    [::]:49154             [::]:0                 LISTENING      
    1000
      Schedule
     [svchost.exe]
      TCP    [::]:49156             [::]:0                 LISTENING      
    508
     [lsass.exe]
      TCP    [::]:49157             [::]:0                 LISTENING      
    500
     [services.exe]
      TCP    [::]:49158             [::]:0                 LISTENING      
    3048
      PolicyAgent
     [svchost.exe]
      TCP    [::1]:14147            [::]:0                 LISTENING       1444
     [FileZilla Server.exe]
      UDP    0.0.0.0:123            *:*                                   
    964
      W32Time
     [svchost.exe]
      UDP    0.0.0.0:500            *:*                                   
    1000
      IKEEXT
     [svchost.exe]
      UDP    0.0.0.0:3702           *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    0.0.0.0:3702           *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    0.0.0.0:4500           *:*                                   
    1000
      IKEEXT
     [svchost.exe]
      UDP    0.0.0.0:5355           *:*                                   
    1104
      Dnscache
     [svchost.exe]
      UDP    0.0.0.0:53274          *:*                                   
    4780
     [VirtualBox.exe]
      UDP    0.0.0.0:53727          *:*                                   
    4788
     [VirtualBox.exe]
      UDP    0.0.0.0:54111          *:*                                   
    4828
     [VirtualBox.exe]
      UDP    0.0.0.0:54112          *:*                                   
    4828
     [VirtualBox.exe]
      UDP    0.0.0.0:54113          *:*                                   
    4780
     [VirtualBox.exe]
      UDP    0.0.0.0:55421          *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    0.0.0.0:58596          *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    0.0.0.0:59838          *:*                                   
    4812
     [VirtualBox.exe]
      UDP    0.0.0.0:62498          *:*                                   
    4796
     [VirtualBox.exe]
      UDP    127.0.0.1:1900         *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    127.0.0.1:55045        *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    192.168.1.87:137       *:*                                   
    4
     Can not obtain ownership information
      UDP    192.168.1.87:138       *:*                                   
    4
     Can not obtain ownership information
      UDP    192.168.1.87:1900      *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    192.168.1.87:55043     *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    192.168.56.1:137       *:*                                   
    4
     Can not obtain ownership information
      UDP    192.168.56.1:138       *:*                                   
    4
     Can not obtain ownership information
      UDP    192.168.56.1:1900      *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    192.168.56.1:55044     *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    [::]:123               *:*                                   
    964
      W32Time
     [svchost.exe]
      UDP    [::]:500               *:*                                   
    1000
      IKEEXT
     [svchost.exe]
      UDP    [::]:3702              *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    [::]:3702              *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    [::]:4500              *:*                                   
    1000
      IKEEXT
     [svchost.exe]
      UDP    [::]:5355              *:*                                   
    1104
      Dnscache
     [svchost.exe]
      UDP    [::]:55422             *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    [::]:58597             *:*                                   
    964
      EventSystem
     [svchost.exe]
      UDP    [::1]:1900             *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    [::1]:55042            *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    [fe80::59f:484a:827f:42ba%11]:1900  *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    [fe80::59f:484a:827f:42ba%11]:55040  *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    [fe80::11a6:2283:bc40:c0cb%16]:1900  *:*                                   
    4172
      SSDPSRV
     [svchost.exe]
      UDP    [fe80::11a6:2283:bc40:c0cb%16]:55041  *:*                                   
    4172
      SSDPSRV
     [svchost.exe]

  • [SOLVED] Greetings... and DNS issues... (why is it so slow?)

    Hey everybody!
    My name is Stephen. I'm new to Arch (hence I'm posting in the newb forum). A bit of background: I'm a CS major in the good 'ole US of A. I used Debian/Ubuntu for 2 years before now. I actually installed Arch just yesterday, so today is my second day of usage. Why do I want to switch from Ubuntu? Several reasons, but they can all be summed up thusly: I want to tinker with and understand how my machine works. I don't want to interface with a blackbox that just "works." Arch seems to be geared towards what I want.
    And I've been learning alot, haha. Which I why I am now here to ask for help.
    I originally installed Arch at school. Everything was great. Then I took my laptop home and I found out something was wrong. Pacman took an extra 5-15 secs before each download started, but once the download started, I got normal speeds. I observed a similar behavior in my web browsers I tried (Firefox/Surf). No matter what I do, this behavior persists. I suspect this is a DNS issue, and thus I have tried the follow methods of correction so far.
    1) Reinstalling to a default configuration.
    2) Disabling IPV6.
    3) Screwing around with etc/hosts, etc/resolv.conf, and etc/dhcpcd.conf (though I probably did something wrong. Also, I'm not sure how to force Arch to accept my changes after modifying these files.)
    I also read somewhere that using HTTP mirrors works better for pacman, but I already was using an HTTP mirror anyway, so I knew that couldn't be the problem.
    I have not tried DNS caching yet. However, given that every other machine in the house runs fine, I suspect it is my configuration that is wrong. Does anybody know how I can pinpoint this as DNS for sure? And if so, how I can fix it? Thanks for all your time/help!
    Here are some config files/snippets of interest. Most of this should be straight from a basic Arch install.
    etc/resolv.conf
    # Generated by dhcpcd from eth0
    # /etc/resolv.conf.head can replace this line
    domain domain.actdsltmp
    nameserver 192.168.0.1
    nameserver 216.165.129.157
    # /etc/resolv.conf.tail can replace this line
    Note that 192.168.0.1 is the address of my router on my LAN. I believe the second address is a DNS provided by my ISP.
    etc/hosts
    #<ip-address> <hostname.domain.org> <hostname>
    127.0.0.1 localhost.localdomain localhost moebius
    ::1 localhost.localdomain localhost
    etc/rc.conf snippet
    HOSTNAME="moebius"
    eth0="dhcp"
    INTERFACES=(eth0)
    # 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)
    Last edited by sskeirik (2011-03-14 23:21:19)

    Output of 'dig google.com a'
    ; <<>> DiG 9.7.3 <<>> google.com a
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52741
    ;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
    ;; WARNING: recursion requested but not available
    ;; QUESTION SECTION:
    ;google.com. IN A
    ;; ANSWER SECTION:
    google.com. 10000 IN A 74.125.65.104
    ;; Query time: 17 msec
    ;; SERVER: 192.168.0.1#53(192.168.0.1)
    ;; WHEN: Mon Mar 14 14:09:45 2011
    ;; MSG SIZE rcvd: 44
    Output of 'dig @8.8.8.8 google.com a'
    ; <<>> DiG 9.7.3 <<>> @8.8.8.8 google.com a
    ; (1 server found)
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43373
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 0
    ;; QUESTION SECTION:
    ;google.com. IN A
    ;; ANSWER SECTION:
    google.com. 229 IN A 74.125.45.105
    google.com. 229 IN A 74.125.45.99
    google.com. 229 IN A 74.125.45.103
    google.com. 229 IN A 74.125.45.147
    google.com. 229 IN A 74.125.45.106
    google.com. 229 IN A 74.125.45.104
    ;; Query time: 74 msec
    ;; SERVER: 8.8.8.8#53(8.8.8.8)
    ;; WHEN: Mon Mar 14 14:10:37 2011
    ;; MSG SIZE rcvd: 124

  • If your web pages are loading slowly, this resolved my issue.Hope it helps!

    Mac OS: Long delay before webpages load, then load suddenly at normal speed
    Symptoms
    When trying to access a website via its DNS name, such as www.apple.com, there may be a delay that ranges from several seconds up to several minutes before the page loads at normal speed, depending on the operating system version and configuration. However, if you access the website's numerical IP address, such as http://17.149.160.49 , the page loads immediately.
    Two causes of the issue are described below, DNS configuration and changing networks. Issues related to changing networks usually only affect portable Macs.
    Products Affected
    Safari, Mac OS X 10.4, Mac OS X 10.3, Mac OS X 10.2, Mac OS X 10.1, Mac OS X 10.0, Mac OS X 10.5, Mac OS X 10.6
    Resolution
    DNS configuration
    This may indicate a non-responsive DNS server or an invalid DNS configuration. A DNS server converts a name to a numerical IP address, "www.apple.com" to "17.149.160.49", for example. You can connect to an IP address without any delay, because the need for DNS resolution is avoided. Here are four scenarios in which the symptom may occur:
    You have specified two or more DNS servers in the Network preference pane (possibly at the direction of a network administrator or your ISP), but the first server on the list has become non-responsive, or was entered incorrectly. The delay occurs while Mac OS X waits for the first server to respond, then it goes to the next server in your list. Make sure the addresses are entered correctly. Changing the order of DNS addresses may improve performance. If your network administrator prefers that the primary server be used, you may wish to change back to the original order after the issue is resolved with the primary server.
    Your network may be configured to provide automatic discovery of DNS service, without needing to manually type the DNS server addresses at your computer. If you have manually typed a DNS address that is incorrect or out of date, your computer may wait for the incorrect address to respond (a "timeout") before succeeding at automatic discovery.
    You have not specified a DNS server, and automatic discovery of the service is not provided on your network. In this scenario, you can only connect via an IP address. Web pages do not load at all via a DNS name, such as is described in this article.
    How to resolve
    Check with your network administrator or Internet Service Provider (ISP) to make sure your DNS information is correct. If your ISP only provides you with one DNS address, consider requesting a second one for use in the event that the first becomes unavailable.
    Once you have the address(es), you can use these steps to change your DNS information. Note: After using these steps, some Internet applications may need to be quit and reopened to return to normal behavior.
    Mac OS X v10.5 or 10.6:
    From the Apple menu, choose System Preferences.
    From the View menu, choose Network.
    Click the interface you use to connect to the Internet, such as AirPort or Built-in Ethernet.
    If you use Built-in Ethernet: Type your DNS address(es) in the DNS Server field. If you have more than one, separate them with a comma.
    If you use AirPort, click Advanced, then click the DNS tab. For each server, click the "+" button under DNS Servers and enter the address provided by your ISP or network admin. Click OK when done.
    Click Apply.
    Mac OS X v10.4 or earlier:
    From the Apple menu, choose System Preferences.
    From the View menu, choose Network.
    From the Show menu, choose the interface you use to connect to the Internet.
    Click the TCP/IP tab.
    Type your DNS address in the Domain Name Servers field. If you have more than one, press Return at the end of each to put the next address on a new line.
    Click Apply Now.
    Changing networks
    You may experience a delay with the first connection after changing networks on a portable Mac. For example, you might use an MacBook at home with AirPort, then take it to work or school and use an Ethernet connection. By default, Mac OS X uses one set of Internet preferences (known as a "location") named Automatic that will search your computer's modem, Ethernet, and AirPort interfaces until it finds the one that is connected to the Internet. You may experience a delay while your computer determines which network it is on. This can be easily differentiated from a DNS issue by creating a location that only contains one network interface. For more information, see Using network locations in Mac OS X.

    Yeah.  I'm seeing the same behavior.  Safari hangs when it loads pages.  Firefox loads them quickly.  That's not a DNS issue.
    Some pages hang for MINUTES in Safari.  If you just touch the resize triangle at the bottom right of the screen, then Safari loads the page just fine.  This is a redraw problem, not a DNS issue.
    This happens on both my wife's iMac Core i5 and my Mac Mini Core 2 Duo - both running Mac OS X 10.6.8
    David

  • How do you resolve the issue with an error message on the Mac mini server stating Unable to get users

    How do you resolve an issue when creating groups on a Mac Mini Server when this error message appears.
    "Unable to get Users & Groups State, The Open Directory master was created, but a problem was encountered trying to refresh the state of the server. Check log files for more info."

    Most likely, the Server was not configured correctly - DNS is a common issue, If DNS is not configured properly, OD will not be happy. You can run
    sudo changeip -checkhostname
    in Terminal to see of DNS is up and running.
    Here's a great tutorial (not mine) for setting up OS X Servers. The page says it's for a typical school environment, but it can be applied in many other environments.
    http://www.wazmac.com/servers_network/fileservers/osxserver_setup/index.htm
    hth
    Jeff

  • Constant Resolving Host Issues

    I have had a good service until recently but now Constant Resolving Host Issues. Pages slow to load making it difficult to use. 
    HH3 Software version 4.7.5.1.83.8.94.1.37 (Type A) 
    I have factory reset hub and tried opendns and Google DNS. 
    Can anyone help?
    Keith

    Hi cookiesandjava
    Sounds stange   I'll be happy to have a look over your connection stats and see if there is anything out of place.
    Could you drop me in an email please? Use the 'contact us' form in my forum profile under the 'about me' section. You can find it by clicking on my username.
    Thx
    Craig
    BTCare Community Mod
    If we have asked you to email us with your details, please make sure you are logged in to the forum, otherwise you will not be able to see our ‘Contact Us’ link within our profiles.
    We are sorry but we are unable to deal with service/account queries via the private message(PM) function so please don't PM your account info, we need to deal with this via our email account :-)”
    td-p/30">Ratings star on the left-hand side of the post.
    If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

  • DNS issues with replaced domain controllers

    I have slight issue I hope some one can help with.
    We recently replaced some domain controllers in our 2 core sites the process we followed is as below:-
    moved FSMO roles to different already working servers
    demoted the old domain controllers and decommissioned.
    built virtual machine replacements with the same names.
    depromo'd the servers
    ran all the tests and it reported everything was fine.
    moved the fsmo roles to the new servers.
    repeated this for the remaining servers.
    this was our 2003 domain to free up physical space but our new 2013 domain what will exist separately until all our applications our tested.
    however the problem we now have is that non domain controllers have issues registering against the new servers despite being able to do look-ups against them all (replication testing looks fine). one of our regional DC's seems to have taken over as the primary
    replica. as changes made else where disappeared but changes made there got replicated out perfectly.
    I have managed to resolve this particular issue by added the domain controllers back into several locations in DNS manually (maining forward lookup zones>my domain>_tcp )but we still experience the odd issue with servers not registering in DNS properly
    (although it's a lot better since the I did the above)
    so basically does any one have a idea on what could have caused this issue and how I can resolve?

    should the demotion not automatically remove it from sites and services automatically (it could well be this if not) the question then becomes how do we resolve the issues we have now.
    Hello,
    NO, as you can demote a DC and it still may run site-aware services like DFS and for this reason a DC is NOT automatically removed from AD sites and services during demotionprocess.
    Best regards
    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://blogs.msmvps.com/MWeber
    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
    Twitter:  

  • Internet connections have trouble "grabbing on": is this a DNS issue?

    Setup: late 2009 iMac, Mountain Lion 10.8.3, using Wifi through an Airport Extreme. A Windows laptop, two iPhones, and an iPad all use the Wifi with no problems at all.
    On the iMac: I suspect it's a DNS issue, although I don't know how to confirm that for all the issues. Often, in Safari, the blue bar will progress a bit and get nowhere - maybe a few minutes later the site will appear. Repeatedly hitting refresh seems to be a faster way of reaching the site. Chrome often tells me "DNS lookup failed": once again, refreshing several times will usually get me to the site.
    The issue comes and goes, and has been doing so for the past few weeks I think. It's not as if I've lost the internet connection - I always get the connection, but sometimes it takes a while. It doesn't seem to be time-based: one minute fine, next minute a problem, next minute fine.
    I live in Taiwan: this issue MAY be less serious with Taiwanese websites (just now I opened a .tw site instantly, while bbc.co.uk is hanging), but it seems to happen with everything.
    But the problems aren't just in browsers: in iTunes, when refreshing podcasts, the behavior is similar: the little rotating arrows can keep going forever, as if no connection is being made at that particular moment. Ditto when downloading a podcast: it sits at nothing downloaded, often until I hit pause and resume a few times, at which point it downloads with good speed. Similar when refreshing NetNewsWire, and Twitter, and Mail. Do DNS issues also happen with iTunes and RSS? (Sorry if that's a dumb question - I'm way out of my depth here, and hadn't even heard of DNS until a couple of days ago.)
    Results from Speedtest.net are consistently good (download in the range of 40 Mbps, upload in the range of 10 Mbps, ping 7ms) - once I can actually get to the website, which as with all other websites, can sometimes involve repeated hangs and hits of refresh/reload. Note that there has never been a hang when actually trying to test with Speedtest (just when getting to the site): that points to DNS issues as well, right?
    The Wifi bar indicator at the top of the screen is always at full strength.
    I've tried things mentioned in different threads here, and also at this page...
    http://apple.stackexchange.com/questions/26616/dns-not-resolving-on-mac-os
    ... but so far nothing seems to help.
    Can anyone advise on what the problem actually is, and how I can go about fixing it? Thanks in advance!

    Hmm. Maybe this has been resolved now - thanks!
    First step: I checked the Network / Wifi Advanced / DNS, and found two DNS servers listed: I just reversed the order of the two, and after clicking "Apply", nothing changed. Still the same issue.
    Second step: looked on the iPad, Settings / Wi-Fi, and found the DNS listed there: and then I added that same number (10.0.1.1 - the iPhone has the same DNS) to the DNS server list on my iMac, at the top of the list. For the moment, everything is working very well, including far faster iTunes Podcast Refresh than I've seen in ages.
    I'll check back in later to confirm the problem has indeed gone away, and I'm not just having a good ten minutes.
    Where would those DNS Servers have come from? Does my ISP somehow automatically install them, or did I type them in back in the mists of time?

  • DNS issues Infinity 2

    So, over the last few days I have seen a steady increase in "page not found" errors.  The websites involved seem to be fairly random.
    in simple terms, some URLs are resolved to a page and others are not.
    ive rebooted the Homehub and modem, and this provides some temporary respite before the problem recurs.
    i read elsewhere on the forums that some people are affected by similar probleparticularly rely on the EA online games, but wanted to flag that the issue is more prevalent.
    anyone else getting issues or just me?
    cheers

    Been having DNS issues as well the last few days. Very frustrating when I need to submit coursework online for a deadline, yet can't access my Uni's servers. Strange thing is, it's intermittent and only seems to affect one device on my WiFi at a time. First it was my laptop, while my phone, 2nd laptop, Xbox and flatmate's laptop were working perfectly. Once I got my laptop working, my flatmate's DNS failed as he tried to submit the same coursework assignment. Today everything is working apart from my phone. There doesn't seem to be any obvious link as to what's causing it...

  • DNS Issues with Hyper-V 2012 R2 VDI Pooled Desktop Deployment

    Good afternoon all!
    We are running a POC VDI deployment on a Nutanix system, and I am having a DNS issue. I would appreciate some help trying to figure this out. Two situations that are causing issues that I can see:
    1. VMs go into a saved state if not being used: This in itself is not an issue, and I see it as a way to save resources not being used; however, if a VM is saved for a few days, the DHCP address often gets reassigned. Now if users are connecting, and that
    saved VM with the stale address is called to wake up, the VM is not found.
    2. Recreating the pool after updating the golden image: This is the bigger issue. After a couple days of running smoothly, I was asked by my pilot users to add Firefox. I installed it and recreated all the VMs in the pool. When this happened, they all got
    new IPs, but the old DNS records were not updated. This made the broker unable to find a single VM in the pool. I could not ping a single one.
    Has anybody else run into these DNS issues with a VDI deployment? If so, what did you do to resolve it? If not, have any ideas on what is going on here?
    Thank you in advance!
    Eric

    Hi Eric,
    As per my research, I can say that the default behavior. When we will recreate the VM it will change the IP address dynamically. But from your description it seems the DNS record is not getting update and due to that you can’t find your VM with hostname or
    IP. But for this you can set one option under DNS server with which DNS record can update the new IP address. The option you need to set is “Dynamic updates>Nonsecure and Secure” under general properties in sites. You can check below snap.
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Is it a DNS issue?

    Hi guys!
    Im experiencing some problems with opening some pages (facebook or youtube) with any broser on my iMac and the pages that i had the chance to open make me wait too long. I was living in Turkey and never had this issue. Today i moved to Bulgaria and the problen came up here. Is a DNS issue or smthng else? What i have to do?

    Can you view other websites besides those two?
    Do other devices you own have the same issues (that are connected on the same network)?
    You may have to contact your Internet Service Provider to resolve this.

Maybe you are looking for

  • What is the best iPhone 3G protective case?

    I have my iPhone since July 11 and since then it has been "caseless", I was dead set on the Agent 18 Eco, but after reading several reviews and talking to someone that currently uses that particular case, it seems it actually scratches your phone, wh

  • How to create a non-destructive luminosity/b&w mask for (de)saturation?

    Someone asked me this question: CG renders (created in Modo, Max, Blender, Maya, Vray, Octane, etc) can be made to look more realistic by desaturating the colours in the highlights. It was also requested that this move would be done in 32bpc as well

  • @XREF vs flat files

    Hello everybody: I would like to know which method is faster or better to copy data from one database to another (remote) database?. When is better one method over the other one?. Is there another way to do this in Planning different to these? Thank

  • Stop changing things that made itunes revolutionary

    why on God's earth do I now have to go through **** and high water just to view the size of my Itunes library???? it used to be conveniently placed at the bottom and as much as your products cost, convenience is a must. STOP MAKING THINGS THAT WERE E

  • 3.0EA1: Code editor closed automatically on saving

    Hi, To reproduce: - open a stored PL/SQL - save through File - Save As - close the opened file ( why is this opened anyway? ) - save again through File - Save As (same name, overwrite) - now the code editor is closed automatically! D'Oh! Can this be