DNS Server Question

I have an Actiontec router that is my primary router, and where my broadband connection is. Behind this I have a second Actiontec that is connected via a MoCA extension in my bedroom and a Netgear router that is connected to the primary via wired ethernet. The Netgear is handling wireless only.
At present the two routers behind the primary router have no DNS server configured. I would like to make the primary router the defacto DNS server. Is it just as easy as pointing the two routers behind the primary to it, or is there more to this. Second the primary router's Network (Home/Office) section is not pointing to any DNS server. Do I just point this section to the IP of the primary also?
Last but not least I would like to resolve the names I gave my routers to their IPs. The problem I see is that the primary router cannot have a DNS entry for itself. Is there anyway to get around this?
Thanks,
Steve
Solved!
Go to Solution.

If the second Actiontec is functioning as a MOCA bridge, it is NOT functioning as a router and it's DHCP server must be disabled. Therefore, it is NOT supplying DNS addresses.
Whether the Netgear is functioning as a router depends on whether it is connected to the primary LAN-to-WAN or LAN-to-LAN.
If configured LAN-to-LAN, then the Netgear is functioning only as a WAP and not as a router and it's DHCP server should also be DISABLED.
Your primary Actiontec should be the only one of the three with DHCP server enabled. It will then be the only source of DNS addresses.

Similar Messages

WRT54GS question.....DNS Server address?????

Someone please help,
          I had a problem with my wireless not working on my 2nd PC. I originally thought that it was because of that PC being old and possibly having some trojan horses or other virus's that i could not get off. I have since threw out that PC and bought a new notebook yesterday at BestBuy. I told the man from geeksquad that i was having a problem with my wireless at home. He said that if the notebook could not connect to the wireless to push the red reset button on the back of the router and start over with redownloading it on my PC.
        I have done that, but am stuck on step 8 of the wizard. I have the IP Address, Subnet Mask, and Gateway. It is now asking for DNS 1(DNS Server address). What is DNS & where would i find this? I've had this router for about 2 years, will there be any other important information that i may need when trying to connect my notebook through this router?
           Thanks for your advise.

I did find the DNS address's, but once i tried to finish the setup of the router it said, Unable to configure router, reset the router to factory default settings. Well in short, after some searching, i wired the PC directly to the modem. It would not connect to the internet. Did I do something or delete something I shouldn't have? Looks like it. UGH!! My notebook is working just fine connected directly to the modem, but I'm getting nothing with the PC connected to the modem or the router.
ANYONE HELP???????

EA6400 Question. DHCP always sets router IP as first DNS server

Subj, is it ok? DNS server 10.2.2.1 removal from list does not changes situation.
DHCP client settings:
Current firmware 1.1.40.160989

It makes no difference. Support has no complaints on this issue. But it is a pain in da a55 in conjunction with this

Question about changing the IP of a Windows DC, that is also acting as a DNS server?

I have two subnets (network A, network B) located within the same single Windows domain site.
Each site has two DCs, which each are running AD-integrated DNS.
I need to move one server from network B, into network A. If I change the IP address, subnet mask, and gateway and DNS entries on this server, shut it down, and then bring it back up on network A, should the server automatically register itself
in DNS under its new IP address, and behaving like a normal domain controller in the new subnet? Or will I need to perform an ipconfig /registerdns on the domain controller once it comes back up in network A, in order for it to be seen as a domain controller/DNS
server under its new IP address?

If you change the IP of the DC, the command isn't going to be a IPCconfig/RegisterDNS.
DC's register their essential records when the NETLOGON service starts, so restart that.
**Are your clients using DHCP? Are you sure you've eliminated the dependancies on that IP address for all your clients?
- Chris Ream -
**Remember, if you find a post that is helpful, or is the answer, please mark it appropriately.**

Your computer appears to be correctly configured, but the device or resource (DNS server) is not responding [and I'm at my wit's end!]

I originally posted this question to the community section and was advised to post it here. Please bear with me as this will be a long post. I'm including the scenarios involving this reoccurring issue, the trouble shooting steps I've already
taken and the results of several diagnostic tools and logs.
I have a Sony VAIOS VPCEBB33FM lap top since 2011. I have had this issue on an off for a long time. I'm at my wit's end. Any new insights or suggestions would be greatly appreciated.
Scenario Details
1) Some times it's on and off through out the day, sometimes it won't work all day, and once in a while it will work fine for the entire day.
2) I've had this issue across several wireless services, Clear Network accessed with WiMax, Library Wi-fi, Comcast cable internet using wireless router and Wi-fi, and Comcast Xfinity Wi-Fi, to name a few examples.
3) Other devices in the household or library will work with no problems such as my smart phone or my roommates' laptops or desktop computers.
4) Once in a while, the built-in wireless adapter is not found and I have to reinstall the driver. Also the diagnostic tool has had to reset my adapter on an increasing basis.
5) I had my hard drive replaced in December 2014 and my system restored from the System Restore disks that came with it when I bought the laptop. Even though I've been online on an infrequent basis it worked just fine for a while. Now that
I've been online a bit more I'm having the same issues again.
Below are my attempts at trouble shooting so far but I still have not been able to consistently resolve my DNS issues
1) Restarting my adapter
2) Turning off my laptop and removing the power supply for 5-10 minutes before turning it back on.
3) Using the IP Config in Command Prompt
     ipconfig /flushdns
   ipconfig /registerdns
   ipconfig /release
     ipconfig /renew
4) Using the NetSh reset in Command Prompt and restarting my laptop
     netsh int ip reset c:\resetlog.txt
     netsh winsock reset
     ipconfig /flushdns
     [restart laptop]
5) Configuring the TCP/IP in several settings
    Select Internet Protocol Version 4 (TCP/IPv4), and then click Properties.
    I have used the following settings:
       a) Obtain an DNS server address automatically
       b) OpenDNS
           208 67 222 222
           208 67 220 220
       c) Google DNS
           8 8 8 8
           8 8 4 4
6) Updating the driver for my Intel Centrino(R) Advanced-N 6250 AGN and Intel Centrino(R) WIMAX 6250 from the Intel website previous having my laptop wiped clean in 2014. It still did not resolve the issue. My laptop
manufacturer as not come up with an driver update for my adapter since 2010. I haven't tried to update the adapter driver from Intel's website since having my laptop repaired due to the fact that Intel strongly recommending using the manufacturer's updates
instead and frankly it didn't make much of a difference when I did it the first time.
7) The last one I've tried as of today is going into Services and changing the start up type to automatic for the following:
       Computer Browser [changed from manual to automatic]
       DHCP Client [already set to automatic]
       DNS Client [already set to automatic]
       Network Connections [already set to automatic]
       Network Location Awareness [changed from manual to automatic]
       Remote Procedure Call (RPC) [already set to automatic]
       Server [already set to automatic]
       TCP/IP Netbios helper [already set to automatic]
       Workstation [already set to automatic]
