DNS Lookup for DHCP-assigned devices

Hi!
I expected that my router would be able to act as a DNS server to allow machines on my network to look up the IP addresses of other machines on my network, given that every machine on my network gets its IP address from the router via DHCP - but the router doesn't appear to be capable of that.
The router in question is a Linksys E2000 device, and it has the latest firmware revision installed (1.0.03 build 2Sep 7, 2010).
So, the questions I have are:
1. Can this router act as a DNS server?
2. If the answer to (1) is "yes", then how should it be configured?
Mike

Name resolution in LANs in Windows happens usually based on broadcasts in a workgroup or homegroup and that's generally the best way to do it. Some routers add DHCP entries to the DNS proxy but you can read about a lot of issues with that either, in particular if the DNS proxy information gets incorrect somehow and the DNS resolution is configured with precedence to LAN name resolution...
I would suggest you make sure your LAN name resolution is working properly.

Similar Messages

  • Constant dns lookups for non-existent addresses

    Hi. I'm connected to a large network and I've noticed
    that there are constant dns lookups for addresses that
    do not exist.
    When i run tcpdump, almost every second
    I see a few requests to the dns server from my IP. And all
    of them get the response NXDOMAIN.
    Is there a reason this should happen or is there something
    not working properly on my computer?
    Thanks
    Last edited by m00nblade (2010-01-25 21:42:23)

    It all depends on your setup.
    If you use only local mail domains, just make sure you do not have a catchall address (luser_relay) and messages to unknown users will not be accepted by Postfix in the first place.
    If you use virtual mail domain, you will need to change your setup as Apple's default setup will always accept mail for unknown users and then bounce it back to sender. See here for a how to: Making Virtual Mail Users in OS X 10.4/10.5 Server
    HTH,
    Alex

  • Push Notifications: DNS Lookup for pubsub.localhost failed

    Hello,
    after a server crash and restore i cant manage to get push notifications back working. When adding a caldav account to ical, it doesnt offer "Push" in "Refresh Calendars" option anymore. Everything in the log files seems to look fine but this:
    6/4/12 11:45:26.024 AM jabberd_notification/s2s: dns lookup for pubsub.localhost failed
    Can someone help me out on this please?

    Some more info. I think its just the last line which fails. Everything else looks like it works…
    DNS seems fine as well.
    6/4/12 5:32:37.179 PM jabberd_notification/c2s: [8] [::ffff:127.0.0.1, port=50810] connect
    6/4/12 5:32:37.217 PM jabberd_notification/c2s: Authentication succeeded, mech: DIGEST-MD5 client IP: ::ffff:127.0.0.1 client port: 50810 username: com.apple.notificationuser
    6/4/12 5:32:37.219 PM jabberd_notification/c2s: [8] SASL authentication succeeded: mechanism=DIGEST-MD5; authzid=com.apple.notificationuser@localhost, TLS negotiated
    6/4/12 5:32:37.223 PM jabberd_notification/c2s: [8] bound: jid=com.apple.notificationuser@localhost/icalserver.3c311a83d7b04f1a977481cfea6 c8d9e
    6/4/12 5:32:37.224 PM jabberd_notification/sm: session started: jid=com.apple.notificationuser@localhost/icalserver.3c311a83d7b04f1a977481cfea6 c8d9e
    6/4/12 5:32:37.233 PM jabberd_notification/s2s: dns lookup for pubsub.localhost failed

  • DNS lookup behaviour of cisco devices

    Hi All,
    Does anyone know how routers and ASA's deal with dns lookups for hostnames in their configuration?
    For instance, an NTP server (0.pool.ntp.org), or a hostname in a VPN tunnel configuration.
    I get the impression that there is only a 1 time resolve happening.
    Can anyone confirm this and if this is the case, does anyone know how to modify this behaviour....
    Thanks in advance.

    Hi,
    Cisco routers can be set up as proxy-dns but with a lot of limitations but ASA can't so on the ASA you must enter static host commands which stay indefinitely.
    I don' t know if it's possible to tune the cache timeout and what is the default value.
    Here is the link descibing the caveats for IOS:
    http://nil.si/ipcorner/RouterDNS/
    Regards.
    Alain.

  • GWIA doing DNS lookup for local address

    Hello,
    I am running GW8.0.2 on Netware 6.5sp8. I have a server that our recreation department uses to send out confirmation emails when a customer signs up for a class. The recreation server and the GWIA are on the same subnet.
    Here's the problem: When the Rec server sends out the first email confirmation, it gets sent out successfully. Subsequent emails after that fail. After about twenty minutes the next email will go out OK again but subsequent emails will fail.
    The verbose logs on the GWIA don't tell me much but the diagnostic logs show what looks like a reverse DNS lookup happening at the GWIA for my local IP address of 10.0.0.3 (the Rec server). This reverse DNS lookup fails (probably a timeout) and subsequent emails from this local Rec server get dropped by the GWIA without the DNS lookup.
    DNS is being done by DNS proxy on Bordermanager 9.2. I've bypassed the Bordermanager DNS and the same thing happens. I've made entries for the local Rec server into a route.cfg file but the GWIA seems to want to ignore these entries and keeps doing the DNS lookup.
    The wierdest part of the puzzle is that if I restart the proxy on the Bordermanager the next email will go out with, of course, subsequent emails failing. I've looked at the proxy dns cache and can't even find an entry for my Rec server.
    Attached are the entries from the Diagnostic logs of the GWIA. Novell tech support has assured me that the GWIA and the BM are working fine. I am also having this problem with a scanner that scans then emails but all other email and Bordermanager are functioning fine. This server and scanner were not having this problem before upgrading to GW8.0.2.
    I don't understand why GWIA is doing DNS lookups for a local address and I don't know what I can do to stop it. Any help would be greatly appreciated.
    This is a successful transfer right after restarting the proxy: 10.0.0.3 is the Rec server, 10.0.0.130 is the GWIA and 10.0.0.1 is the Bordermanager.
    16:04:13 D15 NgwResQuery(3.0.0.10.in-addr.arpa, 1, 12)
    16:04:13 D15 Querying server (# 1) address = 10.0.0.1
    16:04:13 D15 HEADER:
    16:04:13 D15 opcode = QUERY, id = 17615, rcode = SERVFAIL, flags: qr aa rd
    16:04:13 D15 query = 1, answer = 0, authority = 0, additional = 0
    16:04:13 D15
    16:04:13 D15 QUESTIONS:
    16:04:13 D15 3.0.0.10.in-addr.arpa, type = PTR, class = IN
    16:04:13 D15
    16:04:13 D15 rcode = 2, ancount=0
    16:04:13 D15 NgwResQuery failed
    16:04:13 D15 DMN: MSG 2000909 Accepted connection: [10.0.0.3] ()
    16:04:13 D15 Successful login with client/server access: 10.0.0.130:1677
    16:04:13 D15 DMN: MSG 2000909 Receiving file: ECMAIL/SYS:\PROGRAMS\GRPWISE\WPGATE\GWIA\3RD\receive\df30 fad4.221
    16:04:13 D15 DMN: MSG 2000909 SMTP session ended: [10.0.0.3] ()
    This is an unsuccessful transfer:
    16:06:08 D04 timeout
    16:06:08 D04 NgwResQuery: send error
    16:06:08 D04 NgwResQuery failed
    16:06:08 D04 DMN: MSG 2000933 Accepted connection: [10.0.0.3] ()
    16:06:08 D04 DMN: MSG 2000933 SMTP session ended: [10.0.0.3] ()
    Then the successful email comes back into the system:
    16:06:26 AA8 MSG 2000909 Processing inbound message: ECMAIL/SYS:\PROGRAMS\GRPWISE\WPGATE\GWIA\receive\DF30FAD4 .221
    16:06:26 AA8 MSG 2000909 Sender: [email protected]
    16:06:26 AA8 MSG 2000909 Recipient: [email protected]
    16:06:26 AA8 MSG 2000909 Queuing to MTA
    16:06:26 AA8 MSG 2000909 File: ECMAIL/SYS:\PROGRAMS\GRPWISE\WPGATE\GWIA\wpcsin\4\4daf048 2.8m1 Message Id: (4DAF66F2.B67:244:35687) Size: 163.3 Kb

    Thanks Massimo. I could have swore I already did that but when I did it again just to make sure it solved the problem. Appreciate the help. Have a good one.
    Originally Posted by mrosen
    On 02.05.2011 21:06, avanrav wrote:
    >
    > Hello,
    >
    > I am running GW8.0.2 on Netware 6.5sp8. I have a server that our
    > recreation department uses to send out confirmation emails when a
    > customer signs up for a class. The recreation server and the GWIA are on
    > the same subnet.
    >
    > Here's the problem: When the Rec server sends out the first email
    > confirmation, it gets sent out successfully. Subsequent emails after
    > that fail. After about twenty minutes the next email will go out OK
    > again but subsequent emails will fail.
    >
    > The verbose logs on the GWIA don't tell me much but the diagnostic logs
    > show what looks like a reverse DNS lookup happening at the GWIA for my
    > local IP address of 10.0.0.3 (the Rec server). This reverse DNS lookup
    > fails (probably a timeout) and subsequent emails from this local Rec
    > server get dropped by the GWIA without the DNS lookup.
    >
    > DNS is being done by DNS proxy on Bordermanager 9.2. I've bypassed the
    > Bordermanager DNS and the same thing happens. I've made entries for the
    > local Rec server into a route.cfg file but the GWIA seems to want to
    > ignore these entries and keeps doing the DNS lookup.
    >
    > The wierdest part of the puzzle is that if I restart the proxy on the
    > Bordermanager the next email will go out with, of course, subsequent
    > emails failing. I've looked at the proxy dns cache and can't even find
    > an entry for my Rec server.
    The reverse DNS done by GWIA is normal, and can't be stopped or tricked.
    That it fails in such odd ways must be a bug with the reverse DNS proxy
    of Bordermanager though. Apparently on the second lookups, it doesn't
    answer in a timely manner (the type of answer is irrelevant, just it
    *has* to answer). Use a different, "real" DNS server for your GWIA.
    CU,
    Massimo Rosen
    Novell Product Support Forum Sysop
    No emails please!
    Untitled Document

  • How do I setup 'local' dns lookups for hostnames using DHCP server on WRT610N?

    Said router with latest firmware has DHCP reservation setup with reserved clients names mapped to specific MAC addresses/IP addresses.  I'd like my clients (a mixture of Mac and W7) to access mapped devices via hostnames and not IP addresses.   I have static IP address provided by my ISP configured on the router with it's corresponding ISP DNS server addresses.  FYI, the DHCP server DNS settings on the router are masked out (can't be changed) on the router and looks to be inherited from the Internet setup (in which I've entered the DNS IP addresses of my ISP's DNS).
    On my clients, nslookup (or equivalent) clearly specify that the DHCP is pumping out the DNS servers from the ISP.  Why would it not look for the reserved client hostnames first?
    I know I can setup local /etc/hosts (or equivalents) or override the DNS and point to the router's IP address on the clients but I'd rather not - that's a lot of maintenance.  I can also setup an internal DNS server, but again, overkill. 
    Is this feature available on this router or am I doing something wrong?  An aging integrated Westell 327W DSL model/router used to be able to provide internal network DNS - but this more modern capable WRT610N router does not?  Thoughts?   Thanks.

    Well its not possible to access the storage driver using the host name.. You can access the storage driver using only the IP address. As the Linksys Router doesn't work on a Host Name.

  • No DNS lookup for MX, A, AAAA or A6?

    Good day folks,
    Does SJS MS 6.2 support querying DNS for MX,A,AAAA or A6 records for the domain specified in the SMTP mail from:<[email protected]>? Exim and sendmail support this measure as a means of reducing spam but I can't find the equivalent for SJS MS 6.2. mailfromdnsverify on the tcp_local channel only sets up verfication of existence of the domain itself.
    Cheers

    Hi Shane,
    Let me take this piece by piece:
    "Really? That's not a feature I've ever actually heard that either of these products have. I can't imagine how it might impact performance. Badly, I strongly suspect."
    The following is an extract from the central mail servers' SMTP dialogue with my MS 6.2:
    *** START MESSAGE ***
    This report relates to a message you sent with the following header fields:
    Message-id: <000001c73417$3ddaf380$0100007f@localhost>
    Date: Tue, 09 Jan 2007 12:55:29 -0500
    From: Ethan Edwards <[email protected]>
    To: [email protected]
    Subject: What IS 0EM Software And Why D0 You Care?
    Your message cannot be delivered to the following recipients:
    Recipient address: [email protected]
    Original address: [email protected]
    Reason: Remote SMTP server has rejected address
    Diagnostic code: smtp;553 5.1.8 <[email protected]>... Domain of sender address [email protected] does not exist
    Remote system: dns;centraldnsserver.mycentraldomain.com(TCP|mymailserveripaddress|62084|centralmailserveripaddress|25) (centralmailserver.um.edu.mt ESMTP CSCMAIL/External server ready)
    *** END MESSAGE ***
    "No, if we had to query every server that mail appears to come from, to check the validity of that mail address, we'd never be able to process mail in any quantity. I strongly doubt that any other product does as you suggest, either"
    This kind of checking is done on every message by mail servers running sendmail that host about 500 users.
    "How about SpamAssassin?
    RBL?
    Greylisting?"
    I think that these techniques all get past the SMTP stage - I want better handling at the SMTP stage.
    "If your central systems accept mail addressed to fake users, then that's a configuration error on their part, assuming that they can know all the real users."
    What I intended is that the mail servers reject external, incoming mail from source addresses that include domains that only have SOA records.
    Finally, regarding the blah123.com example: this domain has no SOA record so mailfromdnsverify works in rejecting the incoming e-mail at the SMTP stage. But try these:
    pipex.co.uk
    fstngt.org
    lists.midterme.com
    com.br
    net.my
    Thanks for keeping up this discussion.
    Cheers,
    Etiennen

  • 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..

  • Finding LDAP server names by DNS lookup.

    Hi,
    I'm very new with JNDI and DNS
    We are hardcoding the ldap server name in our configuration to connect to the Active directory, but the requirement is to know the ldap server name dynmaically by querying the DNS server.
    The input given to us are below.
    Dns domain : indbank.is.
    SRV RRecord : ldap.tcp.
    Query dns : ldap.tcp.indbank.is.
    The domain controller should be found by a DNS lookup for the domain, then a DNS for Domain controllers that advertise the service, then try to see if the domain controllers areanswering, and if so choose the one with the fastest answer time (to avoid choosing a domain controller over WAN).
    Kindly help me.I am beginner and some code sample and tip will be welcome. :)
    Thanks in advance.
    Hiubert

    Thanks a lot to All.
    My code is as follows...
    import javax.naming.*;
    import javax.naming.directory.*;
    import java.util.*;
    public class dns1
         public static void main(String[] args)     {
              try {
                   Hashtable env = new Hashtable();
                   env.put("java.naming.factory.initial","com.sun.jndi.dns.DnsContextFactory");
                   env.put("java.naming.provider.url", "dns://indbank.is");
                   DirContext ctx = new InitialDirContext(env);
                   System.out.println("Intial context created...");
                   Attributes attrs = ctx.getAttributes("_ldap._tcp.indbank.is",new String[] {"SRV"});
                   System.out.println("Attributes are been retrieved...");
                   for (NamingEnumeration ae = attrs.getAll();ae.hasMoreElements();)
                        Attribute attr = (Attribute)ae.next();
                        String attrId = attr.getID();
                        System.out.println("Attribute ID retrieved is" + attrId);
                        for (Enumeration vals = attr.getAll();vals.hasMoreElements(); System.out.println(attrId + ": " + vals.nextElement()));
                   ctx.close();
              catch(Exception e)
                   System.err.println("Problem querying DNS: " + e);
                   e.printStackTrace();
    The code runs fine and I get the output as follows
    0 100 389 ib500ad1.indbank.in
    0 100 389 ib500ad2.indbank.in
    I have following questions
    1) Do these servers which are returned are the domain controllers or the ldap servers.?(or both domaincontrollers and ldap server are same)
    2) how to extract the server name alone from this string.
    3) If these two server names are domain controllers then how can I query for a DNS for Domain controllers that advertise the service, then try to see if the domain controllers are answering, and if so choose the one with the fastest answer time (to avoid choosing a domain controller over WAN).
    Thanks in advance.
    -Hiubert

  • HELP! Disabling reverse DNS lookups on client

    Is there a property that can be set to disable the reverse DNS
    lookup for client requests? I read that if reverse lookups are
    no working then client requests can take an extra 15-30 seconds.
    In our environment reverse lookups are not something we can
    count on so we would like to disable them completely. Please let
    me know which property can be set it if any to accomplish this.
    Regards,
    Robert

    Don't we all ;)
    WL 5.1 sp3
    Sol 2.6
    J2 1.2.1_04
    Rich Nill wrote in message <[email protected]>...
    Paul,
    What version of Weblogic are you running? I want to make sure we don'tsuffer
    from the same problem.
    Thanks,
    Rich
    Paul Iter wrote:
    Would this patch have any impact on the problem I described in
    "performance
    degradation PROBLEM"?
    Thanks,
    Paul
    Mark Griffith wrote:
    There is another issue here though, when we print out server ID's we
    call
    java.net.InetAddress.toString() which ends up in a DNS call.
    Contact support they have a one-off patch.
    cheers
    mbg
    In article <[email protected]>, [email protected]
    says...
    Is there a property that can be set to disable the reverse DNS
    lookup for client requests? I read that if reverse lookups are
    no working then client requests can take an extra 15-30 seconds.
    In our environment reverse lookups are not something we can
    count on so we would like to disable them completely. Please let
    me know which property can be set it if any to accomplish this.
    Regards,
    Robert
    ==================================================
    NewsGroup Rant
    ==================================================
    Rant 1.
    The less info you provide about your problem means
    the less we can help you. Try to look at the
    problem from an external perspective and provide
    all the data necessary to put your problem in
    perspective.

  • DHCP dynamic dns updates for Chromebooks fail

    Hi all,
    We're having a bit of a problem here. We have a domain here, domain.local, that has approximately 260 Windows Machines (XP, Win7, various MS Servers) and we also have users that bring in iOS devices, Kindles, Androids and so-forth. The domain controller
    runs dhcp, dns, wsus, and is a file server. We only have a single dhcp server and a single dns server on a Windows Server 2008 R2 box.
    We have a wireless network by Aruba that has three SSID's on it. One is secure, two are firewalled and open. You can ping the chromebooks on either of the wireless networks. the DHCP server works find on all of these.
    We started off getting bad_address entries from the chromebooks when they went on our network back in September. Creating a dhcp lease solved most but not all. We are still getting dozens of entries in the dhcp log that specify bad_address. We have the dhcp
    server testing twice before issuing. Once in a great, great while, we might get something on an Android, but that is it.
    Funny thing is, Chromebooks are being handed IPs (horray) and we can see the leases in the dhcp server. Well that really isnt funny, but what is, dynamic updates to dns are not happening. They exist nowhere in the forward zone or as a reverse pointer.
    Kindles, iOS machines, Androids, Windows machines and everything else work flawlessly.
    So two things... bad_address in the dhcp area and the dhcp dynamic updates are not happening for the Chromebooks.
    Dns is set to "Always dynamically update DNS A and PTR records.
    Discard A & PTR records when lease is deleted is checked.
    Dynamically update DNS A and PTR records for DHCP clients that do not request updates is also checked.
    Name protection is turned off as of today.
    Any Ideas?
    Thanks!
    Steve

    The chromebooks are not joined to the domain. They are not designed to do so.
    DNS Suffix is fine.
    We have intermittent issues with Androids and an occassional iOS device, but never Windows machines.
    Here is part of the log from yesterday. Only two bad_addresses happened today. See what I mean by it's intermittant?
    Thanks!
    Steve
    30,01/30/14,07:17:06,DNS Update Request,192.168.211.1,U39RM11-1.ludlow.local,,,0,6,,AAEBv23zaAWZ4WuK1b2+dVq95TA2xTDStNgPobG8nwaXmPQ=,
    11,01/30/14,07:17:06,Renew,192.168.211.1,U39RM11-1.ludlow.local,E840F2D1CE03,,4190867016,0,,,
    32,01/30/14,07:17:06,DNS Update Successful,192.168.211.1,U39RM11-1.ludlow.local,,,0,6,,AAEBv23zaAWZ4WuK1b2+dVq95TA2xTDStNgPobG8nwaXmPQ=,
    30,01/30/14,07:17:18,DNS Update Request,192.168.233.11,U39Rm33-1.ludlow.local,,,0,6,,AAEB2fUQYqMaWdoe1wsX4MPnUoL9Q8UmymYol1QgzAkw/+Q=,
    11,01/30/14,07:17:18,Renew,192.168.233.11,U39Rm33-1.ludlow.local,E840F2D188E2,,3840093265,0,,,
    32,01/30/14,07:17:18,DNS Update Successful,192.168.233.11,U39Rm33-1.ludlow.local,,,0,6,,AAEB2fUQYqMaWdoe1wsX4MPnUoL9Q8UmymYol1QgzAkw/+Q=,
    15,01/30/14,07:17:28,NACK,10.0.0.3,,D8D1CB46ADFB,,0,6,,,
    30,01/30/14,07:17:31,DNS Update Request,192.168.100.33,Lukes-iPod.ludlow.local,,,0,6,,AAEBPiTHYcRevrOxpOVKf6R0r8Licugdjc6HTsZ8yEKd6i8=,
    10,01/30/14,07:17:31,Assign,192.168.100.33,Lukes-iPod.ludlow.local,D8D1CB46ADFB,,4141094238,0,,,
    32,01/30/14,07:17:31,DNS Update Successful,192.168.100.33,Lukes-iPod.ludlow.local,,,0,6,,AAEBPiTHYcRevrOxpOVKf6R0r8Licugdjc6HTsZ8yEKd6i8=,
    30,01/30/14,07:17:50,DNS Update Request,192.168.100.34,LESPRIM1-LAP.ludlow.local,,,0,6,,AAEBmOdFa4iAE3mwpFO0XztiEQTcpHNF2F80hCx+P33Duxc=,
    10,01/30/14,07:17:50,Assign,192.168.100.34,LESPRIM1-LAP.ludlow.local,705AB6E50F05,,448941972,0,,,
    32,01/30/14,07:17:50,DNS Update Successful,192.168.100.34,LESPRIM1-LAP.ludlow.local,,,0,6,,AAEBmOdFa4iAE3mwpFO0XztiEQTcpHNF2F80hCx+P33Duxc=,
    30,01/30/14,07:17:50,DNS Update Request,192.168.113.141,LESPRIM1-LAP.ludlow.local,,,0,6,,AAEBy8Imjdb3sW/XWuiJ5U/WrxaJQ3BxJCy0NQedJPGa4X0=,
    11,01/30/14,07:17:50,Renew,192.168.113.141,LESPRIM1-LAP.ludlow.local,485D605DE330,,2808232855,0,,,
    32,01/30/14,07:17:50,DNS Update Successful,192.168.113.141,LESPRIM1-LAP.ludlow.local,,,0,6,,AAEBy8Imjdb3sW/XWuiJ5U/WrxaJQ3BxJCy0NQedJPGa4X0=,
    30,01/30/14,07:18:26,DNS Update Request,192.168.200.21,BAD_ADDRESS,,,0,6,,,
    11,01/30/14,07:18:26,Renew,192.168.200.21,,5CF8A169E20C,,2629993613,0,,,
    32,01/30/14,07:18:26,DNS Update Successful,192.168.200.21,BAD_ADDRESS,,,0,6,,,
    13,01/30/14,07:18:28,Conflict,192.168.200.21,BAD_ADDRESS,,,0,6,,,
    15,01/30/14,07:18:29,NACK,10.1.10.36,,245FDFAF76C0,,0,6,,,
    30,01/30/14,07:18:30,DNS Update Request,192.168.200.21,BAD_ADDRESS,,,0,6,,,
    10,01/30/14,07:18:30,Assign,192.168.200.21,,5CF8A169E20C,,1425556505,0,,,
    32,01/30/14,07:18:30,DNS Update Successful,192.168.200.21,BAD_ADDRESS,,,0,6,,,
    15,01/30/14,07:18:33,NACK,10.1.10.36,,245FDFAF76C0,,0,6,,,
    30,01/30/14,07:18:49,DNS Update Request,192.168.226.2,U39Counseling2.ludlow.local,,,0,6,,AAEBoDb2i8cNiTs5s6mi1U4cKX6O6XrNKoeN0nhi48apyko=,
    11,01/30/14,07:18:49,Renew,192.168.226.2,U39Counseling2.ludlow.local,E840F2D1B6AE,,3091400663,0,,,
    32,01/30/14,07:18:49,DNS Update Successful,192.168.226.2,U39Counseling2.ludlow.local,,,0,6,,AAEBoDb2i8cNiTs5s6mi1U4cKX6O6XrNKoeN0nhi48apyko=,
    30,01/30/14,07:18:58,DNS Update Request,192.168.100.20,android-6bb3d55f112e2c78.ludlow.local,,,0,6,,AAEBZ8X3hdJsXWkCTi64DjXKWgzR8VSvxXmR27vdeEmuXFc=,
    10,01/30/14,07:18:58,Assign,192.168.100.20,android-6bb3d55f112e2c78.ludlow.local,10AE60DDC84E,,2713964648,0,,,
    32,01/30/14,07:18:58,DNS Update Successful,192.168.100.20,android-6bb3d55f112e2c78.ludlow.local,,,0,6,,AAEBZ8X3hdJsXWkCTi64DjXKWgzR8VSvxXmR27vdeEmuXFc=,
    30,01/30/14,07:18:59,DNS Update Request,192.168.200.68,U39CB68,,,0,6,,,
    11,01/30/14,07:18:59,Renew,192.168.200.68,,6021C0E66497,,2944142942,0,,,
    32,01/30/14,07:18:59,DNS Update Successful,192.168.200.68,U39CB68,,,0,6,,,
    13,01/30/14,07:19:01,Conflict,192.168.200.68,BAD_ADDRESS,,,0,6,,,
    30,01/30/14,07:19:03,DNS Update Request,192.168.100.10,Noahs-Ipod.ludlow.local,,,0,6,,AAEBcMLcZNAQkNiPzr+WDzQUzKRHAQQ40R5Qs/XW2OBsCfg=,
    10,01/30/14,07:19:03,Assign,192.168.100.10,Noahs-Ipod.ludlow.local,848506E9BCF0,,1755798843,0,,,
    32,01/30/14,07:19:03,DNS Update Successful,192.168.100.10,Noahs-Ipod.ludlow.local,,,0,6,,AAEBcMLcZNAQkNiPzr+WDzQUzKRHAQQ40R5Qs/XW2OBsCfg=,
    30,01/30/14,07:19:03,DNS Update Request,192.168.117.131,Lisas-iPad-2.ludlow.local,,,0,6,,AAEBigaHvI9zgqVhhK4yfw0UxzAcRD0yLfh0mU5G6Lq33JI=,
    11,01/30/14,07:19:03,Renew,192.168.117.131,Lisas-iPad-2.ludlow.local,A4D1D20EF3A7,,161525253,0,,,
    32,01/30/14,07:19:03,DNS Update Successful,192.168.117.131,Lisas-iPad-2.ludlow.local,,,0,6,,AAEBigaHvI9zgqVhhK4yfw0UxzAcRD0yLfh0mU5G6Lq33JI=,
    30,01/30/14,07:19:04,DNS Update Request,192.168.200.68,BAD_ADDRESS,,,0,6,,,
    10,01/30/14,07:19:04,Assign,192.168.200.68,,6021C0E66497,,734709404,0,,,
    32,01/30/14,07:19:04,DNS Update Successful,192.168.200.68,BAD_ADDRESS,,,0,6,,,
    30,01/30/14,07:19:04,DNS Update Request,192.168.100.10,Noahs-Ipod.ludlow.local,,,0,6,,AAEBcMLcZNAQkNiPzr+WDzQUzKRHAQQ40R5Qs/XW2OBsCfg=,
    11,01/30/14,07:19:04,Renew,192.168.100.10,Noahs-Ipod.ludlow.local,848506E9BCF0,,1755798843,0,,,
    32,01/30/14,07:19:04,DNS Update Successful,192.168.100.10,Noahs-Ipod.ludlow.local,,,0,6,,AAEBcMLcZNAQkNiPzr+WDzQUzKRHAQQ40R5Qs/XW2OBsCfg=,
    30,01/30/14,07:19:21,DNS Update Request,192.168.100.115,Melissas-iPad.ludlow.local,,,0,6,,AAEBWa+Y6U066OotJwgYxsd0r4WlWFbRi23r65syxZ1CSX4=,
    11,01/30/14,07:19:21,Renew,192.168.100.115,Melissas-iPad.ludlow.local,041552B321A4,,1136634598,0,,,
    32,01/30/14,07:19:22,DNS Update Successful,192.168.100.115,Melissas-iPad.ludlow.local,,,0,6,,AAEBWa+Y6U066OotJwgYxsd0r4WlWFbRi23r65syxZ1CSX4=,
    30,01/30/14,07:19:23,DNS Update Request,192.168.200.68,BAD_ADDRESS,,,0,6,,,
    11,01/30/14,07:19:23,Renew,192.168.200.68,,6021C0E66497,,3892725690,0,,,
    32,01/30/14,07:19:23,DNS Update Successful,192.168.200.68,BAD_ADDRESS,,,0,6,,,
    13,01/30/14,07:19:26,Conflict,192.168.200.68,BAD_ADDRESS,,,0,6,,,
    30,01/30/14,07:19:29,DNS Update Request,192.168.200.68,BAD_ADDRESS,,,0,6,,,
    10,01/30/14,07:19:29,Assign,192.168.200.68,,6021C0E66497,,3507239814,0,,,
    32,01/30/14,07:19:29,DNS Update Successful,192.168.200.68,BAD_ADDRESS,,,0,6,,,
    30,01/30/14,07:19:33,DNS Update Request,192.168.100.10,Noahs-Ipod.ludlow.local,,,0,6,,AAEBcMLcZNAQkNiPzr+WDzQUzKRHAQQ40R5Qs/XW2OBsCfg=,
    11,01/30/14,07:19:33,Renew,192.168.100.10,Noahs-Ipod.ludlow.local,848506E9BCF0,,1772576059,0,,,
    32,01/30/14,07:19:33,DNS Update Successful,192.168.100.10,Noahs-Ipod.ludlow.local,,,0,6,,AAEBcMLcZNAQkNiPzr+WDzQUzKRHAQQ40R5Qs/XW2OBsCfg=,
    30,01/30/14,07:19:36,DNS Update Request,192.168.100.35,iDevices-iPod.ludlow.local,,,0,6,,AAEBFRqIzdXCu9pqShdi5/lq7LLN+pI7v0tCInwVnlPW1zw=,
    10,01/30/14,07:19:36,Assign,192.168.100.35,iDevices-iPod.ludlow.local,D8D1CB0C4B3C,,1043927758,0,,,
    32,01/30/14,07:19:36,DNS Update Successful,192.168.100.35,iDevices-iPod.ludlow.local,,,0,6,,AAEBFRqIzdXCu9pqShdi5/lq7LLN+pI7v0tCInwVnlPW1zw=,
    30,01/30/14,07:19:37,DNS Update Request,192.168.100.35,iDevices-iPod.ludlow.local,,,0,6,,AAEBFRqIzdXCu9pqShdi5/lq7LLN+pI7v0tCInwVnlPW1zw=,
    11,01/30/14,07:19:37,Renew,192.168.100.35,iDevices-iPod.ludlow.local,D8D1CB0C4B3C,,1043927758,0,,,
    32,01/30/14,07:19:37,DNS Update Successful,192.168.100.35,iDevices-iPod.ludlow.local,,,0,6,,AAEBFRqIzdXCu9pqShdi5/lq7LLN+pI7v0tCInwVnlPW1zw=,
    30,01/30/14,07:19:38,DNS Update Request,192.168.211.1,U39RM11-1.ludlow.local,,,0,6,,AAEBv23zaAWZ4WuK1b2+dVq95TA2xTDStNgPobG8nwaXmPQ=,
    11,01/30/14,07:19:38,Renew,192.168.211.1,U39RM11-1.ludlow.local,E840F2D1CE03,,3851649786,0,,,
    32,01/30/14,07:19:38,DNS Update Successful,192.168.211.1,U39RM11-1.ludlow.local,,,0,6,,AAEBv23zaAWZ4WuK1b2+dVq95TA2xTDStNgPobG8nwaXmPQ=,
    30,01/30/14,07:20:02,DNS Update Request,192.168.200.21,BAD_ADDRESS,,,0,6,,,
    11,01/30/14,07:20:02,Renew,192.168.200.21,,5CF8A169E20C,,2527289584,0,,,
    32,01/30/14,07:20:02,DNS Update Successful,192.168.200.21,BAD_ADDRESS,,,0,6,,,
    13,01/30/14,07:20:05,Conflict,192.168.200.21,BAD_ADDRESS,,,0,6,,,
    30,01/30/14,07:20:07,DNS Update Request,192.168.200.21,BAD_ADDRESS,,,0,6,,,
    10,01/30/14,07:20:07,Assign,192.168.200.21,,5CF8A169E20C,,2452767822,0,,,
    32,01/30/14,07:20:07,DNS Update Successful,192.168.200.21,BAD_ADDRESS,,,0,6,,,
    30,01/30/14,07:20:15,DNS Update Request,192.168.231.2,U39Rm31-2.ludlow.local,,,0,6,,AAEBfU6IakW2GjJUF9LqGDA6HTGPvTf5uLEg39/xoy27s7Q=,
    11,01/30/14,07:20:15,Renew,192.168.231.2,U39Rm31-2.ludlow.local,0011116E27A9,,2943185667,0,,,
    32,01/30/14,07:20:15,DNS Update Successful,192.168.231.2,U39Rm31-2.ludlow.local,,,0,6,,AAEBfU6IakW2GjJUF9LqGDA6HTGPvTf5uLEg39/xoy27s7Q=,
    30,01/30/14,07:20:15,DNS Update Request,192.168.100.20,android-6bb3d55f112e2c78.ludlow.local,,,0,6,,AAEBZ8X3hdJsXWkCTi64DjXKWgzR8VSvxXmR27vdeEmuXFc=,
    11,01/30/14,07:20:15,Renew,192.168.100.20,android-6bb3d55f112e2c78.ludlow.local,10AE60DDC84E,,3515676649,0,,,
    32,01/30/14,07:20:15,DNS Update Successful,192.168.100.20,android-6bb3d55f112e2c78.ludlow.local,,,0,6,,AAEBZ8X3hdJsXWkCTi64DjXKWgzR8VSvxXmR27vdeEmuXFc=,
    30,01/30/14,07:20:16,DNS Update Request,192.168.200.68,BAD_ADDRESS,,,0,6,,,
    11,01/30/14,07:20:16,Renew,192.168.200.68,,6021C0E66497,,3323928240,0,,,
    32,01/30/14,07:20:16,DNS Update Successful,192.168.200.68,BAD_ADDRESS,,,0,6,,,
    13,01/30/14,07:20:19,Conflict,192.168.200.68,BAD_ADDRESS,,,0,6,,,
    30,01/30/14,07:20:21,DNS Update Request,192.168.200.68,BAD_ADDRESS,,,0,6,,,
    10,01/30/14,07:20:21,Assign,192.168.200.68,,6021C0E66497,,4015370588,0,,,
    32,01/30/14,07:20:21,DNS Update Successful,192.168.200.68,BAD_ADDRESS,,,0,6,,,
    30,01/30/14,07:20:30,DNS Update Request,192.168.107.132,ShonaTrisiPhone.ludlow.local,,,0,6,,AAEBEAQoKj7rtYMVPEaXrk7cnBX90v+WX4e8VWX/LLIlYsQ=,
    11,01/30/14,07:20:30,Renew,192.168.107.132,ShonaTrisiPhone.ludlow.local,8C58779AAE66,,3741452386,0,,,
    32,01/30/14,07:20:30,DNS Update Successful,192.168.107.132,ShonaTrisiPhone.ludlow.local,,,0,6,,AAEBEAQoKj7rtYMVPEaXrk7cnBX90v+WX4e8VWX/LLIlYsQ=,
    30,01/30/14,07:20:37,DNS Update Request,192.168.107.132,ShonaTrisiPhone.ludlow.local,,,0,6,,AAEBEAQoKj7rtYMVPEaXrk7cnBX90v+WX4e8VWX/LLIlYsQ=,
    11,01/30/14,07:20:37,Renew,192.168.107.132,ShonaTrisiPhone.ludlow.local,8C58779AAE66,,3758229602,0,,,
    32,01/30/14,07:20:37,DNS Update Successful,192.168.107.132,ShonaTrisiPhone.ludlow.local,,,0,6,,AAEBEAQoKj7rtYMVPEaXrk7cnBX90v+WX4e8VWX/LLIlYsQ=,
    30,01/30/14,07:20:38,DNS Update Request,192.168.106.131,Martina-ipad2.ludlow.local,,,0,6,,AAEB4JkFG0yi5GATQmXtmGs+xNyzUMvp5CHQ7vC17roJRV8=,
    11,01/30/14,07:20:38,Renew,192.168.106.131,Martina-ipad2.ludlow.local,E0B9BAD88CF4,,743727717,0,,,
    32,01/30/14,07:20:38,DNS Update Successful,192.168.106.131,Martina-ipad2.ludlow.local,,,0,6,,AAEB4JkFG0yi5GATQmXtmGs+xNyzUMvp5CHQ7vC17roJRV8=,
    30,01/30/14,07:21:24,DNS Update Request,192.168.236.10,U39Rm36-1Miel.ludlow.local,,,0,6,,AAEB9phYpXhSho8uUIuhgdv60Mgthppg4Vw9tU1MsxQLUNU=,
    11,01/30/14,07:21:24,Renew,192.168.236.10,U39Rm36-1Miel.ludlow.local,7054D2457626,,2120051083,0,,,
    32,01/30/14,07:21:24,DNS Update Successful,192.168.236.10,U39Rm36-1Miel.ludlow.local,,,0,6,,AAEB9phYpXhSho8uUIuhgdv60Mgthppg4Vw9tU1MsxQLUNU=,
    30,01/30/14,07:21:32,DNS Update Request,192.168.100.4,Haileys-iPad.ludlow.local,,,0,6,,AAEBKB7Xlol/CFyRFfPIXdtUN1OmQ0w/zWeclSXhRX49EuM=,
    11,01/30/14,07:21:32,Renew,192.168.100.4,Haileys-iPad.ludlow.local,ACCF5C2CB6DC,,437817067,0,,,
    32,01/30/14,07:21:32,DNS Update Successful,192.168.100.4,Haileys-iPad.ludlow.local,,,0,6,,AAEBKB7Xlol/CFyRFfPIXdtUN1OmQ0w/zWeclSXhRX49EuM=,
    30,01/30/14,07:21:33,DNS Update Request,192.168.117.131,Lisas-iPad-2.ludlow.local,,,0,6,,AAEBigaHvI9zgqVhhK4yfw0UxzAcRD0yLfh0mU5G6Lq33JI=,
    11,01/30/14,07:21:33,Renew,192.168.117.131,Lisas-iPad-2.ludlow.local,A4D1D20EF3A7,,178302469,0,,,
    32,01/30/14,07:21:33,DNS Update Successful,192.168.117.131,Lisas-iPad-2.ludlow.local,,,0,6,,AAEBigaHvI9zgqVhhK4yfw0UxzAcRD0yLfh0mU5G6Lq33JI=,
    30,01/30/14,07:21:51,DNS Update Request,192.168.231.3,U39Rm31-3.ludlow.local,,,0,6,,AAEBZLIcMEpmxTb3TnhGsNRxgdLLmJ3biPg8dRuPqwkG0EE=,
    11,01/30/14,07:21:51,Renew,192.168.231.3,U39Rm31-3.ludlow.local,001CC06D271A,,647858421,0,,,
    32,01/30/14,07:21:51,DNS Update Successful,192.168.231.3,U39Rm31-3.ludlow.local,,,0,6,,AAEBZLIcMEpmxTb3TnhGsNRxgdLLmJ3biPg8dRuPqwkG0EE=,
    30,01/30/14,07:21:57,DNS Update Request,192.168.231.4,U39Rm31-4.ludlow.local,,,0,6,,AAEB8jeDfIgZt/5EtAnoDCaYlU2UDndCxbY6+F8Q8jhcwZk=,
    11,01/30/14,07:21:57,Renew,192.168.231.4,U39Rm31-4.ludlow.local,001CC06D2722,,1511683688,0,,,
    32,01/30/14,07:21:57,DNS Update Successful,192.168.231.4,U39Rm31-4.ludlow.local,,,0,6,,AAEB8jeDfIgZt/5EtAnoDCaYlU2UDndCxbY6+F8Q8jhcwZk=,
    30,01/30/14,07:21:59,DNS Update Request,192.168.102.1,LESKinder1.ludlow.local,,,0,6,,AAEBp2ylbEUqDPc66pqOvwGle4wCK2aPj7j68lVBh0Uz+HY=,
    11,01/30/14,07:21:59,Renew,192.168.102.1,LESKinder1.ludlow.local,001320782CA2,,3119110832,0,,,

  • DNS record ownership for DHCP clients

    my configuration:
    dhcp/dns/dc installed on same system - Windows 2008 R2 SP1 in domain environment.
    all zones configured to secure updates only with aging and scavenging enabled
    dhcp servers are member of DNSupdateproxy group.
    dhcp are configured with standard domain user account (this user was made a member of dnsupdateproxy as well, DOES THAT MATTER?)
    dhcp scopes are configured with default DNS setup (force DNS update by DHCP)
    now...
    all DNS records for endpoint devices on dhcp lease (windows7, mac os X, ubuntu) are owned by SYSTEM
    in security tab for some DNS records i can see service account with write permission to record ( i believe this is desired state)
    in other records service account has no permission but timestamps are still updated by computer account (hostname$ has write permission). these records have pencil icon on computers in dhcp lease table.
    Problem with this (hostname$ has write permissions) is when user connect to network via VPN (obtains dhcp lease) it get's two records registered in DNS -> 1 record for ip distributed by dhcp server and 2nd record for his home private network.
    Have anyone seen this before?
    i've tried deleting DNS records / releasing ip on endpoint device (example win7). It would not register to DNS by DHCP. However if i do ipconfig /registerdns it will do it, but dhcp service account won't have permission no this record.

    Apparently it appears that DHCP may not be configured with credentials, DHCP DNS settings are not configured to force DHCP to register ALL requests, nor has the DHCP server itself have been added to the DnsUpdateProxy group. These are all prerequisites
    for DHCP to own all records, otherwise you will see default behavior, which is:
    By default, a Windows 2000 and newer statically configured machines will
    register their A record (hostname) and PTR (reverse entry) into DNS.
    If set to DHCP, a Windows 2000 or newer machine will request DHCP to allow
    the machine itself to register its own A record, but DHCP will register its PTR
    (reverse entry) record.
    The entity that registers the record in DNS, owns the record.
    In summary:
    Configure DHCP Credentials. The credentials only need to be a plain-Jane, non-administrator, user account. Give it a really strong password.
    Set DHCP properties, DNS tab, to update everything, whether the clients can or cannot.
    Add the DHCP server(s) to the Active Directory, Built-In DnsUpdateProxy security group.
    Make sure ALL other non-DHCP servers are NOT in the DnsUpdateProxy group. For example, some believe that the DNS servers or other DCs not running DHCP should be in it. They must be removed or it won't work.
    On Windows 2008 R2 or newer, DISABLE Name Protection.
    If DHCP is co-located on a Windows 2008 R2 or Windows 2012 DC, you can and must secure the DnsUpdateProxy group by running the following:
    dnscmd /config /OpenAclOnProxyUpdates 0
    Configure Scavenging one one DNS server. Set the NOREFRESH and REFRESH values combined to be equal or greater than the DHCP Lease length. What it scavenges will replicate to others anyway.
    DHCP Service Configuration, Dynamic DNS Updates, Scavenging, Static Entries, Timestamps, DnsUpdateProxy Group, DHCP Credentials, prevent duplicate DNS records, DHCP has a "pen" icon, and more...
    Published by Ace Fekay, MCT, MVP DS on Aug 20, 2009 at 10:36 AM  3758  2 
    http://msmvps.com/blogs/acefekay/archive/2009/08/20/dhcp-dynamic-dns-updates-scavenging-static-entries-amp-timestamps-and-the-dnsproxyupdate-group.aspx 
    Good summary:
    How Dynamic DNS behaves with multiple DHCP servers on the same Domain?
    http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/e9d13327-ee75-4622-a3c7-459554319a27
    DNS Record Ownership and the DnsUpdateProxy Group
     http://technet.microsoft.com/en-us/library/dd334715(v=ws.10).aspx
    DNS Record Ownership and the DnsUpdateProxy Group
    "... to protect against unsecured records or to permit members of the DnsUpdateProxy group to register records in zones that allow only secured dynamic updates, you must create a dedicated (NON-ADMIN) user account and
    configure DHCP servers to perform DNS dynamic updates with the credentials of this account (user name, password, and domain). Multiple DHCP servers can use the credentials of one dedicated user account."
    http://technet.microsoft.com/en-us/library/dd334715(WS.10).aspx
    DNS record ownership and the DnsUpdateProxy group
    http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/b17c798c-c4b2-4624-926c-4d2676e68279/
    Ace Fekay
    MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/
    This post is provided AS-IS with no warranties or guarantees and confers no rights.

  • Finding DHCP addresses for LAN connected devices

    i am suffering from information overwhelm!
    can anyone tell me how I can find out the DHCP assigned addresses for devices that are connected to my airport extreme via wired connections to the lan?
    i have a voip box connected to the base station and i need to know it's 10.0.1.x address so that i can work with the voip company to check why that box is currently having problems.
    tia for any and all help!
    iMac G5 (PowerPC) & MacBook   Mac OS X (10.4.8)  

    You should be able to choose Logs and Statistics from
    the Base station menu and then choose the DHCP
    clients tab. That will show you all of the DHCP
    leases currently in use.
    It appears that there is a problem displaying DHCP information for wired clients.
    I discovered that if you disable the wireless (I'm only running wired clients), the Logs and Statistics tab only shows "Logs". The other tabs are not even displayed.
    When I turn the Wireless back on, the other tabs re-appear but are empty (no entries). This appears to be a bug that will hopefully be corrected in the next update
    PowerMac G5   Mac OS X (10.4.8)  
    PowerMac G5   Mac OS X (10.4.8)  

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

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

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

  • 9i app 9.0.2.01?Does the reverse DNS lookup have to be set up for a FQDN

    HEy guys:
    I'M ALWAYS GETTING STUCK IN THE SAME PLACE WHEN I AM TRYING TO INSTALL 9I APPSERVER 9.0.2.0.1 REL 2. ITS ALWATYS HAPPENING AT THE oRACLE db CONFIG assistant i have set up my host file and when i ping -a servername i get the full reply back ex. servername.domain.com but now when i ping -a 111.111.111.111 i do not get the host name back this is b/c i do not have the PTR record set up. Do i have to have a reverse dnslookup working for what oracle is stating is "FQDN" and not just the dns lookup working...how is oracle installer looking at this piece.
    that is the only i see that i don't have when i look at my computer name (by the way this is a winnt environment)in properties it has the FQDN. i also have set up the host file correctly resembling 111.111.111.111 servername.domainname.com servername oracleinstall. What else am i missing here guys? thanks for the help in advance
    regards,
    robert

    Actually, these issues were/are documented - see the addendum. Also, the install guide details which files need to be updated with the FQDN/IP.
    Though it does not have to be setup in your DNS server (say if you are just doing it on a single tier to test), those machines which are looking to connect to it would need to have the proper additions to the hosts file as well.
    As for why the 'non-default' http ports, this was a result of Unix security. Non-root users cannot start processes using ports below a specific range. As a result, oracle defaults them to a higher number allowing your oracle account whom lacks root access to start the http service.
    As for non-oracle responses, this isn't really an official forumn. I believe those oracle peeps who do respond here are doing so on their own. If you need official/immediate responses, then i would recommend using metalink for an itar or the metalink forums.
    Now on to Robert's second question. See metalink Note:209114.1: How to Change the Port used for Oracle 9iAS Portal 9.0.x. If you don't have access to metalink, let me know and I can forward the note or post it here.
    Have fun!

Maybe you are looking for