New Cisco Linksys e4200 internal DNS not resolving

I have a e4200 sitting behind a BT home hub 2. The home hub provides internet connection to the e4200, and the e4200 allows all devices to connect. I am able to ping internal IP addresses, but when I try to ping by device name it returns the external IP address. How can I view / amend the DNS table on the router?

I've amended entries to protect my security, but this should give the general gist:
Windows IP Configuration
   Host Name . . . . . . . . . . . . : E001
   Primary Dns Suffix . . . . . . . : MyHome.net
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : MyHome.net
                                       home
Ethernet adapter Local Area Connection:
   Connection-specific DNS Suffix . : home
   Description . . . . . . . . . . . : Intel(R) 82566DM-2 Gigabit Network Connection
   Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.0.65(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 17 January 2012 18:24:56
   Lease Expires . . . . . . . . . . : 17 January 2012 20:03:56
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DNS Servers . . . . . . . . . . . : 192.168.1.254
                                       192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.home:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . : home
   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
The "external IP address" which it resolves to is 82.98.86.161 www161.sedoparking.com - thank you for asking, I was previously assuming (incorrectly) that it was resolving back to the external IP address assigned by my ISP.
I'm still none the wiser as to why names are not being resolved at the linksys router for the internal network.

Similar Messages

When the message arrives, the message tone sound that many times. How this problem can be solved? I installed the new version, but the problem is not resolved, the future is to be taken into account in the new version of this?

When the message arrives, the message tone sound that many times. How this problem can be solved? I installed the new version, but the problem is not resolved, the future is to be taken into account in the new version of this?

I'm not sure I understand the question, is the message tone going more then once?
Turn off repeat message alert here:
settings > notifications > messages > repeat alert > never
Some people have found this does not stop the repeat miessage tone,
if you are one of those then I suggest you contact Apple:
http://www.apple.com/feedback/iphone.html
They may not respond, but hopefully will fix in uodate if enough people complain.

Airport with Cisco / Linksys E4200 Router

Hi, I have not been able to find a straight forward answer so i'm posting this.
I'm looking to switch my Linksys router over to N wireless, vs N and G or Just G- Not sure what it is now. I don't have great connection on my 2nd floor, with my Linksys router on the first floor. I want to use this as a bridge (instead of the RE1000), because i want the 5ghz, and AirPlay.
Can i use this as a plug and play bridge? I just want it to extend the signal, and be able to use airplay. No new network.
Some info i thought i would add:
ISP Cat 5 or 6? to Modem to Router (E4200)
Ping at 64 bytes
WPA2/WPA Mixed Mode Security
Thanks in advance.

No you will not be able to use an AirPort to extend the wireless range of the Cisco/Linksys router if they will be interconnected by wireless. However, if they can be interconnected by wire, you could configure them for a roaming network.

Cisco Linksys E3000 - Open DNS Error

I just purchased a Cisco Linksys E3000 and got it set up pretty much the way I want it. My only remaining problem is I wish to used Open DNS as my DNS server. On Line chat support says,"Please access router set up. Under the set up tab you will see the option for DNS1 and DNS2 please change it to 208.87.222 & 208.67.220 and save settings". I replied"I am on the basic set up page and currently I see Static DNS 1 thru 3 which are currently all zeros is that where you want me to put the new DNS numbers?"
I made the changes as directed, saved and also flushed the DNS cache in Windows and in Firefox, rebooted and everything worked great.
The problem is if the computer goes to sleep or is shut down when it restarts it cannot find the DNS server! What am I missing?
Thanks

Thanks for your help. This one really has me baffled
As you can see below the static DNS is set to 3 adddresses for Open DNS and everthing works fine.untill either the computer goes to sllep or is shut down. Then the router can no longer locate a DNS server. The only way I can find to get everything working again is to zero out the address for Open DNS and reboot the router which somehow reestablises the DNS servers as:
DNS Servers . . . . . . . . . 156.154.119.11
                                       156.154.129.11
                                       192.168.1.1
You can also this below and I hope you have some idea of what is happening. I never had this problem before with any other routers on this system.
Thanks,
Chick
C:\Windows\system32>ipconfig /all
Windows IP Configuration
   Host Name . . . . . . . . . . . . : Dominator
   Primary Dns Suffix . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection 3:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : TAP-Win32 Adapter V9
   Physical Address. . . . . . . . . : 00-FF-8F-A2-D9-9F
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Local Area Connection 2:
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet #
2
   Physical Address. . . . . . . . . : 00-04-4B-14-AE-3F
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::6d9a:9c78:1a19:fbfa%19(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.133(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Saturday, September 24, 2011 2:57:14 PM
   Lease Expires . . . . . . . . . . : Sunday, September 25, 2011 3:07:26 PM
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 469763147
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-75-07-8A-00-04-4B-14-AE-3F
DNS Servers . . . . . . . : 208.67.222.222
                                       208.67.220.220
                                       208.67.220.222
   NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{13320496-B6EC-4CA2-9952-BDB3B51EED80}:
   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 Local Area Connection* 12:
   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.{8FA2D99F-77B6-4DB6-9F88-C9952D1BE3EF}:
   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:\Windows\system32>
After Zeroing out Static DNS from Open DNS Address I get:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>ipconfig /all
Windows IP Configuration
   Host Name . . . . . . . . . . . . : Dominator
   Primary Dns Suffix . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection 2:
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet #
2
   Physical Address. . . . . . . . . : 00-04-4B-14-AE-3F
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::6d9a:9c78:1a19:fbfa%19(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.133(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Saturday, September 24, 2011 3:38:12 PM
   Lease Expires . . . . . . . . . . : Sunday, September 25, 2011 3:38:12 PM
   Default Gateway . . . . . . . . . : fe80::c2c1:c0ff:fe7b:a655%19
                                       192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 469763147
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-75-07-8A-00-04-4B-14-AE-3F
   DNS Servers . . . . . . . . . . . : 156.154.119.11
                                       156.154.129.11
                                       192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Local Area Connection* 12:
   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
   IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:3451:dea:3f57:fe7a(Prefe
rred)
   Link-local IPv6 Address . . . . . : fe80::3451:dea:3f57:fe7a%10(Preferred)
   Default Gateway . . . . . . . . . : ::
   NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter isatap.{13320496-B6EC-4CA2-9952-BDB3B51EED80}:
   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:\Windows\system32>

DNS not resolving on one Mac but the other works fine in same local network

Snow Leopard is doing something strange to the DNS or the permission to ping.
I have 2 Macs on the same local network, connect through the same ISP (verizon FIOS). One has no problem resolving any domain, but the other is constantly not resolving some domains.
The problem progresses like this:
* All of a sudden, DNS is not resolving from Ethernet (when it did perfectly well a minute ago).
* Then I switched to wireless (using the same LAN), and it resolved fine.
* Then it failed completely a few minutes later.
* Then I reboot my Mac, and it seemed to clear that, and worked for a day.
* Then it failed again in both Ethernet and Wireless; rebooting does not fix it.
* I cleared all the caches using Onyx, did "dscacheutil -flushcache", zapped the PRAM, reinstalled 10.6.2 combo update, repaired the permission, nothing works.
* Since the unresolved domain is my own domain, I changed the nameserver, and waited for it to propagate to see if that may be the problem, since it appeared that it is not resolving the A Record, and I waited 72 hours, and it is not resolved or propagating to the local DNS, but it worked perfectly well on my other Mac within the same network.
* Then I added other DNS, such as google DNS 8.8.8.8 or openDNS servers to it, but it didn't fix anything.
* Then I "ping" either the unresolved domain or my own Mac .local, and it gave me the error "permission denied". (Whereas I have no problem pinging my own Mac or the unresolved domain in my other Mac that works!).
* Then I "sudo ping" the unresolved domain or my own Mac, and it pinged perfectly well.
* Then I tried "ping6" my own Mac or the unresolved domain on the broken Mac, and it worked fine!
* Also, I used http://network-tools.com to ping it, and noticed that during the trace, somewhere along the route through te7-2.dsr02.dllstx3.theplanet.com and po2.car04.dllstx5.theplanet.com, it timed out along the route, so I don't know if the timeout could have been causing the reject, but I doubted, because "sudo ping" locally will get through but "ping" does not.
So I think I traced the Snow Leopard DNS problem as follows:
* Why does "ping6" works, but "ping" permission is denied unless the user is root?
* I tried to "chmod 4755 ping" but it won't let me.
* Is it because DNS is resolving using IPv6 but not IPv4?
* Or is Snow Leopard somehow screwed up the permission to access ping or similar DNS service?
* Why DNS has no problem in one Mac but caused problem on the other Mac, even though they are in the same local network?
* The only difference between the Macs maybe because I have Parallels installed in the Mac that failed to resolve DNS (with the extra Parallels Shared Ethernet), which may be interfering with it, but I tried to turn Parallels Shared Ethernet off, and it did not fix the problem.
Can anyone help or have any idea that I can fix this nagging bug with DNS? The DNS had worked before, but it simply quit working all of a sudden, and nothing can resurrect it.
Thanks.

Shut down Parallels and restart w/o letting any of Parallels TCP/IP stack resurrect itself. So many network issues with VM solutions. See if the problem persists. Create a new account and ping from there. Are your search domains manually entered on the 10.6 box?

External DNS not resolving SBS2011

Hi,
Hoping someone can help me out here. We have an SBS server that is no longer forwarding external DNS queries. We setup a secondary DNS server onsite so users would still be able to access web resources, but our primary DC only resolve
internal DNS. We have checked the forwarders on the servers (same on both), and one server resolves the forwarders, the other can't.
I have triedrestarting the DNS service, flushing DNS cache and a server restart. I've also checked forwarders and root hints, but can't see anything wrong in the configuration. Both servers have NIC set with the other DNS server as primary and itself
as secondary.
I tried running an nslookup which works when both DNS servers are polled, but fails on the SBS server if it tries to poll itself or an external DNS server.
Anyone have any ideas?
Thanks
Luke

Here is the results from my dcdiag test:
dcdiag /test:dns
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = SERVER01
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\SERVER01
Starting test: Connectivity
......................... SERVER01 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\SERVER01
Starting test: DNS
DNS Tests are running and not hung. Please wait a few minutes...
......................... SERVER01 passed test DNS
Running partition tests on : ForestDnsZones
Running partition tests on : DomainDnsZones
Running partition tests on : Schema
Running partition tests on : Configuration
Running partition tests on : domain
Running enterprise tests on : domain.com.au
Starting test: DNS
Test results for domain controllers:
DC: SERVER01.domain.com.au
Domain: domain.com.au
TEST: Forwarders/Root hints (Forw)
Error: All forwarders in the forwarder list are invalid.
Error: Both root hints and forwarders are not configured or
broken. Please make sure at least one of them works.
Summary of test results for DNS servers used by the above domain
controllers:
DNS server: 128.63.2.53 (h.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.63.2.53
DNS server: 128.8.10.90 (d.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.8.10.90
DNS server: 139.130.4.4 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 139.130.4.4
DNS server: 139.134.5.51 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 139.134.5.51
DNS server: 192.112.36.4 (g.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.112.36.4
DNS server: 192.203.230.10 (e.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.203.230.10
DNS server: 192.33.4.12 (c.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.33.4.12
DNS server: 192.36.148.17 (i.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.36.148.17
DNS server: 192.5.5.241 (f.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 192.5.5.241
DNS server: 193.0.14.129 (k.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 193.0.14.129
DNS server: 198.41.0.10 (j.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 198.41.0.10
DNS server: 198.41.0.4 (a.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 198.41.0.4
DNS server: 202.12.27.33 (m.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 202.12.27.33
DNS server: 203.50.2.71 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 203.50.2.71
DNS server: 203.8.183.1 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 203.8.183.1
DNS server: 208.67.220.220 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 208.67.220.220
DNS server: 208.67.222.222 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 208.67.222.222
DNS server: 209.244.0.3 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 209.244.0.3
DNS server: 209.244.0.4 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 209.244.0.4
DNS server: 210.23.129.34 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 210.23.129.34
DNS server: 220.233.0.1 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 220.233.0.1
DNS server: 220.233.0.2 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 220.233.0.2
DNS server: 4.2.2.1 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 4.2.2.1
DNS server: 4.2.2.2 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 4.2.2.2
DNS server: 61.8.0.113 (<name unavailable>)
1 test failure on this DNS server
PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 61.8.0.113
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
Domain: domain.com.au
SERVER01 PASS PASS FAIL PASS PASS PASS n/a
......................... domain.com.au failed test DNS
Hope this helps.
Thanks
Luke

Airport Extreme 802.11ac local dns not resolving

I have an AirPort Extreme 802.11ac wireless router that I cannot get to resolve local dns names and entries. Everything else is working perfectly, even external dns resolution, but any local dns hostname does not resolve. I can ping the ip addresses of all local systems, I just cannot resolve them. I have checked all configurations and they are set correctly. Please help

adbrennick wrote:
Update:
Setting the AE in Bridge Mode works fine.
Because the dns is then moved to the main router.
Apple are bent on removing as much as possible from even what little was available in 5.6 utility.. so each update removes yet more options.. as for having telnet or ssh .. go wash out your mouth.. they are anathema to Apple total control of the environment.. I mean to say you might set something they didn't intend.

DNS not resolving to new machines on network after increasing DHCP pool size

Hello,
I am having a very strange issue with connecting new machines to reach the internet.
We have a ASA 5505 which the previous tech configured the DHCP pool to 192.168.1.60 - 192.168.1.110
We ended up reaching our limit which I changed it to: 192.168.1.60 - 192.168.187
Then next day when I arrived to work, our DC was hung from windows updates. Once we got everything back up, every computer currently on the network can reach the internet/VPN tunnels etc. So (continuing with my day) I created a new server in a VM (Hyper-V)
I can ping everything internally (even the router) 192.168.1.1, but I cannot resolve DNS. I have configured a static IP, tried Dynamic IP.
I have looked for any ACL indicating to block outside the range of the old DHCP pool but no luck.
On my local maching I can ping the DNS addresses, but just not on the new server.
Can anyone point me in the right direction to where to look for this issue?

I ended up figuring out what the issue was.
Since it was in a Hyper-V VM. the hosting server had to be updated to SP1.
Once completed, and rebooted. The VM in question got an IP address.

Bordermanager setup dns not resolving

Hi,
Our existing BM server HD died...I replaced the drive and rebuilt it.
Having problems with DNS resolving which I think are also causing my
other problems. Client trust isn't communicating correctly (no stats)
and I can't resolve internal addresses when pointed to the BM server.
Have read through various posts related to dns but haven't had any luck.
We have a very simple system...another appliance does the firewall.
The server has one NIC...filtsrv is off....have tried it with nat and
without..tried it with dns proxy and without. it sees the rules which
are are the top of the tree. The clients all exist from the previous
server so they have the firewall exceptions needed but I did disable the
windows firewall to test on a couple of systems I am obviously
missing something in the setup. Any help is appreciated.
Thanks
JT

JT wrote:
> Hi,
>
> Our existing BM server HD died...I replaced the drive and rebuilt it.
> Having problems with DNS resolving which I think are also causing my
> other problems. Client trust isn't communicating correctly (no stats)
> and I can't resolve internal addresses when pointed to the BM server.
> Have read through various posts related to dns but haven't had any luck.
> We have a very simple system...another appliance does the firewall. The
> server has one NIC...filtsrv is off....have tried it with nat and
> without..tried it with dns proxy and without. it sees the rules which
> are are the top of the tree. The clients all exist from the previous
> server so they have the firewall exceptions needed but I did disable the
> windows firewall to test on a couple of systems I am obviously
> missing something in the setup. Any help is appreciated.
>
> Thanks
>
> JT
forgot to mention....dns is not on this server it is pointing to a
different box for dns.
thanks

Any solutions to the DNS not resolving IPv6 problem?

Hello,
Does anyone know how to fix the broken DNS behaviour that was introduced into OS X sometime since 10.4? I'd like to have my systems be able to resolve AAAA addresses, but Apple seems to have broken DNS resolution (probably in response to people complaining about problems which are a result of other IPv6 equipment which are broken!)
Note that this has nothing to do with whether IPv6 works. It does. It's just that OS X's DNS resolver does not return AAAA records at all. Take a look:
[lain:~] john% ping6 andromeda.ziaspace.com
ping6: No address associated with nodename
[lain:~] john% host -t aaaa andromeda.ziaspace.com
andromeda.ziaspace.com has AAAA address 2001:4830:1200:17::2
[lain:~] john% ping6 2001:4830:1200:17::2
PING6(56=4088 bytes) 2001:4830:1700:18::2 --> 2001:4830:1200:17::2
It'd be nice if Apple had a technote or a preference somewhere...
Mac mini Mac OS X (10.4.6)
Mac mini Mac OS X (10.4.6)

If i recall the message is about DirectPlay?
When i installed and ran pse 12 on windows 8.1, windows offered to turn that on.
You might have to go to the Control Panel>Programs>Programs and Features>Turn Windows Features on or off>Legacy Componets>DirectPlay

Weblogic.security.acl.internal.AuthenticatedSubject not resolved

Hi guys,
when I try to implement that code:
CallbackHandler handler = new URLCallbackHandler(username,
password);
Subject mySubject =
weblogic.security.services.Authentication.login(handler);
weblogic.servlet.security.ServletAuthentication.runAs(mySubject, request);
// Where request is the httpservletrequest object.
in my servlet I get that issue in workshop 9.2:
The type weblogic.security.acl.internal.AuthenticatedSubject cannot be resolved. It is indirectly
referenced from required .class files
Any idea??
Thanks a lot
L.

solved!
simply import weblogic.jar in the project

DNS not resolving on the server - resolves fine on the LAN

Hello all - I just had an odd experience and I thought I'd share it, hopefully gathering some comments.
I performed a fresh install of Tiger Server on my PowerMac last night, with the intention of testing the installer's ability to set up services, particularly Open Directory.
I enabled DNS, AFP, and Open Directory in the installer (first boot after install). The server configured itself and when I logged into admin for the first time I went to Server Admin, where I found DNS, AFP, and Open Directory running. This suprised me as Open Directory was always a bear to get Kerberos running correctly, and here I found Kerberos was running even though there were no entries in DNS.
I went about configuring the rest of my services, DHCP, NAT, Firewall, and so on. When I finally open Workgroup Manager to add some OD users, I find I cannot create home folders. I head to Terminal where I find this:
server:/ admin$ host 10.1.1.1
Host 1.1.1.10.in-addr.arpa not found: 3(NXDOMAIN)
server:/ admin$ host server.ishcabittle.private
Host server.ishcabittle.private not found: 3(NXDOMAIN)
The server cannot see itself for some reason. I had set up a nameserver, server.ishcabittle.private residing on the router address of 10.1.1.1 in my local subnet. I made sure that the DNS server 10.1.1.1 was listed on my subnet's ethernet interface, Built-in Ethernet.
host -v 10.1.1.1 returns the same, only listing a Comcast server for some reason. My guess is that setting up DNS during install hard wired the comcast DNS server as the permanent nameserver. I've edited /etc/hosts to include 10.1.1.1 server.ishcabittle.private, I've edited hostconfig to include HOST=server.ishcabittle.private (although I've read that 10.4.6-7 doesn't need this entry, it was the only thing that got Kerberos running on my previous install). Not sure what else to do.
Is there a permanent DNS record established during install? If so, where can I find this config file? None of these contain what I'm looking for:
/private/etc/.hostconfig.swp
/private/etc/hostconfig
/private/etc/hostconfig.personal
/private/etc/hosts
/private/etc/hosts.equiv
/private/etc/hosts.lpd
I'm pretty much going to reinstall anyway, I'll most likey do so without the cable modem plugged in.

Thanks Leif. I managed to get most things working as you'd expect, except that I am uncertain about the setup when it comes to Open Directory. The DNS I setup on my server maps the WAN IP to the server name, so OD ends up on the WAN IP. Is this not a security concern?
I have DHCP working for the LAN side on the secondary ethernet port, which means all of my clients are on a different subnet from the OD. Also, my DNS is setup on the WAN IP and not the LAN IP, so there is no DNS to nicely set names to IPs for the LAN side. I did try setting up another zone for the LAN side, but then I received some sort of mis-match error (can't recall if it was from OD or changeip or what) - something about the machine handling two different IPs each with a unique name.
At one point I had shared folders working (broken now, ugh) and an account under Workgroup Manager showed this under Account Summary:
Location: WAN-IP/LDAPv3/127.0.0.1
Home: afp://LAN-IP/Users/username
Maybe this is nothing unusual, but I am new to this so apologies if this is obvious. I was under the impression DNS, DHCP, and OD should be running only on the LAN side, but I have not been able to do this because OD must run on the primary interface (which connects to the WAN). It just seems a bit odd to me that I would be running a DNS on a WAN IP when all I really need is a DNS for the LAN side ... is this just a limitation caused by the primary interface needing to be the WAN interface and the OD IP?
Would kindly appreciate a clarification on this.
Thank you!
Update: the following post is very similar to my question, but remained unresolved:
http://lists.apple.com/archives/Macos-x-server/2006/Mar/msg01463.html
In my situation, I would like VPN to work as well, which seems to require OD on the primary interface as well - again, which places my LAN clients on a different subnet from the OD...

DNS not resolving on local network

When I initally set up the server I could go to ktecserver.ktec.us and it would resolve and let me access the server, now the only way to do it is to use ktecserver.local (which sometimes works) but mostly I am stuck with using the IP address of the server to get to it. I have the server as the default dns server for the client computers but it doesn't seem to work. I don't know what has changed or where I need to look to try and troubleshoot this.
Also I want to set it up so people can go to something like x.ktec.us and get to specific services on my mac. One thing I don't know about is security, I'm very hesitent to expose any of my server to the internet because I don't know how to properly log/defend against attacks and intrusions, any advice would be great.
Thanks
Message was edited by: TimThor

You want LAN DNS working, then you want public DNS working.
I'm using an airport extreme as a router (so I guess NAT firewall ;P ) and the VPN service on the server.
I am well aware of what you are running, of your configuration goals and current set-up, with the various issues and discussions around VPN pass-through (in general and with the Apple devices specifically, and often around L2TP pass-through), and that this configuration is a frequent topic of discussions here in the forums.
Having a VPN-capable firewall makes for a simpler configuration, and also allows you to access various (other) hosts on your LAN when your server is down.
Which logs should I be looking at?
It's usually dig and ping commands to determine what's working and not working with DNS, and not logs. Typical commands include...
$ dig host.example.com
$ dig -x host.ip.address.here
$ ping host.example.com
$ traceroute host.example.com
You're looking to determine if the forward and reverse DNS translations work, and if they match, and if you can ping the host, and then (potentially) what the IP route to the host might be.
Also why would it just quit working, I can verify that the airport extreme is giving out the right DNS server
The address of that DNS server would be the IP address of the DNS server on your LAN, and no ISP DNS servers, correct?
With remote access via VPN, you need have IP routing correct, and this means that both ends of the VPN need to be in different subnets, and it's typical to have issues when the target LAN is in 192.168.0.0/24 or 192.168.0.0/24, and it's common to move NAT'd LANs that you manage out of 192.168.0.0/16 and into a subnet somewhere in the 172.16.0.0/12 or 10.0.0.0/8 blocks.
You can also try forcing all traffic onto the VPN as a test. That's an option on the VPN set-up.

Cloud Service Site Url DNS not resolving

I have a site published to Azure Cloud Services that is running, and accessible via VIP. I cannot access the site via Site Url, even after flushing my local dns, or trying on different devices. In my browser's debugger, I see that DNS resolution
fails in the first step of the web request.
I am relying on the site url for CNAME records - I cannot use the VIP.
What would be causing this? What can I do about it?
Also - if I run whatsmydns.net to query CNAMEs against the cloudapp.net address, I get nothing, but A records are resolving to the VIP.

Hello,
Did your make sure your CNAME is valid? I suggest you could use some DNS tool to query it and check it.
If your dns name is valid, I suggest you could follow tutorial (http://www.windowsazure.com/en-us/develop/net/common-tasks/custom-dns/ ) to step by step.
Please try it.
Any question, please let me know.
Thanks.
Will
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Cisco Linksys RE1000 extender is not recognized

My Actiontec Model GT784WNV (from Verizon) does not recognize the Linksys RE1000 range extender - any ideas?

Most Linksys products have the recessed reset button to reset devices to factory defaults.
Set the extenders Static IP information first before completing the wireless configuration. That way you can login on the extend using that IP after it's initial configuration.
Make sure the router sees the extender at about 70% signal strength. You don't want the extender to have too weak or strong a signal.
Please remember to Kudo those that help you.
Linksys
Communities Technical Support

New Cisco Linksys e4200 internal DNS not resolving

Similar Messages

Maybe you are looking for