...and I'm still having DNS issues.
My only guessing are that my laptop came with a lemon adapter that needs to be replaced, some advanced setting(s) that I'm not aware off, or my firewall/anti-virus is interfering. I've used Symmantic Anti-virus and Firewall in the past and currently
Avast Anti-Virus with Microsoft Network Firewall. I've had DNS issues with both anti-virus/firewall set ups.
Below are the results from the diagnostics and tests that I've ran.
Windows Network Diagnostics
Your computer appears to be correctly configured, but the device or resource (DNS server) is not responding Detected Detected
Contact your network administrator or Internet service provider (ISP) Completed
Windows can't communicate with the device or resource (DNS server). The computer or service you are trying to reach might be...
Details about network adapter diagnosis:
Network adapter Wireless Network Connection driver information:
   Description . . . . . . . . . . : Intel(R) Centrino(R) Advanced-N 6250 AGN
   Manufacturer . . . . . . . . . : Intel Corporation
   Provider . . . . . . . . . . . : Intel
   Version   . . . . . . . . . . . : 13.2.1.5
   Inf File Name . . . . . . . . . : C:\Windows\INF\oem17.inf
   Inf File Date . . . . . . . . . : Monday, June 14, 2010 9:05:44 AM
   Section Name . . . . . . . . . : Install_MPCIEX_GEN_6250_AGN_2x2_HMC_WIN7_64_MOW
   Hardware ID . . . . . . . . . . : pci\ven_8086&dev_0087&subsys_13018086
   Instance Status Flags . . . . . : 0x180200a
   Device Manager Status Code . . : 0
   IfType . . . . . . . . . . . . : 71
   Physical Media Type . . . . . . : 9
Informational Diagnostics Information (Wireless Connectivity)
Details about wireless connectivity diagnosis:
Information for connection being diagnosed
Interface GUID: 70a0781d-6329-45e4-8d7c-34aeca294c39
Interface name: Intel(R) Centrino(R) Advanced-N 6250 AGN
Interface type: Native WiFi
Connection incident diagnosed
Auto Configuration ID: 1
Connection ID: 1
Connection status summary
Connection started at: 2015-03-07 19:57:14-186
Profile match: Success
Pre-Association: Success
Association: Success
Security and Authentication: Success
List of visible access point(s): 22 item(s) total, 22 item(s) displayed
        BSSID       BSS Type PHY   Signal(dB)   Chnl/freq    SSID
60-02-92-C6-D3-E8   Infra   <unknown>   -62       11   HOME-C7D4-2.4
60-02-92-A1-75-E0   Infra   <unknown>   -58       6   HOME-B917-2.4
00-1D-D5-D5-34-F0   Infra   <unknown>   -73       6   HOME-34F2
60-02-92-A1-75-E1   Infra   <unknown>   -58       6   (Unnamed Network)
06-1D-D5-D5-34-F0   Infra   <unknown>   -78       6   xfinitywifi
C4-27-95-C9-C4-2D   Infra   <unknown>   -57       1   HOME-C42D
02-1D-D5-D5-34-F0   Infra   <unknown>   -74       6   (Unnamed Network)
00-0D-97-07-E0-79   Infra   g   -75       6   (Unnamed Network)
00-1D-CF-2A-44-C0   Infra   <unknown>   -86       6   HOME-44C2
02-1D-CF-2A-44-C0   Infra   <unknown>   -86       6   (Unnamed Network)
F8-E4-FB-3C-87-A2   Infra   <unknown>   -89       6   YVNM7
06-1D-CF-2A-44-C0   Infra   <unknown>   -87       6   xfinitywifi
0C-F8-93-7A-13-50   Infra   b   -87       6   PKennedy
06-F8-93-7A-13-50   Infra   b   -89       6   xfinitywifi
02-F8-93-7A-13-50   Infra   b   -87       6   (Unnamed Network)
E0-88-5D-C8-A9-DC   Infra   <unknown>   -80       1   HOME-A9DC
E2-88-5D-C8-A9-DD   Infra   <unknown>   -79       1   (Unnamed Network)
16-CF-E2-43-0B-30   Infra   <unknown>   -88       1   xfinitywifi
60-02-92-F0-A8-C0   Infra   <unknown>   -90       11   HOME-96A6-2.4
60-02-92-C6-D3-E9   Infra   <unknown>   -63       11   (Unnamed Network)
02-1D-D4-EB-87-00   Infra   <unknown>   -88       11   (Unnamed Network)
06-1D-D4-EB-87-00   Infra   <unknown>   -88       11   xfinitywifi
Connection History
Information for Auto Configuration ID 1
List of visible networks: 13 item(s) total, 13 item(s) displayed
BSS Type PHY   Security   Signal(RSSI)   Compatible   SSID
Infra   <unknown>   Yes       63   Yes       HOME-C7D4-2.4
Infra   <unknown>   Yes       70   Yes       HOME-B917-2.4
Infra   <unknown>   Yes       43   Yes       HOME-34F2
Infra   <unknown>   Yes       70   Yes       (Unnamed Network)
Infra   <unknown>   No       40   Yes       xfinitywifi
Infra   <unknown>   Yes       71   Yes       HOME-C42D
Infra   g   No       43   Yes       (Unnamed Network)
Infra   <unknown>   Yes       28   Yes       HOME-44C2
Infra   <unknown>   Yes       20   Yes       YVNM7
Infra   b   Yes       21   Yes       PKennedy
Infra   <unknown>   Yes       33   Yes       HOME-A9DC
Infra   <unknown>   Yes       35   Yes       (Unnamed Network)
Infra   <unknown>   Yes       16   Yes       HOME-96A6-2.4
List of preferred networks: 3 item(s)
   Profile: xfinitywifi
    SSID: xfinitywifi
    SSID length: 11
    Connection mode: Infra
    Security: No
    Set by group policy: No
    Connect even if network is not broadcasting: No
    Connectable: Yes
   Profile: HTC Portable Hotspot 9F50
    SSID: HTC Portable Hotspot 9F50
    SSID length: 25
    Connection mode: Infra
    Security: Yes
    Set by group policy: No
    Connect even if network is not broadcasting: No
    Connectable: No
     Reason: 0x00028002
   Profile: belkin.332
    SSID: belkin.332
    SSID length: 10
    Connection mode: Infra
    Security: Yes
    Set by group policy: No
    Connect even if network is not broadcasting: No
    Connectable: No
     Reason: 0x00028002
