DNS set up when not distributing dns

Ok it's not clear but let me try, I am in a place where they give me an ip address and my domain names come from godaddy and are directed from there. sorry I'm french. Here's my question,
Do I need to setup DNS on leopard server if I want to use all the services, open dir, qtss , podcast producer ect. or since I don't distribute dns, can I not use the dns service.
I'm not sure I expressed my self properly so ask questions if you need to know more.

Do I need to setup DNS on leopard server if I want to use all the services, open dir, qtss , podcast producer ect. or since I don't distribute dns, can I not use the dns service.
If you want to run your own directory service for your clients then you SHOULD run your own DNS server. This is essential if you're setting up your server in a private-class network (e.g. 10.1.x.x or 192.168.x.x) since GoDaddy are not going to be able to resolve your internal hostname(s).
The fact that no external users will ever query your server for DNS lookups doesn't matter - your own machine will and that's what counts.

Similar Messages

  • Airport not distributing DNS servers over network

    Hi everyone,
    I connect to the Internet over ADSL (ISP: Arnet Highway, Buenos Aires, Argentina) using PPPoE from my MacBook Pro.
    I have my ADSL modem connected to the Airport Extreme (802.11n) and distributing IP over DHCP just fine. Every device that joins the network obtains a valid IP.
    However, DNS servers aren't distributed by the router over the network. Every connected device has to be manually configured to set the DNS servers of my ISP to be able to resolve hosts, instead of 'asking' these addresses to the router, as it should be.
    Initially I thought there might be a problem obtainig the DNS servers from the ISP. So in the Airport Utility, in Internet / PPPoE settings, I've manually set my ISP's DNS servers, which should be distributed over the network to all connected devices.
    This doesn't happen, and every somebody new joins my wireless network I have to manually change the DNS servers for that connection which, as I'm sure you'll agree with me, can be quite annoying. Not to mention what would happen if my ISP decides to use dynamic DNS addresses.
    Thanks for any help you might provide.
    Cheers.

    Hello belbo,
    I connect to the Internet over ADSL using PPPoE from my MacBook Pro.
    Is your Macbook Pro Network configured to use PPPoE or DHCP?
    I have my ADSL modem connected to the Airport Extreme (802.11n) and distributing IP over DHCP just fine. Every device that joins the network obtains a valid IP.
    Is NAT enabled on the AE? Are the valid IP Address obtained from your ISP or from the AE?
    However, DNS servers aren't distributed by the router over the network. Every connected device has to be manually configured to set the DNS servers of my ISP to be able to resolve hosts, instead of 'asking' these addresses to the router, as it should be.
    When you setup the AE to use PPPoE did you enter a Domain Name or a DHCP Client ID?
    Initially I thought there might be a problem obtainig the DNS servers from the ISP. So in the Airport Utility, in Internet / PPPoE settings, I've manually set my ISP's DNS servers, which should be distributed over the network to all connected devices.
    The DNS servers listed in the AE aren't distributed to each Network Device but are only used to translate names into IP addresses when need by a Network Device.
    This doesn't happen, and every somebody new joins my wireless network I have to manually change the DNS servers for that connection which, as I'm sure you'll agree with me, can be quite annoying. Not to mention what would happen if my ISP decides to use dynamic DNS addresses.
    If your AE is distributing IP Address using DHCP and NAT then this should not be a problem but I'm not sure without more information about the questions I asked.
    Later.
    Buzz

  • TC set up when not connected to internet/using as a router

    Hi,
    I bought a TC and can't seem to get it to back up at a reasonable speed with an ethernet cable attached to my MBP. I have 180GB to back up, I've been getting 1GB in 3 hours, which is ridiculous, so something must be wrong. My suspicion is it's doing it wirelessly.
    It's not set up as a router because I'm staying with friends and I can't seem to see in the instructions how to set it up to transfer the data by cable. Can anyone suggest how to move forward, I'm just feeling frustrated with it, and I can't have it tied to a desk for 540 days to do a first back up.
    Anyone's assistance would be really appreciated - with the sparks out the back when I first plugged it in - I'm wondering whether I should just send it back... this has not been plug and play so far, but appreciate it not being connected to the net/acting as a router might be complicating things a bit.
    Thanks
    Ben

    Hello benho. Welcome to the Apple Discussions!
    with the sparks out the back when I first plugged it in - I'm wondering whether I should just send it back
    You did power all your networking equipment off before making any connections ... right?
    You can configure the Time Capsule (TC) as either a stand-alone router or to join an existing wireless network in order to perform backups.
    If your Mac has AirPort at the top of the network connections list, it will attempt to connect wirelessly first, and then, move down the list to the next networking option. If you want to "force" your computer to try Ethernet first, just move this option to the top of the list.

  • DNS Set Up system throw as ORA-12154; TNS :could not resolve the connect id

    Hi,
    While i'm creating DNS set up system throws below message
    unable to connect
    SQLState=08004
    DNS Set Up for instantclient(win32-10.2.0.4) system throw as ORA-12154; TNS :could not resolve the connect identified specified.
    operationg system:xp
    dir path:C:\Oracle\instantclient10_2
    TNSNAMES.ORA(C:\Oracle\instantclient10_2\NetWork\ADMIN) Contants
    YourTNSName =sankar
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST =localhost)(PORT =1521))
    (CONNECT_DATA =
    (SID =sankar)
    (SERVER = DEDICATED)
    dir contains:
    sqresus.dll,
    sqresja.dll
    sqoras32.dll
    sqora32.dll
    oraociei10.dll
    oraocci10.dll
    orannzsbb10.dll
    ojdbc14.jar
    ocijdbc10.dll
    ociw32.dll
    oci.dll
    classes12.jar

    user7197586 wrote:
    Hi
    I have been created one DBLink it's created but when i am trying to access the data through the link it's raise error as
    "ORA-12154: TNS:could not resolve the connect identifier specified"
    CREATE
    PUBLIC DATABASE LINK
    Vrd_tcplink
    CONNECT TO
    "SAPVRD"
    IDENTIFIED BY
    "manager123"
    USING
    'VRD_TCP.WORLD'
    created this above dblink
    Kindly Suggest to wau out.
    Regards,
    Sachin
    When using a dblink, the database with the link is acting as a client to the remote database ... exactly like sqlplus running on the db server.
    read: http://edstevensdba.wordpress.com/2011/02/26/ora-12154tns-03505/ ora-12154tns-03505

  • The network path was not found *DNS*

    Hi all,
    Some background... I only have one DC which is running AD and DNS.  I have a file/share server that I want to add to the domain and along with a few workstations.  I was getting an error before this and it was 'dns name does not exist'... but now
    I'm getting 'the network path does not exist' error.  Some items that I changed are for the DC I pointed the DNS to itself by changing the primary DNS to its loopback address (127.0.0.1) and the secondary dns setting is left blank.  For the file/share
    server I changed the primary DNS to the DCs IP address.  The DC does have a forwarder for resolving external addresses that it does not know locally.  
    When I try to add the file server to the domain by entering in the DC admin credentials it just says 'the network path was not found' to the DC and it doesn't give me an error code. I just want to add the server/clients to the domain.
    The file/share server is a windows 2012 r2 and the DC is also windows 2012 r2.  

    Both the DC and file share server are on the same subnet and I checked the logs on the FW and the FW is not seeing the traffic.
    As far as DNS goes do I have it configured correctly.  For the DC I have a static IP and the Primary DNS setting as its loopback address.  The file share server also has a static IP address and the Primary DNS setting is the DCs IP address.
    On the DC there is a yellow exclamation icon on the network icon which says 'no internet access'.  This could be a problem... but when I do nslookup I'm able to resolve names.
    On the DC and File server I have McAfee agent EPO running on it (HIPS and A/V).  I checked the logs on the DC and the only thing being blocked was netbios which I allowed it now but for some reason the logs still show that it is being blocked.

  • Nslookup: DNS request timed out. time out was 2 seconds. (When the primary DNS is down)

    Hi All,
    I have set up 2 Windows Server 2012 domain controllers (DCA & DCB). DCA points at DCB as the primary DNS, and itself as the alternate DNS. DCB points at DCA as the primary DNS, and itself as the alternate DNS.
    When both DCs are running and if I do an nslookup on DCA: The result is as follows:
    Default Server: dcb.testdomain.com
    Address: 30.30.30.2
    nslookup on DCB:
    Default Server: dca.testdomain.com
    Address: 30.30.30.1
    Client PC (Windows 7 Pro):
    1st DNS : 30.30.30.31
    Alternate DNS: 30.30.30.32
    nslookup on the client PC
    Default Server: dca.testdomain.com
    Address: 30.30.30.1
    Up to here everything is fine. Now if I turn off DCA, and do an nslookup, the result is as follows:
    DCB nslookup:
    DNS request timed out.
           time out was 2 seconds.
    Default Server Unknown
    Address: 30.30.30.31
    Client PC nslookup:
    DNS request timed out.
           time out was 2 seconds.
    Default Server Unknown
    Address: 30.30.30.31
    I waited for more than 15 minutes an tried again, it didn't help.
    I have been reading a few similar posts on this matter, but couldn't find the answer.
    I would  expected it to display the DCB when I do an nslookup.
    Question 1: Shouldn't that display DCB rather than displaying a time out message when I do nslookup?
    Question 2: The fact that it displays a time out message, does it mean that more configuration needs to be done? If so please kindly advice what needs to be done. 
    I did an ipconfig /displaydns command. I realized that the order of DNS have changed on both DCB and the Client PC:
    Now, they both display DCB on the top of the list, whereas they were displaying DCA on the top of the list prior to the shut down.
    Question 3: Does it mean that the Client PC now knows that the 1st DNS is down and so it's using the 2nd DNS?
    If so, why does the nslookup display the time out message?
    Question 4: Is it possible to configure either of DNS Server or the DNS client, so it displays the 2nd DNS when the first DNS is not accessible and when I do nslookup?
    Thank you for. 

    Hi Ton_2013,
    Based on my understanding, the issue we are experiencing is that: when the primary DNS server is down, the result of the tool Nslookup is to diaplay the time out message at first. Right?
    Based on my knowledge, timed out message is means that the server did not respond to a request after a certain amount of time and a certain number of retries. Because the primary DNS server is down, it can't respond to this request and time is out. When
    the primary DNS server can't respond, the secondary DNS server works to ensure effective work. And the order is changed as you said.
    As to the reason why the result is still the same even when the order has changed, we can try to use Network Monitor to capture network traffic and view and analyze it to find the cause. And the cause may be the cache. For your information, please refer
    to the following link to download the tool Network Monitor:
    http://www.microsoft.com/en-hk/download/details.aspx?id=4865
    Regards,
    Lany Zhang

  • Windows are not using dns for resolving short hostnames ?

    Hello,
    we are using static DNS records on our company's router and Windows is not trying to resolve hostnames.
    For example on the router is set DNS foo for address
    192.168.2.1
    When I try ping foo from linux machine, it works just fine. But it is not working on Windows, because windows doesn't even try to resolve this kind of "short" hostnames.
    It works when it's changed to foo.foo or when foo is added into hosts file. But adding it on every machine is what I don't want to do.
    Is there a way how to configure Windows to resolve these short hostnames via DNS ? 
    Thanks

    Thanks for your response.
    Yes, windows is using router as it's only dns server. It works fine with longer hostnames (hostname has to have at least two parts). I'll try the other stuff tomorow. I'm already outside the network.
    http://superuser.com/questions/480792/setting-windows-to-resolve-all-hostnames-via-dns-when-not-connected-to-a-domain
    This guy has exactly the same problem, maybe he is explaining it better. Problem is that windows don't even give it a try to resolve the name through dns. Everything works fine from Linux systems.

  • Purge DNS setting on my Mac

    I cannot access my email due to a change on my website. I have been told I need to purge the DNS setting on my mac so that the new settings will then be stored.
    What happened is I had to redirect people accesing my website because my isp doesn't have SQL server. Once the redirection happened I couldn't access my email, from anywhere. On my PC's I "flushed" the DNS settings so the updated setting would be stored. I need to do this on my mac.
    How do I do this?
    Thanks!

    DNS Fundamentals
    The following section will go over DNS fundamentals. A Domain Name Server's primary duty is to take IP addresses and return host names, and vice versa. For example, a computer's IP address of 15.1.1.10 will be converted to 'starfury.zone.com' by the DNS. There are several different types of records that are used with a DNS. The most important is the A-record, which returns an IP address for a host name. The A-record's inverse is the PTR record, which returns a host name for an IP address. The PTR record is a little strange because it is created by reversing the IP address and adding 'in-addr.arpa.' to the end. There is also a CNAME record which is a host name alias to another host, this allows multiple host names to resolve to one IP address. These three record types are illustrated below.
    A-record name -> IP address host.domain.com -> 12.1.8.51
    PTR IP address -> name 51.8.1.12.in-addr.arpa. -> host.domain.com
    CNAME host name alias name.domain.com (A-record name) = othername.domain.com
    The next type of DNS record is only used by SMTP Mail Servers. It is called an MX record, or mail exchanger. An MX-list is used with a host to specify how mail for that host should be delivered. The MX-list contains all the possible mail exchanger hosts along with preference values indicating which host should be the final recipient of mail. A host with a lower number value has higher preference (a host with a value of 10 would be preferred over a host valued at 15). If two hosts have the same preference value, they do load-balancing between them. MX records are best explained by example.
    MX-list record for mail.company.com
    10 mail.company.com
    20 mail-backup.company.com
    30 isp-backup.isp.net
    In this example a mail server attempting to deliver mail to 'mail.company.com' will ask DNS for the MX-list shown here. The server will then try and deliver the mail to the host on the MX-list that has the lowest numerical preference value. In this case it would be 'mail.company.com'. The server will then look up the IP address for 'mail.company.com' and deliver the mail to that address. If that host is not available the mail server will attempt to connect to the next best host, 'mail-backup.company.com'. If 'mail-backup.company.com' is also not available the mail server will then try 'isp-backup.isp.net'. Supposing 'isp-backup.isp.net' was up it would accept the mail and then assume responsibility for forwarding it on to 'mail.company.com' because that host is the preferred final destination for mail addressed to 'mail.company.com'. If all three of these hosts are down the attempting mail server will wait for a while (usually around 5-20 minutes) and try all three again in preference order.
    There is a lot more complexity to DNS than what has been described, but that is enough background information to get started. This next section will describe the ways in which the Apple Mail Server uses DNS to deliver mail.
    How the Apple Mail Server uses DNS
    The Apple Mail Server uses DNS to discover what host names should be considered "local" and to properly deliver mail to other mail servers. Without a DNS available the mail server will be essentially nonfunctional. Many mail delivery problems are the result of a misconfigured DNS server. The Apple Mail Server is designed to use the information returned by DNS to auto-configure itself so that it "knows" what names it can be called by.
    Who am I?
    One of the first things the mail server does when it starts up is determine what its own names are. It will use DNS to look up the PTR record for the server computer's IP address to discover the name or names that goes with it (Example server IP 15.0.0.21 = 'mail.zone.com'). This name will be marked as a "local" host in the host list. The server will also mark any hosts that end up being local when resolved through DNS. If a mail comes in that is addressed to 'alias.zone.com' and this name maps to 'mail.zone.com' using a CNAME record, then it will be marked local as well. MX-list hosts can also become "local" hosts if they point to the same computer, (zone.com MX-list; 5 mail.zone.com 10 nowhere.zone.com) 'zone.com' will be "local". All mail addressed to "local" hosts will be delivered to users in the mail servers Users & Groups list. Any hosts which are not local will need to be contacted for message delivery.
    Server IP address 15.0.0.21
    PTR for 21.0.0.15.in-addr.arpa. -> mail.zone.com
    A-record for mail.zone.com -> 15.0.0.21
    CNAME for mail.zone.com -> alias.zone.com
    MX-list for zone.com
    5 mail.zone.com
    10 nowhere.zone.com
    Local Host Names: mail.zone.com, alias.zone.com, zone.com
    Using MX-lists
    MX-lists are usually used in two ways. (1) Providing an alternative/backup mail server for a host, and (2) mapping a domain wide address to a specific mail server. It is important to have a backup mail server available to handle mail for your domain when your primary mail server goes down. You should configure an MX-list for your host which indicates mail for your mail server 'mail.wigit.com' should be delivered to 'mail.wigit.com' unless it is down, in which case it should be delivered to your backup server, 'mail-backup.wigit.com', or your Internet Service Provider's mail server, 'mail-backup.isp.net'.
    MX-list for mail.wigit.com
    10 mail.wigit.com
    15 mail-backup.wigit.com
    20 mail-backup.isp.net
    The second use for the MX-list is to provide a "shortcut" email address for your mail users. An MX-list can be created for a host that doesn't have an A-record, this is called an MX-only record. It is used to simplify email addresses, instead of having an email address of '[email protected]' you can simply use '[email protected]'. To do this, create an MX-only record which indicates mail for 'wigit.com' should go to 'mail.wigit.com'. You'll also want to include your mail server backups in this MX-list.
    MX-only list for wigit.com
    10 mail.wigit.com
    15 mail-backup.wigit.com
    20 isp-backup.isp.net
    The mail server will also use the MX-list for all outgoing mail. It will look up the MX-list for each host and determine which computer should be contacted to deliver the mail. If the mail server comes across a host that does not have an MX-list it will attempt to connect to the A-record address for that host. The server will also try the A-record address if all hosts on the MX-list are unreachable.

  • How DNS traffic behaves when we have Enterprise Domains configured in RAP-NG(IAP VPN) deployment?

    Q: How DNS traffic behaves when we have Enterprise Domains configured in RAP-NG(IAP VPN) deployment?
    The four modes available in the RAP-NG architecture are
    1.Local mode
    2.Centralized L2 mode
    3.Distributed L2 mode
    4.Distributed L3 mode
    In all the above mode the common behavior is, Internet traffic is source NATed with Master IAPs local IP. The DHCP and corporate traffic behavior changes depending up on mode used in the RAP-NG architecture.
    A: Below is the behavior of the DNS traffic
    By Default all the DNS requests from a client are forwarded to the clients DNS server.
    In a typical IAP deployment without VPN configuration, client DNS requests are resolved by the clients' DNS server. 
    The DNS behavior of an IAP network (SSID/wired port) configured for RAPNG is determined by the enterprise domain settings. 
    The enterprise domain setting on the IAP defines the domains for which the DNS resolution must be forwarded to the clients' default DNS server. 
    Example:
    internal-domains
     domain-name arubanetworks.com
    In the above example if the enterprise domain is configured for arubanetworks.com, then DNS resolution for hostnames in arubanetworks.com will be forwarded to the clients' default DNS server.
    The DNS resolution for rest of all the hostnames domains ex. google.com, yahoo.com etc. will be Scr-NATed to the local DNS server of the IAP.
    If you need to allow all the hostnames domains to be forwarded to the clients' default DNS server we need to use "*" in the enterprise domain configuration
    internal-domains
     domain-name *
    From Web UI:
    To create/ View 
    1. Hit settings
    2. Click on Show advanced options
    3.Select Enterprise Domains
    To View Enterprise domain setting from CLI;
    #show running-config | begin  internal-domains
    To Create Enterprise domain from CLI:
    (config)#internal-domains
     domain-name <domain-name>

  • DNS set properly?

    After all the issues I was having with the server, I decided to do a clean install. This time I have it set as a standalone server until I get the DNS set properly.
    Right now, the way I have my DNS configured is this:
    ^ 0.16.172.in-addr.arpa. - Reverse Zone
    - 172.16.0.100 - Reverse Mapping - server1.markhadjar.com.
    ^ markhadjar.com. - Primary Zone
    - server1 - Machine - 172.16.0.100
    - mail - Machine - 172.16.0.100
    - www - Machine - 172.16.0.100
    highlighting markhadjar.com. shows that my name servers are set as:
    Zone: markhadjar.com.
    Nameserver Hostname: server1.markhadjar.com.
    Is all this correct?
    Running checkip -checkhostname results in:
    Primary Address: 172.16.0.100
    Current Hostname: server1.markhadjar.com
    DNS HostName: server1.markhadjar.com
    The names match. There is nothing to change.
    Traceroute works when using server1.markhadjar.com and 172.16.0.100
    however, when I type in just the domain markhadjar.com it can't find anything. I have reason to believe this is why some of my services before were not working properly.
    Before doing the clean install, I was only able to get Mail and VPN to work. AB/iCal would not work. iChat would only work if I used [email protected] and having the server set to server1.markhadjar.com but it would not work with [email protected]
    Any help would be appreciated!
    THanks

    If you are trying to access your server from your local client machine you need to have the client looking to your server added to the DNS lookup path. Trying to access the server from outside is a whole different story.

  • Could someone who has dns set up correctly confirm that this test works?

    The test that's here http://docs.info.apple.com/article.html?artnum=106798 says if you attempt to visit this link:
    http://17.254.0.91
    and you are taken to Apple's page then you probably don't have your DNS set up correctly.
    Can anyone confirm, who has their DNS set up correctly, that attempting to visit that link does not work for them please?
    TIA

    Right, thanks for that info. I don't understand what all the code stuff is at all, but I do understand this:
    If you type in the link stated and you are taken to Apple’s page then DNS IS SET UP CORRECTLY.
    I'm still confused though. In that article/test in part of its explanation of DNS it says:
    If you encounter some applications that continue to work, it may be because they are set up to go directly to an IP address, bypassing the need for DNS service.
    Surely typing in http://17.254.0.91 into your browser is a way of making your browser access apple's site *bypassing DNS*? -- because you're using the IP address irradicating the need for changing a name into an IP address. The way to test if DNS is working, surely, is to try and access apple's site via www.apple.com? Not http://17.254.0.91.
    Thanks.

  • DNS cache " Name Does not Exist"

    Hey Guys,
    So we've been experiencing a really weird issue related to the DNS for past couple of months. Here are the details:
    1) Our domain machines are Windows 7 Enterprise and their DNS points to Windows DNS Servers
    2) For companyxyz.net internal sites, the Windows DNS resolves those from its
    companyxyz.net zone.
    3) For public *.companyxyz.com records, the Windows DNS has conditional forwarders to point these requests to our Linux Bind Servers. And than the authoritative name servers respond to these queries accordingly
    4) Our internal employees use the public records such as testing.companyxyz.com 
    Problems:
    1) Employees on the internal network would randomly experience page not found on their browsers while trying to hit
    testing.companyxyz.com. When we try to ping this URL, ping would fail too. However, NSLOOKUP would work perfectly fine and return the correct results. ipconfig /flushdns fixes the issue right away
    2) During the time when this problem is occurring, if I look into the local cache ( ipconfig /displaydns), I find an entry saying:
        testing.companyxyz.com
        Name does not exist. 
    ipconfig /flushdns obviously clears out this record along with the other local cached records and fixes the issue.
    3) Point the local computers directly to the Linux Bind servers as DNS never create this issue. It's only when they are pointing to the Windows DNS and going to this public record. The problem also seems to occur a lot more frequently if there are considerably
    high number of hits to this URL.
    Have you guys experienced this issue before? I am looking for a fix for this issue and not having the end-users to flush their dns constantly. Also note this problem occurs sometimes once a day, or 2 -3 times a week. It's very random.
    Thanks.
    Bilal
     

    Hi,
    It seems that the issue is related to your Windows 7 client. Considering whether there is DNS attack or virus on this computer.
    Please try to do the safety scan first.
    Please monitor the DNS server performance referring these article:
    Monitoring DNS server performance
    http://technet.microsoft.com/en-us/library/cc778608(WS.10).aspx
    Monitoring and Troubleshooting DNS
    http://www.tech-faq.com/monitoring-and-troubleshooting-dns.html
    For further step, we need to capture the traffic by using Network monitor when the issue happened and we continuously ping
    testing.companyxyz.com.
    Microsoft Network Monitor 3.4
    http://www.microsoft.com/en-us/download/details.aspx?id=4865
    Let’s see whether there is DNS request happened and the DNS request is handled.
    You can post back the save traffic log here for our further research.
    Kate Li
    TechNet Community Support

  • 2K8 - Best practice for setting the DNS server list on a DC/DNS server for an interface

    We have been referencing the article 
    "DNS: DNS servers on <adapter name> should include their own IP addresses on their interface lists of DNS servers"
    http://technet.microsoft.com/en-us/library/dd378900%28WS.10%29.aspx but there are some parts that are a bit confusing.  In particular is this statement
    "The inclusion of its own IP address in the list of DNS servers improves performance and increases availability of DNS servers. However, if the DNS server is also a domain
    controller and it points only to itself for name resolution, it can become an island and fail to replicate with other domain controllers. For this reason, use caution when configuring the loopback address on an adapter if the server is also a domain controller.
    The loopback address should be configured only as a secondary or tertiary DNS server on a domain controller.”
    The paragraph switches from using the term "its own IP address" to "loopback" address.  This is confusing becasuse technically they are not the same.  Loppback addresses are 127.0.0.1 through 127.255.255.255. The resolution section then
    goes on and adds the "loopback address" 127.0.0.1 to the list of DNS servers for each interface.
    In the past we always setup DCs to use their own IP address as the primary DNS server, not 127.0.0.1.  Based on my experience and reading the article I am under the impression we could use the following setup.
    Primary DNS:  Locally assigned IP of the DC (i.e. 192.168.1.5)
    Secondary DNS: The assigned IP of another DC (i.e. 192.168.1.6)
    Tertiary DNS:  127.0.0.1
    I guess the secondary and tertiary addresses could be swapped based on the article.  Is there a document that provides clearer guidance on how to setup the DNS server list properly on Windows 2008 R2 DC/DNS servers?  I have seen some other discussions
    that talk about the pros and cons of using another DC/DNS as the Primary.  MS should have clear guidance on this somewhere.

    Actually, my suggestion, which seems to be the mostly agreed method, is:
    Primary DNS:  Locally assigned IP of the DC (i.e. 192.168.1.5)
    Secondary DNS: The assigned IP of another DC (i.e. 192.168.1.6)
    Tertiary DNS:  empty
    The tertiary more than likely won't be hit, (besides it being superfluous and the list will reset back to the first one) due to the client side resolver algorithm time out process, as I mentioned earlier. Here's a full explanation on how
    it works and why:
    This article discusses:
    WINS NetBIOS, Browser Service, Disabling NetBIOS, & Direct Hosted SMB (DirectSMB).
    The DNS Client Side Resolver algorithm.
    If one DC or DNS goes down, does a client logon to another DC?
    DNS Forwarders Algorithm and multiple DNS addresses (if you've configured more than one forwarders)
    Client side resolution process chart
    http://msmvps.com/blogs/acefekay/archive/2009/11/29/dns-wins-netbios-amp-the-client-side-resolver-browser-service-disabling-netbios-direct-hosted-smb-directsmb-if-one-dc-is-down-does-a-client-
    logon-to-another-dc-and-dns-forwarders-algorithm.aspx
    DNS
    Client side resolver service
    http://technet.microsoft.com/en-us/library/cc779517.aspx 
    The DNS Client Service Does Not Revert to Using the First Server in the List in Windows XP
    http://support.microsoft.com/kb/320760
    Ace Fekay
    MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
    This posting is provided AS-IS with no warranties or guarantees and confers no rights.
    I agree with this proposed solution as well:
    Primary DNS:  Locally assigned IP of the DC (i.e. 192.168.1.5)
    Secondary DNS: The assigned IP of another DC (i.e. 192.168.1.6)
    Tertiary DNS:  empty
    One thing to note, in this configuration the Best Practice Analyzer will throw the error:
    The network adapter Local Area Connection 2 does not list the loopback IP address as a DNS server, or it is configured as the first entry.
    Even if you add the loopback address as a Tertiary DNS address the error will still appear. The only way I've seen this error eliminated is to add the loopback address as the second entry in DNS, so:
    Primary DNS:  The assigned IP of another DC (i.e. 192.168.1.6)
    Secondary DNS: 127.0.0.1
    Tertiary DNS:  empty
    I'm not comfortable not having the local DC/DNS address listed so I'm going with the solution Ace offers.
    Opinion?

  • How to set source ip in JNDI DNS

    hello everyone,
    As we known the linux command dig can set sourceip with -b option for a dns query.
    examples:
    dig @DNSSERVER -b 202.16.32.24 www.google.cn
    so,how can i set a sourceip for a dns query in JNDI?
    Is anybody help me?

    Thanks a lot .
    it work well for me now .
    i have a another question.
    i set the nat to gloable ip .and it works.i set it by the Cisco Configuration Professional
    in the edit the static nat.
    but there is a abnormal .
    when the electronic is down. the setting change to the old one.
    so what is the problem?

  • Diagnostic code: smtp;501 DNS says just_hostname is not a real domain

    Hi guys,
    I'm running IMS5.2 in Solaris and i have a problem sending a mail to a specific domain. I can send mail to everybody but not to this one. I think the problem is in the other side, but i need to confirm this suspect and understand the error i'm getting. This is the report i receive when i try to send an e-mail to this specific domain( They are probably using MDaemon 6.8.5):
    This report relates to a message you sent with the following header fields:
    Return-path: <user@mydomain>
    Received: from tcp-daemon.mail.mydomain by mail.mydomain
    (iPlanet Messaging Server 5.2 (built Feb 21 2002))
    id <[email protected]> (original mail from user@mydomain); Mon,
    19 Jan 2004 08:31:33 +0200 (GMT)
    Received: from mydomain (myhost [192.168.1.33])
    by mail.mydomain (iPlanet Messaging Server 5.2 (built Feb 21 2002))
    with ESMTP id <[email protected]> for final_user@domain_to_deliver; Mon,
    19 Jan 2004 08:30:04 +0200 (GMT)
    Received: from [196.28.224.7] by mail.mydomain(mshttpd); Mon,
    19 Jan 2004 08:30:04 +0200
    Date: Mon, 19 Jan 2004 08:30:04 +0200
    From: user@mydomain
    Subject: Teste da conta de e-mail
    To: final_user@domain_to_deliver
    Message-id: <c854a4.54a4c8@mydomain>
    MIME-version: 1.0
    X-Mailer: iPlanet Messenger Express 5.2 (built Feb 21 2002)
    Content-type: text/plain; charset=windows-1252
    Content-language: en
    Content-transfer-encoding: quoted-printable
    Content-disposition: inline
    X-Accept-Language: en
    Priority: normal
    Your message cannot be delivered to the following recipients:
    Recipient address: final_user@domain_to_deliver
    Reason: Remote server rejected HELO command.
    Diagnostic code: smtp;501 DNS says <just_my_hostname> is not a real domain
    Remote system: dns;mail.domain_to_deliver (domain_to_deliver ESMTP MDaemon 6.8.5; Mon, 19 Jan 2004 08:44:34 +0200)
    Any comments please!
    Best Regards

    In your imta.cnf file, look down to the second part, marked,
    "Part II, Channel Block"
    Look further down, find
    ! tcp_local
    tcp_local smtp mx single_sys remotehost inner\ switchchannel identnonelimited subdirs 20 maxjobs 20\
    pool SMTP_POOL maytlsserver maysaslserv\ dequeue_removeroute\
    tcp-daemon somedomain.com
    The 4 lines after "!tcp_local" are all on one line. I've added the backslash character to show a continuation. The next line contains the tcp-daemon keyword, and is followed by what the server will send out on the ehlo/helo line.

Maybe you are looking for