RV042 with DMZ responding to external dns queries

Got a call from my ISP saying that my router was responding to dns requests.
tested with ezdig and it does.
Two rv042, one facing internet, the 2nd in DMZ port. The only public adress answering to dns requests is the Gateway in the dmz.
Firmware bug or i dont understand DMZ ?

Got a call from my ISP saying that my router was responding to dns requests.
tested with ezdig and it does.
Two rv042, one facing internet, the 2nd in DMZ port. The only public adress answering to dns requests is the Gateway in the dmz.
Firmware bug or i dont understand DMZ ?

Similar Messages

  • Cisco 877W acting a a DNS server. Does it answer external DNS queries coming from the WAN

    Hello,
    I have a Cisco 877W running on my ADSL2+ service at home.
    It is setup to act as a DNS server to answer DNS queries for my LAN and has the below commands as part of its configuration
    ip dns server
    ip dhcp pool LAN
       network 192.168.2.0 255.255.255.0
       default-router 192.168.2.254
       dns-server 8.8.8.8
    My question is, when I scan my WAN IP for open ports, port 53 (DNS) is open. Does this mean my router will be acting as a DNS server for anyone on the internet who directs DNS queries to my WAN IP?
    If so, am I able to turn off port 53 towards the Internet, or do I need to add an an access-list to only accept queries from my internal network.
    Thanks for your feedback.

    That's correct. The "ip dns server" command will answer queries on any interface.
    Given that your DHCP server is telling your clients to use Google DNS and not your router, I would just turn the router's DNS server off with the "no ip dns server" command.
    Setting up an ACL (and/or inspection or zone-based firewalling) on your Internet-facing interface is the best practice to protect your network in general, not just to prevent external DNS queries.

  • 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

  • External DNS name with Transversal Firewall

    Have have one server RedHat 4.0 with SGD 4.1 with this names in diferrent
    IP:
    server1.company.com (peer dns name)-> IP1
    server2.company.com (Bind in another IP2 with external dns name and
    firewall forewarding in port 443, the customca is server2.company.com)
    Question:
    Can I configure SGD 4.1 to respond with two external dns name with
    firewall forewarding ?
    https://server1.company.com/tarantella
    https://server1.company.com/sgd
    https://server2.company.com/tarantella
    https://server2.company.com/sgd
    The client user can works with two names ?
    Client prefer to choose access with server1 or server2.
    Best Regard�s
    Marcelo Moreira Martins
    [email protected]
    Technical Consultant - Tarantella Systems Engineer
    SE- Systems Engineer - M3 System Integrator.
    Sun Microsystems do Brasil - Authorized Campus Dealer
    +55-51-3333-2644 - Office
    +55-51-9962-6536 - Mobile Phone
    Visit the EduSoft web site: http://www.sun.com/edu/edusoft/

    Marcelo,
    It is possible to have more that one external DNS name. Please see:
    Array Manager - Array - <server> - General - Properties
    In here you can map ip-addresses (of clients) to dns names.
    However, a user will not be able to dynamically choose which server to
    access - the
    server will be selected on the first matching IP pattern.
    Regards
    "Marcelo M. Martins" <[email protected]> wrote in message
    news:dhu1c0$u5m$[email protected]..
    Have have one server RedHat 4.0 with SGD 4.1 with this names in diferrent
    IP:
    server1.company.com (peer dns name)-> IP1
    server2.company.com (Bind in another IP2 with external dns name and
    firewall forewarding in port 443, the customca is server2.company.com)
    Question:
    Can I configure SGD 4.1 to respond with two external dns name with
    firewall forewarding ?
    https://server1.company.com/tarantella
    https://server1.company.com/sgd
    https://server2.company.com/tarantella
    https://server2.company.com/sgd
    The client user can works with two names ?
    Client prefer to choose access with server1 or server2.
    Best Regard�s
    Marcelo Moreira Martins
    [email protected]
    Technical Consultant - Tarantella Systems Engineer
    SE- Systems Engineer - M3 System Integrator.
    Sun Microsystems do Brasil - Authorized Campus Dealer
    +55-51-3333-2644 - Office
    +55-51-9962-6536 - Mobile Phone
    Visit the EduSoft web site: http://www.sun.com/edu/edusoft/

  • Can't do traceroute or DNS queries withing a non-global zone.

    I'll start by outlining my servers and their roles
    they are all on the same network, behind the same gateway, plugged into the same switch.
    secure1 = a freebsd server running bind. It's a recursive DNS server. works perfectly.
    secure2 = a solaris 10 server.
    zone1 = a zone that was setup before i inherited this env.
    zone2 = a zone i tried to create, and it mostly worked.
    The problem:
    From zone2 I cannot do DNS queries. And traceroutes past the gateway don't work. At first I suspected the firewall, but everything that doesn't work on zone2, works fine on zone 1.
    What does work on zone2
    I can ssh into it
    I can ssh out of it
    I can ping it
    I can ping from it
    I can trace route from it to secure1
    I can ssh to other hosts out on the internet.
    What doesn't work
    I can't do any DNS queries, whether the DNS server is inside of my network or outside of it.
    I can't traceroute past my gateway, tho I can from zone1.
    Finally here's what happens when I do a dns query
    zone2# /usr/sbin/host google.com 66.48.78.91
    ;; connection timed out; no servers could be reached
    Oh, I diffed the zone1.xml and zone2.xml files in /etc/zones and except for things like ip addresses they are the same.
    Any suggestions would be muchly appreciated. Thanks folks.

    ifconfig -a and netstat -rn from the zone that isn't working properly would help.
    Off the top of my head, my guess is that your default route isn't valid for zone 2.

  • External DNS server not replicating records to secondary after migration from 2003 to 2012

    Hi
    I have a query relating to 2012 Server and DNS.
    Last week we de-commissioned our primary external DNS server (Windows 2003 Server) and moved the role over to a new Windows 2012 server.
    Since this point replication to our secondary server (3rd party hosted) does not seem to occur and our DNS records seem to have expired on the secondary server as we cannot look these up via nslookup.
    I cannot see any failures in the event log of the server; I have checked our external firewall logs and nothing is being blocked inbound/ outbound as far as I can see. And the server’s local firewall has been disabled.
    The server is a standalone server in a workgroup with a standard filebased primary zone, with no AD integration and recursion disabled.
    When I created the zone I copied the .dns file from the old server and selected this in the interface during the creation of the zone on the new server.  The new server has the same internal and external IP as the old server and the old server is off-line.
    I have also manually increased the serial number of the zone and still no joy.
    One thing that I have noticed is when I open the zones properties/Name Servers and click edit on the external nameserver I get the infamous "The server with this IP address is not authoritative for the required zone" error.
    Any help Would be appreciated, thanks in advance

    Nice to hear that you are close in finding the problem. So in short:
    You have enabled Zone transfers in DNS management console for the applicable zone
    You have verified that your DNS is listening to the correct interfaces
    You have enabled firewall rules to accept TCP and UDP traffic to port 53
    You have checked if "BIND secondaries" option is applicable to your case
    You have initiated a zone transfer from the secondary server
    Lefteris Karafilis 
    MCSE, MCTS, SEC+ 
    LinkedIn: http://www.linkedin.com/in/lkarafilis 
    Mail: [email protected] 
    Blog: http://www.karafilis.net 

  • DNS - external DNS internal - Domainname?

    Hello, I have the following problem:
    Private IP network (192.168.0.0) behind router, which has a fixed external IP and an ADSL connection.
    The Leo server on the internal network has a fixed IP: 192.168.0.20.
    The Domain Name "firma.com" is hosted on a external provider, there is also a external web server running, which can be and should be accessible under "firma.com" and "www.firma.com".
    I have set up a subdomain in the external provider’s DNS, "intranet.firma.com". This is resolving to the external IP of my router. The router is configured that it routes all requests from the external IP to the internal address "192.168.0.20".
    The Mailxchange (MX) record also redirects on "intranet.firma.com."
    And now the DNS server on the Leo-server? Which are the correct entries?
    IP address: 192.168.0.20
    subnet mask: 255.255.255.0
    router : 192.168.0.1
    Primary DNS: 192.168.0.20
    DNS Secondary: I 192.168.0.1
    Which has to be primary zone name: "firma.com" or "intranet.firma.com"? I mean, can there be "firma.com", when there is a external webserver which needs that name?
    When I use "firma.com" for the Leo DNS and the server’s name is "intranet ", the it resolves to the internal server very well. But how can I get my externally hosted web "firma.com" or "www.firma.com", if I DNS server "firma.com" as the primary zone there? Which is the right configuration that I can send mails internal, external and from external? And use the external webserver as is?
    Thank you
    Willi

    First using a 192.168.0.0/24 or 192.168.1.0/24 network on your LAN is a bad thing if you are going to use VPN later.
    "I have set up a subdomain in the external provider’s DNS, "intranet.firma.com". This is resolving to the external IP of my router. The router is configured that it routes all requests from the external IP to the internal address "192.168.0.20". "
    You can use this if you want but you probably don't want the mail to require a an address like:
    <user/mailaccount-name>@intranet.firma.com do you? The MX pointer can use firma.com with an address of intranet.firma.com:
    firma.com MX 10 intranet.firma.com
    You could also look at intranet(.firma.com) as a hostname instead of a subdomain.
    (Maybe you should use an other domainname internally: firma.private or firma.internal)
    If you want to use the same domainname (firma.com) internally setup "all" the public names/IPs in the internal DNS and use only the server (private IP) DNS (with forwarders to your ISP DNS IPs) not the router DNS proxy for all internal machines.
    If you want to run an intranet webserver why not call it intranet.firma.com and the public one keeps it's name www.firma.com.

  • Setup internal and external DNS namespaces best practice

    Is external name space (e.g. companydomain.com) and internal name space (e.g. corp.companydomain.com or companydomain.local) able to run on the same DNS server (using Microsoft Windows DNS servers)?
    MS said it is highly recommended to use a subdomain to handle internal name space - say corp.companydomain.com if the external namespace is companydomain.com.  How shall this be setup?  Shall I create my ADDS domain as corp.companydomain.com directly
    or companydomain.com then create a subdomain corp?
    Thanks in advanced.
    William Lee
    Honf Kong

    Is external name space (e.g. companydomain.com) and internal name space (e.g. corp.companydomain.com or companydomain.local)
    able to run on the same DNS server (using Microsoft Windows DNS servers)?
    Yes, it is technically feasible. You can have both of them running on the same DNS server(s). Just only your public DNS zone can be published for external resolution.
    MS said it is highly recommended to use a subdomain to handle internal name space - say corp.companydomain.com
    if the external namespace is companydomain.com.  How shall this be setup?  Shall I create my ADDS domain as corp.companydomain.com directly or companydomain.com then create a subdomain corp?
    What is recommended is to avoid having a split-DNS setup (You internal and external DNS names are the same). This is because it introduces extra complexity and confusion when managing it.
    My own recommendation is to use .local for internal zone and .com for external one.
    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Get Active Directory User Last Logon
    Create an Active Directory test domain similar to the production one
    Management of test accounts in an Active Directory production domain - Part I
    Management of test accounts in an Active Directory production domain - Part II
    Management of test accounts in an Active Directory production domain - Part III
    Reset Active Directory user password

  • Applications sending ipv6 dns queries, but ipv6 is disabled

    Hi,
    I had some problems with dns lookups a long time ago and so I followed every hint I could find here in the forums and the wiki, like disabling ipv6, installing dnsmasq, and so on. Firefox and other typical internet applications worked like a charm after that.
    Pacman instead took a long time to lookup the ip for the chosen mirror url, but I didn't bother to look deeper into this issue, until now.
    Wireshark revealed that the dns query that is sent by pacman (and some other console applications like w3m, wget, but not lynx ...) is an AAAA query for an ipv6 address. In spite of ipv6 being disabled.
    Additionally my router (which is added in /etc/resolv.conf) ignores the query, it times out, and after 5 seconds, the AAAA query is sent again.
    This happens 4 times and then a query for the A record is sent which is answered promptly.
    (A simple "w3m google.com" takes up to 1min 20sec with all the lookups following the 301 and 302 answers...)
    Well, a workaround for this is obvious. I could use a nameserver that answers the AAAA query, which I already tried with the opendns server.
    But the question that I have is: Why are some applications sending dns queries for ipv6 addresses although ipv6 is disabled?
    Regards,
    Marc

    Hi,
    I had some problems with dns lookups a long time ago and so I followed every hint I could find here in the forums and the wiki, like disabling ipv6, installing dnsmasq, and so on. Firefox and other typical internet applications worked like a charm after that.
    Pacman instead took a long time to lookup the ip for the chosen mirror url, but I didn't bother to look deeper into this issue, until now.
    Wireshark revealed that the dns query that is sent by pacman (and some other console applications like w3m, wget, but not lynx ...) is an AAAA query for an ipv6 address. In spite of ipv6 being disabled.
    Additionally my router (which is added in /etc/resolv.conf) ignores the query, it times out, and after 5 seconds, the AAAA query is sent again.
    This happens 4 times and then a query for the A record is sent which is answered promptly.
    (A simple "w3m google.com" takes up to 1min 20sec with all the lookups following the 301 and 302 answers...)
    Well, a workaround for this is obvious. I could use a nameserver that answers the AAAA query, which I already tried with the opendns server.
    But the question that I have is: Why are some applications sending dns queries for ipv6 addresses although ipv6 is disabled?
    Regards,
    Marc

  • External DNS zone on Internal DNS servers

    We currently have a 2 domain forest with DNS running on all domain controllers. All domain controllers are 2012 or 2012 R2 and our Domain and forest functional level is set at 2008 R2 due to the existence of an exchange 2003 server which wont be retired
    for several months. We have 2 DNS servers in the root domain and 4 DNS servers in the child domain. This is a centralized DNS setup. Our parent domain is DOMAIN.LOCAL and the child domain is XX.DOMAIN.LOCAL. Externally, our DNS is MYDOMAIN.com. we
    do not have a public facing DNS server and our DNS records are hosted by a 3rd party
    We want to add the MYDOMAIN.COM DNS zone internally (AD Integrated) since we have several instances where applications do not really work well with the XX.DOMAIN.LOCAL DNS. We want this zone to host several DNS records for internal resolution
    only since we do not have any public facing applications or web servers such as SharePoint etc.
    My question(s) is this?
    How is the best way to do this and how will it affect the zones we currently have in place.
    Is it as simple as creating a new forward lookup zone, adding static records?
    How do we (or do we) handle delegation?
    Any information or suggestions to get me started would be greatly appreciated.
    Russ

    Hi,
    I’m not quite understand your question, do you want to create a new primary DNS zone on your current DNS server? If so, you
    just need to create a new primary, you can create the additional primary DNS zone.
    The related KB:
    Configuring a new primary server
    http://technet.microsoft.com/en-us/library/cc776365(v=ws.10).aspx
    Hope this helps.
    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.

  • Leopard server and external DNS issues?

    I am trying to setup a new leopard server for a school with the internet being streamed in from the local borough with filtering for the students via DHCP with a range of 10.x.x.50 - 10.x.x.200. I have all their details (IP, subnet, router) inc their DNS settings. Now I want to create an OD master but am going insane with DNS as the new layout is confusing things. I am using the primary zone name "schoolname.internal" and giving it the manual IP address of the ethernet card 10.X.XX.XXX, I can ping clients around me but the server will not resolve correctly, I am using the external DNS settings provided by the ISP as forwarders.
    I will admit that I am still getting my head around DNS and would really like some more details into how to configure Leopard for this, Why can't I use the internal IP address setting of my server for the DNS?
    Plus do I need to have DHCP running on the server for OD in Leopard if it is being given by the external borough supplier ?

    Ladies and gentlemen, I have the answer.
    I stumbled across this accidentally when I was playing desperately in the Finder trying to get some inspiration about this issue.
    The problem doesn't lie in the clients... it lies in the Server.
    Here is my solution:
    1. In the finder, right-click on the external drive, and select "Get Info".
    2. Under "General", there should be 2 little check boxes, "Shared Folder" and "Locked".
    3. Click on "Shared Folder" to put an X in it.
    Thats it!
    For some reason Time Machine setup didn't share the folder and so the client machines recognised it as a shared time machine backup source, but couldn't actually find it on the network because it wasn't shared.
    Have fun ladies and gentlemen!!

  • WRT54G....Can I set DHCP to use the router for DNS instead of external DNS?

    Hi folks. I cant' get my router to have DHCP tell my PCs that the router should be the DNS server instead of the external servers it is using. I am using Comcast Cable internet. It sets the external DNS servers for every PC that connects to it and I have problems finding my PCs on my network by NetBIOS name because the external DNS servers obviously don't store my local PCs. How can I set the router up to set DHCP to use the router for DNS?

    If you cannot set the DNS server in the configuration page for the DHCP server in your router then your router does not support this.
    This won't solve your problem though. The DNS server on the router is a simply forwarder. It simply forwards the DNS requests from your computer to the ISP's DNS servers. The DNS server does not accept dynamic updates to a private zone inside your LAN. And DNS is pretty much unrelated to the standard windows workgroup browsing which does the actual name resolution inside your LAN. That name resolution even works without a router inside your network. Basically all windows computers in your network periodically broadcast their name to the network. One windows computers is elected "master browser" which collects all these names and provides the name resolution service for all computers in the workgroup.
    If this does not work it is most likely a windows configuration problem. It could be a software firewall on the computers which blocks traffic. It could be that the computers are not setup for file/printer sharing and thus have the computer browser disabled. It could be that your computers have a WINS server configured which does not exist. There are probably more causes. The better source to ask this question would probably a Microsoft support group. They deal with these kinds of issues more often and maybe a MVP may be able to point you into the right direction or give some links to step-by-step instructions...

  • Some CNAME DNS queries fail after latest 10.6.5 update

    Right after rebooting from the latest MacOS X update I noticed some DNS queries are failing. These happen to be DNS queries for CNAME records. Other computers in the same network are not affected by this problem, including Mac's to wich the update was not yet installed.
    Here are the simple diagnostic steps:
    snowboard:~ pmsjt$ nslookup imap.texair.net.
    Server: 192.168.0.14
    Address: 192.168.0.14#53
    imap.texair.net canonical name = taz.warner.local.
    Name: taz.warner.local
    Address: 192.168.0.12
    snowboard:~ pmsjt$ ping imap.texair.net
    ping: cannot resolve imap.texair.net: Unknown host
    snowboard:~ pmsjt$
    snowboard:~ pmsjt$ ping taz.warner.local
    PING taz.warner.local (192.168.0.12): 56 data bytes
    64 bytes from 192.168.0.12: icmp_seq=0 ttl=64 time=2.818 ms
    64 bytes from 192.168.0.12: icmp_seq=1 ttl=64 time=2.211 ms
    64 bytes from 192.168.0.12: icmp_seq=2 ttl=64 time=1.425 ms
    64 bytes from 192.168.0.12: icmp_seq=3 ttl=64 time=2.242 ms
    64 bytes from 192.168.0.12: icmp_seq=4 ttl=64 time=4.882 ms
    64 bytes from 192.168.0.12: icmp_seq=5 ttl=64 time=3.190 ms
    ^C
    --- taz.warner.local ping statistics ---
    6 packets transmitted, 6 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 1.425/2.795/4.882/1.083 ms
    snowboard:~ pmsjt$

    Just as a sanity check, the second portion of the clause from the KB article doesn't apply in your situation, does it?
    Additionally, Mac OS X v10.6 automatically detects when the local network operator has set up a name server that will answer name requests for a domain ending in ".local". It does this by checking to see if there is a Start Of Authority (SOA) record for the top level domain "local", which is how a DNS server indicates that it claims to have authority over a part of the DNS namespace. As long as the DNS server is properly configured with the required SOA record, Mac OS X v10.6 will detect this SOA record and automatically use this server to look up all host names in the domain.
    Also, if you have time, you might want to check what mDNSResponder is actually doing by enabling logging; the man page describes the process in more detail:
    LOGGING
    There are several methods with which to examine mDNSResponder's internal state for debugging and
    diagnostic purposes. The syslog(1) logging levels map as follows:
    Error - Error messages
    Warning - Client-initiated operations
    Notice - Sleep proxy operations
    Info - Informational messages
    By default, only log level Error is logged.
    A SIGUSR1 signal toggles additional logging, with Warning and Notice enabled by default:
    % sudo killall -USR1 mDNSResponder
    Once this logging is enabled, users can additionally use syslog(1) to change the log filter for the
    process. For example, to enable log levels Emergency - Debug:
    % sudo syslog -c mDNSResponder -d
    A SIGUSR2 signal toggles packet logging:
    % sudo killall -USR2 mDNSResponder
    A SIGINFO signal will dump a snapshot summary of the internal state to /var/log/system.log:
    % sudo killall -INFO mDNSResponder
    http://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/ man8/mDNSResponder.8.html
    I suspect in this case packet logging might be most informative.

  • External DNS cache slow to update?

    Hello.
    Is there something in OS X 10.5 Server (which all machines use for their DNS server) that caches external DNS requests? I often find, within our network, external DNS cache is slow to be updated.
    For example, right now, I just moved servers for a project I'm working on (well, I moved it 12 hours ago) and updated the DNS/zone file for it. When I'm outside our network, tracecroutes of the domain point to the new server. But, when I'm within the network, traceroutes still point to the old server.
    The reason I think this has something to do with OS X 10.5 Server is, on the machine I'm sitting at right now, when DNS is set to the IP of the OS X 10.5 Server, external DNS is old (i.e., the traceroute on the domain I've moved still points to the old server). But, if I change the DNS to OpenDNS or Google DNS, the DNS information is new (i.e., the traceroute on the domains I've moved points to the new server).
    Now, on the OS X 10.5 Server, I have "Forwarder IP Addresses" set to OpenDNS server. So, should DNS requests, via the OS X 10.5 Server, not make their way via OpenDNS servers? And if so, why is it that, when going through OS X 10.5 Server, I'm still pulling old DNS information?
    I've:
    - flushed the cache in OS X 10.5 Server (via dscacheutil -flushcache)
    - flushed the cache on the 10.8 client machine (via sudo killall -HUP mDNSResponder)
    - restarted the machines
    Does anyone know what's going on here?
    Thanks,
    Kristin.

    Hi
    If it's any consolation both sites mentioned have always been slow to load for me. Regardless of Service Bandwidth, external/internal DNS, Browser, Platform or Location.
    Occasionally and for no apparent reason they do load as quickly as other sites. Only to return to their usual 'performance' after a short time. There are other sites that perform the same for me which I can't think of at the moment.
    Tony

  • RV042 with Windows VPN Server

    Hi!,
    how do I connect the RV042 with an Windows VPN Server,
    so that the PC's behind the RV042 get the external IP of the VPN and join the VPN-Server's Network.
    I did configure the Windows Server with this tutorial:
    http://blog.lan-tech.ca/2012/01/28/sbs-2011-essentials-configuring-vpn-access/
    I can connect from any device just fine, so the server is running properly. I just need to know how to connect the RV042 to this VPN.
    Kind Regards
    penpenpen

    Dear Customer,
    Thank you for reaching the Small Business Support Community.
    Please refer to the below document, I think it is what you are looking for;
    http://sbkb.cisco.com/CiscoSB/Loginr.aspx?login=1&pid=2&app=search&vw=1&articleid=2957
    Please do not  hesitate to reach me back if there is any further assistance I may help you with.
    Kind regards,
    Jeffrey Rodriguez S. .:|:.:|:.
    Cisco Customer Support Engineer
    *Please rate the Post so other will know when an answer has been found.

Maybe you are looking for