Information for Connection ID 1
Connection started at: 2015-03-07 19:57:14-186
Auto Configuration ID: 1
Profile: xfinitywifi
SSID: xfinitywifi
SSID length: 11
Connection mode: Infra
Security: No
Pre-Association and Association
   Connectivity settings provided by hardware manufacturer (IHV): No
   Security settings provided by hardware manufacturer (IHV): No
   Profile matches network requirements: Success
   Pre-association status: Success
   Association status: Success
    Last AP: 06-1d-d5-d5-34-f0
Security and Authentication
   Configured security type: Open
   Configured encryption type: None
   802.1X protocol: No
   Key exchange initiated: Yes
    Unicast key received: No
    Multicast key received: No
   Number of security packets received: 0
   Number of security packets sent: 0
   Security attempt status: Success
Connectivity
   Packet statistics
    Ndis Rx: 2068
    Ndis Tx: 2543
    Unicast decrypt success: 0
    Multicast decrypt success: 0
    Unicast decrypt failure: 0
    Multicast decrypt failure: 0
    Rx success: 3954
    Rx failure: 0
    Tx success: 537
    Tx failure: 4
    Tx retry: 2
    Tx multiple retry: 2
    Tx max lifetime exceeded: 0
    Tx ACK failure: 18
   Roaming history: 0 item(s)
InformationalDiagnostics Information (Wireless Connectivity)
Details about wireless connectivity diagnosis:
For complete information about this session see the wireless connectivity information event.
Helper Class: Auto Configuration
Initialize status: Success
Information for connection being diagnosed
Interface GUID: 70a0781d-6329-45e4-8d7c-34aeca294c39
Interface name: Intel(R) Centrino(R) Advanced-N 6250 AGN
Interface type: Native WiFi
Result of diagnosis: There may be problem
Network Connection details from Command Prompt (some info hidden for security reasons)
Connection-specific DNS Suffix:
Description: Intel(R) Centrino(R) Advanced-N 6250 AGN
Physical Address: ‎00-23-15-54-19-B8
DHCP Enabled: Yes
IPv4 Address: 192.168.X.XX
IPv4 Subnet Mask: 255.255.XX.X
Lease Obtained: Saturday, March 07, 2015 7:57:14 PM
Lease Expires: Saturday, March 07, 2015 8:24:44 PM
IPv4 Default Gateway: 192.168.X.X
IPv4 DHCP Server: 192.168.X.X
IPv4 DNS Servers: 75.75.75.75, 75.75.76.76
IPv4 WINS Server:
NetBIOS over Tcpip Enabled: Yes
Link-local IPv6 Address: fe80::b8de:3ac9:e166:XXX%XX
IPv6 Default Gateway:
IPv6 DNS Server:
Results of Ping and Trace Route in Command Prompt
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>ping 127.0.0.1
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Ping statistics for 127.0.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Windows\system32>ping www.youtube.com
Pinging youtube-ui.l.google.com [173.194.121.6] with 32 bytes of data:
Reply from 173.194.121.6: bytes=32 time=24ms TTL=55
Reply from 173.194.121.6: bytes=32 time=19ms TTL=55
Request timed out.
Request timed out.
Ping statistics for 173.194.121.6:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 19ms, Maximum = 24ms, Average = 21ms
C:\Windows\system32>ping 74.125.239.34
Pinging 74.125.239.34 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 74.125.239.34: bytes=32 time=3286ms TTL=50
Request timed out.
Ping statistics for 74.125.239.34:
    Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3286ms, Maximum = 3286ms, Average = 3286ms
C:\Windows\system32>ping www.hotmail.com
Pinging dispatch.kahuna.glbdns2.microsoft.com [65.55.157.204] with 32 bytes of data:
Reply from 65.55.157.204: bytes=32 time=111ms TTL=237
Request timed out.
Request timed out.
Reply from 65.55.157.204: bytes=32 time=1537ms TTL=237
Ping statistics for 65.55.157.204:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 111ms, Maximum = 1537ms, Average = 824ms
C:\Windows\system32>ping 207.46.11.236
Pinging 207.46.11.236 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 207.46.11.236:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Windows\system32>tracert www.youtube.com
Tracing route to youtube-ui.l.google.com [173.194.121.5]
over a maximum of 30 hops:
1    19 ms    13 ms    17 ms xfwsr12-nwca-01.sys.comcast.net [68.85.15.244]
2    13 ms    13 ms    27 ms ae-14-32767-ar03.newcastle.de.panjde.comcast.net [68.85.192.205]
3    20 ms    26 ms    21 ms he-5-10-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.94.249]
4    18 ms    34 ms    22 ms he-0-13-0-0-pe07.ashburn.va.ibone.comcast.net [68.86.86.50]
5    19 ms    18 ms    18 ms 50-248-116-190-static.hfc.comcastbusiness.net [50.248.116.190]
6    35 ms    18 ms    18 ms 209.85.249.217
7    21 ms    19 ms    19 ms 72.14.233.93
8     *        *        *     Request timed out.
9     *     2509 ms   677 ms iad23s25-in-f5.1e100.net [173.194.121.5]
Trace complete.
C:\Windows\system32>tracert 74.125.239.34
Tracing route to nuq04s19-in-f2.1e100.net [74.125.239.34]
over a maximum of 30 hops:
1    54 ms    23 ms    12 ms xfwsr12-nwca-01.sys.comcast.net [68.85.15.244]
2    22 ms    19 ms    17 ms ae-14-32767-ar03.newcastle.de.panjde.comcast.net[68.85.192.205]
3    19 ms    19 ms    18 ms he-5-14-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.166.121]
4    18 ms    18 ms    18 ms he-0-15-0-0-cr01.350ecermak.il.ibone.comcast.net[68.86.85.74]
5    19 ms    18 ms    22 ms 50-248-116-190-static.hfc.comcastbusiness.net [50.248.116.190]
6    22 ms    36 ms    19 ms 209.85.249.217
7    26 ms    23 ms    25 ms 209.85.143.112
8     *        *        *     Request timed out.
9     *        *        *     Request timed out.
10   972 ms     *        *     216.239.51.97
11   148 ms    97 ms    95 ms 216.239.46.241
12   324 ms   130 ms   432 ms 209.85.246.252
13     *        *        *     Request timed out.
14 1403 ms   101 ms   126 ms nuq04s19-in-f2.1e100.net [74.125.239.34]
Trace complete.
C:\Windows\system32>tracert www.hotmail.com
Tracing route to dispatch.kahuna.glbdns2.microsoft.com [65.55.157.144]
over a maximum of 30 hops:
1    13 ms    13 ms    25 ms xfwsr12-nwca-01.sys.comcast.net [68.85.15.244]
2    13 ms    15 ms    13 ms ae-14-32767-ar03.newcastle.de.panjde.comcast.net[68.85.192.205]
3    20 ms    19 ms    17 ms he-5-13-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.95.145]
4    17 ms    20 ms    20 ms he-0-13-0-0-pe07.ashburn.va.ibone.comcast.net [68.86.86.50]
5    17 ms    18 ms    38 ms as8075-2-c.ashburn.va.ibone.comcast.net [173.167.58.82]
6    18 ms    18 ms    36 ms ae4-0.ash-96cbe-1a.ntwk.msn.net [207.46.36.172]
7     *        *        *     Request timed out.
8     *     2191 ms    35 ms ae0-0.atb-96cbe-1b.ntwk.msn.net [191.234.81.167]
9     *        *        *     Request timed out.
10     *        *        *     Request timed out.
11    86 ms    84 ms    84 ms ae4-0.lax-96cbe-1a.ntwk.msn.net [191.234.83.150]
12    86 ms    86 ms    87 ms ae9-0.by2-96c-1a.ntwk.msn.net [207.46.42.176]
13     *        *        *     Request timed out.
14     *        *        *     Request timed out.
15     *        *        *     Request timed out.
16     *        *        *     Request timed out.
17    87 ms    84 ms    85 ms origin.by173w.bay173.mail.live.com [65.55.157.144]
Trace complete.
C:\Users\C.Cunningham>tracert 207.46.11.236
Tracing route to origin.by181w.bay181.mail.live.com [207.46.11.236]
over a maximum of 30 hops:
1    16 ms    16 ms    19 ms xfwsr12-nwca-01.sys.comcast.net [68.85.15.244]
2    18 ms    13 ms    13 ms ae-14-32767-ar03.newcastle.de.panjde.comcast.net[68.85.192.205]
3    21 ms    19 ms    21 ms he-5-12-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.95.141]
4    18 ms    21 ms    18 ms he-0-13-0-0-pe07.ashburn.va.ibone.comcast.net [68.86.86.50]
5     *        *        *     Request timed out.
6     *        *        *     Request timed out.
7     *        *        *     Request timed out.
8     *        *        *     Request timed out.
9     *        *        *     Request timed out.
10     *        *        *     Request timed out.
11     *        *        *     Request timed out.
12     *        *        *     Request timed out.
13     *        *        *     Request timed out.
14     *        *        *     Request timed out.
15     *        *        *     Request timed out.
16     *        *        *     Request timed out.
17     *        *        *     Request timed out.
18     *        *        *     Request timed out.
19     *        *        *     Request timed out.
20     *        *        *     Request timed out.
21     *        *        *     Request timed out.
22     *        *        *     Request timed out.
23     *        *        *     Request timed out.
24     *        *        *     Request timed out.
25     *        *        *     Request timed out.
26     *        *        *     Request timed out.
27     *        *        *     Request timed out.
28     *        *        *     Request timed out.
29     *        *        *     Request timed out.
30     *        *        *     Request timed out.
Trace complete.
Results of Intel WiFi Manual Diagnostics
Test Name                 Test Result   Test Summary
Hardware Test           Passed        Wireless Hardware is enabled
Driver Test           Passed        Diver is loaded. NETwNs64 Version 13.3.0.24
Radio Test                  Passed       Radio is ON
Scan Test                   Passed       There are 25 Networks available to connect
Association Test        Passed       Associated
Authentication Test   Passed       Authenticated
Signal Test                Passed       Signal Quality: Poor
Ping Test                  Failed          No Reponse: default gateway, DHCP server
I hope this information is enough to get to the root of this problem once and for all. Please let me know if you any other information such as event logs or statistics.
Thanks in advance.

Results of Intel WiFi Event View Log (I deleted some lines since there were basically repeats of the same messages)
#Event Source Time
Error Severity    Domain
User      Description
45           EvtEngine
3/8/2015 20:40 Success
Connection         SYSTEM
iAMT - Failed to read Windows Events Log
46           S24EvMon
3/8/2015 20:41 Information
AppDriver
SYSTEM
Getting List of adapters.
47           S24EvMon
3/8/2015 20:41 Information
AppDriver
SYSTEM
Intel adapter(s) found.
156         S24EvMon
3/8/2015 20:47 Information
Driver    SYSTEM
AddToExclude 06:1d:d5:d5:34:f0 xfinitywifi 6 WEV_EXCLUDE_LIST_REASON_802_11_AUTH_FAILURE
157         S24EvMon
3/8/2015 20:47 Information
Driver    SYSTEM
ATC 06:1d:cf:2a:44:c0 xfinitywifi 6 RSSI=-88
158         S24EvMon
3/8/2015 20:47 Error
Driver    SYSTEM
AssociationFailure 06:1d:cf:2a:44:c0 xfinitywifi 6 CNCT_GENERAL_FAILURE
159         S24EvMon
3/8/2015 20:47 Information
Driver    SYSTEM
AddToExclude 06:1d:cf:2a:44:c0 xfinitywifi 6 WEV_EXCLUDE_LIST_REASON_802_11_ASSOC_FAILURE
160         S24EvMon
3/8/2015 20:47 Information
Driver    SYSTEM
ATC 06:1d:d5:d5:34:f0 xfinitywifi 6 RSSI=-79
161         S24EvMon
3/8/2015 20:47 Success
Driver    SYSTEM
RxAuthSuccess 06:1d:d5:d5:34:f0 6
162         S24EvMon
3/8/2015 20:47 Success
Driver    SYSTEM
RxAssocResp 06:1d:d5:d5:34:f0 6 -77
163         S24EvMon
3/8/2015 20:49 Information
TCP/IP SYSTEM
VoIP: Got link down - deleting flows .
164         S24EvMon
3/8/2015 20:49 Information
Driver    SYSTEM
ATC 06:1d:d4:eb:87:00 xfinitywifi 11 RSSI=-88
165         S24EvMon
3/8/2015 20:49 Error
Driver    SYSTEM
AssociationFailure 06:1d:d4:eb:87:00 xfinitywifi 11 CNCT_GENERAL_FAILURE
166         S24EvMon
3/8/2015 20:49 Information
Driver    SYSTEM
AddToExclude 06:1d:d4:eb:87:00 xfinitywifi 11 WEV_EXCLUDE_LIST_REASON_802_11_ASSOC_FAILURE
167         S24EvMon
3/8/2015 20:49 Information
Driver    SYSTEM
ATC 06:1d:d4:eb:87:00 xfinitywifi 11 RSSI=-89
168         S24EvMon
3/8/2015 20:49 Error
Driver    SYSTEM
AssociationFailure 06:1d:d4:eb:87:00 xfinitywifi 11 CNCT_GENERAL_FAILURE
169         S24EvMon
3/8/2015 20:49 Information
Driver    SYSTEM
AddToExclude 06:1d:d4:eb:87:00 xfinitywifi 11 WEV_EXCLUDE_LIST_REASON_802_11_ASSOC_FAILURE
170         S24EvMon
3/8/2015 20:49 Information
Driver    SYSTEM
ATC 06:1d:d4:eb:87:00 xfinitywifi 11 RSSI=-90
171         S24EvMon
3/8/2015 20:49 Error
Driver    SYSTEM
AssociationFailure 06:1d:d4:eb:87:00 xfinitywifi 11 CNCT_GENERAL_FAILURE
172         S24EvMon
3/8/2015 20:49 Information
Driver    SYSTEM
ATC 06:1d:d5:d5:34:f0 xfinitywifi 6 RSSI=-82
173         S24EvMon
3/8/2015 20:49 Success
Driver    SYSTEM
RxAuthSuccess 06:1d:d5:d5:34:f0 6
174         S24EvMon
3/8/2015 20:49 Success
Driver    SYSTEM
RxAssocResp 06:1d:d5:d5:34:f0 6 -81
175         S24EvMon
3/8/2015 20:50 Information
Driver    SYSTEM
AddToExclude 06:1d:d5:d5:34:f0 xfinitywifi 6 WEV_EXCLUDE_LIST_REASON_802_11_AUTH_FAILURE
176         S24EvMon
3/8/2015 20:50 Information
Driver    SYSTEM
ATC 06:1d:d5:d5:34:f0 xfinitywifi 6 RSSI=-79
177         S24EvMon
3/8/2015 20:50 Success
Driver    SYSTEM
RxAuthSuccess 06:1d:d5:d5:34:f0 6
178         S24EvMon
3/8/2015 20:50 Success
Driver    SYSTEM
RxAssocResp 06:1d:d5:d5:34:f0 6 -80
179         S24EvMon
3/8/2015 21:03 Information
Driver    SYSTEM
RoamTrigger 06:1d:d5:d5:34:f0 xfinitywifi 6 RSSI=-81 MisBcn=8 RSSITh=-85 Roam Other Reason
186         S24EvMon
3/8/2015 21:21 Information
General
SYSTEM
DeviceIoCtrlS24NDIS: (2) Failed to send OID 0xff100055 to driver. Error - 31
187
S24EvMon
3/8/2015 21:21 Information
General
SYSTEM
DeviceIoCtrlS24NDIS - Dot11ExtNicSpecificExtension failed (31)

Externally Hosted DNS - How do I set up my 2003 DNS server for sub domain to point to internal IP address??

I have a domain name(domain.com) DNS hosted at my ISP. I also have 3 sub domains DNS hosted at the same ISP pointing to various external ip addresses (mail.domain.com, vpn.domain.com and ts.domain.com). We want to set up sales.domain.com to point to an
internal 10. IP address. We have AD integrated DNS servers for our 2003 AD domain. The AD domain name is totally different than the hosted domain name in question. I currently edit the host file for a couple of PC's but this isnt practical company wide so
I want to add entries on our internal AD DNS servers to resolve the locally hosted site. If i recall, someone once told me that you cannot just put an A record for one sub domain, I would have to have entries on my 2003 DNS server to resolve anything related
to the domain.com name. Is this accurate? If so, what is the proper way to configure my 2003 AD DNS server to resolve anything domain.com related for my internal users while still allowing my ISP to do the DNS lookup for the internet.

On my 2003 AD integrated DNS server...i rightclick forward lookup zone and choose...new zone..primary zone (store zone in AD checkbox checked)..i chose to all DNS servers in the AD domain for replication...zone name sales.domain.com....allow secure updates
option....then i added an A record in that zone...sales.domain.com..pointed that towards my internal 10. IP address...is this correct? It seems to be working correctly for the sales.domain.com DNS record...and i tested the other sub domains...and those look
like they are going to my ISP for DNS resolution...
Is this the correct procedure? I did this on a test AD domain and not my production...i want to make sure i dont break everything under the domain.com by incorrectly adding 1 sub domain..

Can I avoid setting up a DNS server?

Dear all,
I’m a newbie to set up a server but I recently bought a Mac Mini Server and I have some questions in setting up the machine.
My ultimate goal:
Set up a multimedia server in my Mac Mini Server which provide photos up / download and Quicktime video streaming services for my friends outside my local Lan.
My settings:
ISP (Dynamic IP) →DSL modem →Linksys Router (DHCP) →
1. Web Cam IP: 192.168.1.253 port 50000
2. Synology NAS IP:192.168.1.107 port 5000
3. Mac Mini Server IP: 192.168.1.108
4. Mac Book Pro x 2(wireless)
Since I don’t have a static IP, I registered a domain name which link to my dynamic IP. i.e. abc.viewnetcam.com
I can access my web cam and Synology from outside through port forwarding i.e. http://abc.viewnetcam.com: 50000 & http://abc.viewnetcam.com: 5000
During set up my Mac Mini Server, I was required to enter the Primary Domain Name, since I did not have a DNS server in my local Lan, I entered MacMinSserver.private
After I set up the server, I found that there was a message left on the desktop saying that; ….The domain name servers you’re using don’t have an entry for the domain MacMiniServer.private, and therefore your clients won’t be able to access your server using the name MacMiniServer.private…..
Now here is the question:
1. Can I just simply avoid to set up a DNS server in my Mac Mini Server? Cause it is very complicate; I have read up some information about DNS server settings which make me feel puzzle.
2. If DNS server is a must, so how can I set it? I have read the instructions in the HoffmanLabs, but after setting up the DNS server, how can I access my server from outside? Through port forward?
( Now I can access my server from outside in Safari with URL afp://abc.viewnetcam.com:548)
Many thanks.

I take some time to digest your suggestions. I’m convinced to build up a DNS server, although I don’t fully understand how it works.
DNS is a way to ask a server or a series of servers to translate a string of a specific format into an IP address. If you follow the article in your implementation, then the local DNS services will cooperate with and access external DNS servers world-wide for public DNS translations.
But then questions come up again, first what should be my Primary Domain Name?
I don't know what you're looking at that is using "primary domain name", but the "domain name" you use? I use real and registered and public domains for the domain on private LANs. It's simple, effective, and unique. And I don't have to deal with collisions. I don't prefer to recommend using a made-up domain, as it's a few dollars to get a real domain and then you don't have to deal with collisions if and when you need to expose parts of your network.
Here, a bogus TLD would be, for instance, macminiserver.myhouse.ngmy69; that's a top-level domain (ngmy69) (TLD) that is not allocated, and unlikely to be publicly allocated, and a subdomain (myhouse) of your choice, and a host name (macminiserver) of your choice. (There are around 300 TLDs already allocated and live, and more are on the way. com, net, biz, org, travel, cat, two-character country codes, and more...)
This is listed in the article, including the trade-offs, and including a description of bogus domains.
As you said that the external DNS and the internal DNS should be separately functioning, then is it true that I have the freedom to choose my Primary DNS name? Or I have to stick to certain rules?
DNS and IP routing work by cooperation. You have to stick to certain rules, and the article guides you through the four general choices for picking a domain name.
In my case, do I need to use the external domain name, i.e. macminiserver.abc.viewnetcam.com or I rent another registered domain name and it will be macminiserver.xxxxx.com or even I create an imaginary name?
After you get your LAN DNS going, then read the [dynamic DNS article|http://labs.hoffmanlabs.com/node/1541].
Here, you've picked a domain (viewnetcam.com) name that's real and registered. That, and the use of the abc and macminiserver subdomains are something you'd have to work out with the folks administering that domain. While it is technically a domain name, macminiserver.abc.viewnetcam.com is also variously called a host name, as that'll usually have an associated IP address, and a subdomain like abc.viewnetcam.com might and variously will not.
With a real and registered domain (your own registered domain, or a DynDNS host), you can (later) choose to expose parts of your network. You don't own a DynDNS name, and DynDNS doesn't allow you to use various server functions and you can't use that on your LAN. DynDNS is a good solution for remote access into a home network and even for a VPN connection in but (if you're eventually looking to use mail or secure web access or other features) you'll usually end up using your own domain name.
The second question is that, how can I avoid using the subnet 192.168.1.0/24, as my router is providing the DHCP service, will that means I need to re-organized the whole network included the web cam and my Synology? Is there any simple way to achieve that?
It's the effort you think it is, and it involves getting that gateway server reconfigured to have its address in a different subnet and the DHCP server reconfigured to pass out addresses within a range within that subnet, and this is an effort that scales as your network increases and as you get IP addresses embedded. If you're going to do remote access via VPN, many home networks and many coffee shops will use 192.168.0.0/24 or 192.168.1.0/24, and having the same subnet on both ends of the VPN means IP routing tosses a snit.
[Please read the DNS article|http://labs.hoffmanlabs.com/node/1436] through, and then post up questions you might have.

How do I create a backup DNS server?

Hi All,
I've got my production server (Xserve Intel) running 10.6 and it is our primary DNS server. I've gotta take it down to do some work on it, but by doing so, no one in the organization will be able to access the internet.
I'd like to set up my old Xserve (G5, running 10.5) as a backup DNS server that can handle the DNS requests whenever I need to take the main server down. Unfortunately, I'm kind of a DNS n00b.
What is the best way to go about this?
Thanks,
Chris

Oh, quite embarrassing. I complained about not understanding the author of the article when I was actually speaking to the author. How rude! Apologies, kind sir.
I've now got it set up correctly with your help, it seems. I've just got a few other questions regarding the Secondary DNS Server if you don't mind:
1) Do I set any forwarder IP Addresses on the secondary server? Should I put the same forwarders that I use on my primary, or should I put the IP address of my primary in there, or should I just leave it blank?
2) *Edit - Ignore question 2; found the answer in your guide*
3) When I look at the secondary zones, they don't seem to be populated with any data. . . Does this mean that the secondary server is completely reliant on the primary server to function correctly? In other words, *when I take my primary server offline, does the secondary server still work?*
Thanks,
Chris
Message was edited by: cscrofani

Proper Configuration of DNS server for our new branch office

Hi All,
Our new office will setup a new branch office with a routed network link to our HO. In HO, we have 2 domain controllers configured as AD and DNS just for fail over scenarios.
How will we configure the DNS server of our 3rd domain controller which we will placed in the new branch office. What would be the proper settings of DNS server integrated to AD to work well especially to have a successful replication and communication to
the 2 DC's located in HO?

Hi,
If you have multiple DC's in that site i would recommend using any of the partner DC's IP addresses as preferred one and secondary DNS IP to pointing to itself. Dont use loopback addresses configure it with actual IP addresses.
If you have only one server in branch office point itself as the primary DNS and HO DC as secondary and tertiary.
Make sure that all clients in your branch site are pointing to the branch DC as primary DNS server.
Regards,
Rafic
If you found this post helpful, please give it a "Helpful" vote.
If it answered your question, remember to mark it as an "Answer".
This posting is provided "AS IS" with no warranties and confers no rights! Always test ANY suggestion in a test environment before implementing!

Can't override DNS Server settings - can only append!

See this thread for a similar question:
http://discussions.apple.com/thread.jspa?messageID=3555096
I have also filed this with Apple (Problem ID 5159216). Here is the text of the report (with a few bits removed - not crucial to understanding the report).
If anyone has suggestions/clues to resolve, please advise. Thanks!
Summary:
This problem concerns AirPort Extreme (802.11n) at revision 7.1. I will summarize with a comparison between AirPort and MacOS X.
MacOS X and Airport Extreme (referred herein as "AE") both permit editing of DNS server settings whether in DHCP or Manual mode.
When MacOS X DNS server settings are set manually by the end-user, the new server IPs are used (good). When AE's DNS server settings are overridden by the end-user, the new server IPs are NOT used (not good)! Rather, the DHCP-supplied DNS server always pre-empts whatever is given in the AE Configuration UI.
Steps to Reproduce:
1. Using AirPort Extreme (802.11n) at revision 7.1 and MacOS 10.4.9 on a MacBook Pro (Core 2 Duo). The AE has been previously configured for IPv4 using DHCP and the MacBook is successfully connected and resolving domain names through the AE.
2. Visit "Apple Menu > Location > Network Settings" and check the AirPort TCP/IP settings. For purposes of this test, make sure the "DNS Servers" field is EMPTY so MacOS X defaults to the AE's DNS settings, then close System Preferences.
3. Run "AirPort Utility" (the newer version, not "Airport Admin Utility") and configure the AE under test. Pick the "Internet" icon in the toolbar and note the Internet Connection settings.
4. In this test, Configure IPv4 is set to "DHCP" and the DNS Server(s) field contains two DNS IPs assigned by the Internet Service Provider. In my case that's Cablevision's Optimum Online service. You may or may not see IP addresses here, but in my case they are visible.
5. As the DNS Server(s) are editable, and they both show ISP-supplied addresses, they can be changed to whatever alternate IPs you wish. For instance, change them to these alternate DNS IPs from OpenDNS.com: 208.67.222.222 and 208.67.220.220. (You could use any alternate set of IPs but for the purpose of this test use the OpenDNS IPs.) Update the AE and restart.
(For additional reference, http://www.opendns.com/start/airport.php shows instructions for the older AirPort Admin Utility, but the concept is exactly the same.)
6. Normally you shouldn't have to restart the MacBook Pro since we're just using the AE settings, but go ahead and do that just to be consistent with this test.
Expected Results:
Now for the moment of truth! We want to verify that we're using the OpenDNS IPs for our DNS Servers. One nice feature OpenDNS has is automagic redirection for certain domain name typos.
Here's an example. Drop to shell (Applications > Utilities > Terminal) and try this command (excluding the $ prompt, natch):
$ dig craigslist.og
The "og" typo is deliberate. We really want to go to craigslist.org. If you're using the new OpenDNS IPs, you will STILL get an Address (A) record with an IP like so:
;; ANSWER SECTION:
craigslist.og. 0 IN A 208.69.32.130
If you had entered "craigslist.og" in Safari, you would end up at 208.69.32.130 (an OpenDNS server) and then redirected to craigslist.org.
Actual Results:
Alas, that's not what happens! Instead, you get NO IP address, like so:
;; QUESTION SECTION:
;craigslist.og. IN A
This means we're not actually using the OpenDNS IPs. What's happening?
To find out, I spoke with the AirPort support group (Case # xxx-xxx-xx). I learned that, despite being allowed to edit and override the IP addresses provided via DHCP, the AE still uses the DHCP-provided DNS server if available.
Again, the user interface suggests that I'm allowed to override the DHCP-provided DNS IPs as shown in the UI. Even though I can do this, the AirPort will still keep note of any DHCP-provided DNS Server IPs and use those first.
True, I can switch to Manual network settings (and then my own DNS Server IPs take effect). Of course this is problematic when the ISP renews my IP address (which it does from time to time).
Another workaround is to use the "DNS Servers" settings noted in step 2 (above). However this is also problematic if I want to keep my network settings simple. It requires a "Home Network" location and an "Office" location. Still not preferable, but it's a workaround.
Regression:
n/a
Notes:
I would like AirPort's DNS settings to be overridden in the same way OS X allows DNS settings to be overridden. The user interfaces suggest this is possible but it is not. It's only possible in the OS X case. Having the same flexibility on the AirPort would be most welcome.

Afraid of the answer...sheesh...you must be a child. This has nothing to do with masquerading anything. The issue being discussed here is that people want to manually assign a dns server address via the new AEBS, while maintaining DHCP for IP address assignments through their ISP. For example, I would like to have opendns.com take care of all dns addressing at the router level, even though I have "Configure IPv4" set to "Using DHCP". If you do not understand why one would want to use something like opendns.com, please visit their website and enlighten yourself. The fact that the dns server address fields are editable when set to "Using DHCP" leads one to believe that you can manually assign a dns server in this configuration; however, under firmware 7.1.1, you still cannot. The previous iteration of the airport hardware can do it, as can nearly any router you pull off the shelf. In addition, this is something that can easily be done at the individual-computer level in OS X; however, many people would prefer to administer their network at the router level. That is the issue being discussed here. Either you can't read or you are purposely derailing the thread.
iMac 24" Mac OS X (10.4.9)

Can't connect to mail server - DNS Server settings?

Hello:
Let me preface this question by saying that computer networking is not my strong suit.
Last week I moved our web hosting from our ISP to Lunarpages; our domain is marshall-arts.net. I set up some POP email accounts on our new mail servers and was able to successfully send and receive email wirelessly using our G4 ibook. However, none of our networked desktop systems could connect to our new mail server, although they could connect to our ISP's mail server; they also have no problem connecting to the web. The mail server and user names were identical between the desktop systems and the ibook. But upon closer examination of the TCP/IP settings of the ibook I found that the ibook had 209.253.113.10 entered into the DNS Servers (optional) field. That field was blank in the desktop systems. Once I entered that address into the DNS Servers field on the desktop systems they had no problem connecting to our Lunarpages mail servers.
Here's our setup, as best as I can describe it:
We have an AirPort Extreme connected to our DSL router. It's connected via ethernet, configured manually with a static IP, router and DNS server addresses provided by our ISP. It's set to distribute IP addresses with the AirPort client computers sharing a single IP address using DHCP and NAT (10.0.1.1. addressing). It's connected via ethernet to a Linksys gigabit ethernet switch to which we have connected three desktop Macs running OS 10.3.x and 10.4.x.
The TCP/IP of the three desktop systems and the ibook are configured Using DHCP.
As I wrote above, only the ibook had an address entered into the DNS Servers field, 209.253.113.10. This doesn't correspond to anything our ISP provided (those addresses are entered in the AirPort Extreme.) I have no idea where it came from.
So I have two questions:
Would that address have been generated automatically while setting up the AirPort connection on the ibook?
Why would that supposedly optional DNS Server address be required for me to connect to our new mail servers (but not our old ISP mail servers)?
Thank you.
Shawn Marshall
Marshall Arts Motion Graphics
Dual 2.5 Ghz G5 Mac OS X (10.4.7)
Dual 2.5 Ghz G5 Mac OS X (10.4.7)

Hello:
Let me preface this question by saying that computer networking is not my strong suit.
Last week I moved our web hosting from our ISP to Lunarpages; our domain is marshall-arts.net. I set up some POP email accounts on our new mail servers and was able to successfully send and receive email wirelessly using our G4 ibook. However, none of our networked desktop systems could connect to our new mail server, although they could connect to our ISP's mail server; they also have no problem connecting to the web. The mail server and user names were identical between the desktop systems and the ibook. But upon closer examination of the TCP/IP settings of the ibook I found that the ibook had 209.253.113.10 entered into the DNS Servers (optional) field. That field was blank in the desktop systems. Once I entered that address into the DNS Servers field on the desktop systems they had no problem connecting to our Lunarpages mail servers.
Here's our setup, as best as I can describe it:
We have an AirPort Extreme connected to our DSL router. It's connected via ethernet, configured manually with a static IP, router and DNS server addresses provided by our ISP. It's set to distribute IP addresses with the AirPort client computers sharing a single IP address using DHCP and NAT (10.0.1.1. addressing). It's connected via ethernet to a Linksys gigabit ethernet switch to which we have connected three desktop Macs running OS 10.3.x and 10.4.x.
The TCP/IP of the three desktop systems and the ibook are configured Using DHCP.
As I wrote above, only the ibook had an address entered into the DNS Servers field, 209.253.113.10. This doesn't correspond to anything our ISP provided (those addresses are entered in the AirPort Extreme.) I have no idea where it came from.
So I have two questions:
Would that address have been generated automatically while setting up the AirPort connection on the ibook?
Why would that supposedly optional DNS Server address be required for me to connect to our new mail servers (but not our old ISP mail servers)?
Thank you.
Shawn Marshall
Marshall Arts Motion Graphics
Dual 2.5 Ghz G5 Mac OS X (10.4.7)
Dual 2.5 Ghz G5 Mac OS X (10.4.7)

Windows server 2012 standard second DNS server not automaticly detected by Windows 7.

Hi!
We have configured a second DNS server on our domain just in case.
I have tested the second DNS by activating manually the second dns server in the IPV4 config in windows 7 pro.
My question is: the second DNS server is not supposed to be detected automaticly by windows?
Thanks you.

Hi,
There may be some misunderstanding about how DNS works.
DNS client doesn't detect DNS servers. DNS client doesn't know which zone is hosted by the DNS server. DNS client can only send DNS query to the DNS servers which are configured in the client.
As I mentioned above, the DNS Client service queries the DNS servers in the following order:
The DNS Client service sends the name query to the first DNS server on the preferred adapter’s list of DNS servers and waits one second for a response.
If the DNS Client service does not receive a response from the first DNS server within one second, it sends the name query to the first DNS servers on all adapters that are still under consideration and waits two seconds for a response.
If the DNS Client service does not receive a response from any DNS server within two seconds, the DNS Client service sends the query to all DNS servers on all adapters that are still under consideration and waits another two seconds for a response.
If the DNS Client service still does not receive a response from any DNS server, it sends the name query to all DNS servers on all adapters that are still under consideration and waits four seconds for a response.
If it the DNS Client service does not receive a response from any DNS server, the DNS client sends the query to all DNS servers on all adapters that are still under consideration and waits eight seconds for a response.
In your case, if you configure the DNS2 as the secondary DNS server on Windows 7, when the DNS1 is down, Windows 7 will send DNS query to DNS2 after 3 sceconds(Step 3).
Best Regards.
Steven Lee
TechNet Community Support

Do I need to run local DNS server for NAT/DHCP to work?

Hello,
I'm coming across all kinds of explanations how to set up a server for public access, having a static IP and a pointed domain, but I have a dynamic public IP and don't need the server to be accessible through a domain name. I just want all the computers in my office to connect to the web over 1 cable connection. I've used Gateway Setup Assistant to set up NAT and DHCP and DNS and what not, but it didn't work out of the box. After some bootpd.plist fixes I now have DHCP working, it's handing out IP addresses, but all LAN connected machines cannot get onto the web, only the server can.
What am I doing wrong? Should I configure my DNS server differently? Or should it not be on at all, couldn't the local machines use my ISP's DNS servers?
Currently DNS is configured like this:
Settings are:
accept recursive queries from the following networks: localnets
forwarder IP addresses: (empty)
Zones are:
private. primary zone
134.23.24.in-addr.arpa. reverse zone

Though still a valid question for others I guess, I got my DNS working. The network preferences didn't have external DNS servers configured for the local network interface.

Resolving arabic domain name in Solaris DNS server

Hi..
I just quickly want to know how can i define arabic font domain name to get resolve in my DNS server?
I tried to put entry with arabic name but editor making it abnormal, i recently get arabic locale installed on server through north Africa region. Locale is now showing me "AR" ..
Thank you

Sorry my bad.... slight mistake in my question...Here is my corercted query--
After successfully connecting to the internet, when I do NSLOOKUP on the DC, the DNS doesnt resolve my internal domain/site but instead resolves external sites on the internet.
My computer FQDN is nri.wwe.com
Domain dns name is wwe.com
The above should get resolve internally but it searches on the internet.
This is how it should work
& it works perfect when I disable the other NAT network adapter (i.e. disable internet connectivity on my virtual DC)
C:\>nslookup nri.wwe.com
Server: nri.wwe.com
Address: 192.168.1.11
Name:    nri.wwe.com
Address: 192.168.1.11
But when I again enable internet connectivity, this it what happens.
C:\nslookup www.wwe.com
DNS request timed out.
    timeout was 2 seconds.
Server: UnKnown
Address: 192.168.12.2
DNS request timed out.
    timeout was 2 seconds.
Non-authoritative answer:
DNS request timed out.
    timeout was 2 seconds.
Name:    www.wwe.com.nsatc.net
Address: 64.152.0.124
Aliases: www.wwe.com
And when I again nslookup, this is what I get,
C:\>nslookup www.wwe.com
DNS request timed out.
    timeout was 2 seconds.
Server: UnKnown
Address: 192.168.12.2
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to UnKnown timed-out
Now this 192.168.12.2 is VM assigned DNS via VM Natting with its own DHCP. If we do it manually, none of the virtual machines can connect to the internet. So I cannot fiddle with it anymore as I have already that as well.

Change of DNS server setting caused Exchange outages!

I am trying to google/bing my way through this, but here are the main points:
All remote Exchange servers had a) static IP addresses and b) were instructed to use DNS servers in Edmonton and Calgary
If WAN links dropped, they lost DNS
SOLUTION! Point remote servers to the domain controller in that location as the primary DNS server. WAN outage means Exchange still resolves names locally.
Well the day came and we add the local DNS server for each remote site as the primary DNS server at the top of "DNS server addresses, in order of use" portion of advanced TCP/IP settings dialogue box.
A reboot is performed
Voila! Exchange shits the bed! Hub transport servers in Edmonton and Calgary cannot resolve remote server names; as in no host(a) record exists for them anymore. And we have a 91 minute outage until the DNS is sorted out (ipconfig /registerdns run on each
server).
Has anyone encountered this or have some deep knowledge of DNS (relative to my own) that could at least throw out a theory as to why this might happen?

Hi, please issue Get-ExchangeServer -Identity "ServerName" -status | fl and check:
CurrentDomainControllers
CurrentGlobalCatalogs
CurrentConfigDomainController
The server must been linked to the wrong server. You can change that in powershell too.
Regards, Philippe
Don't forget to mark as answer or vote as helpful to help identify good information. ( linkedin endorsement never hurt too :o) )
Answer an interesting question ? Create a
wiki article about it!

DNS Server Question

Similar Messages

Maybe you are looking for