<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Linux client and Windows DNS in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/linux-client-and-windows-dns/m-p/4184227#M83516</link>
    <description>&amp;gt;&amp;gt;&amp;gt; Logs show that netbackup server and linux servers couldn't resolve each (ex. linuxserver.company.net.edu.au)&lt;BR /&gt;&lt;BR /&gt;So, the netbackup server can't resolve a Linux host. Are you sure that your Windows DNS server is answering queries for the secondary zone? Have you tested with:&lt;BR /&gt;&lt;BR /&gt;dig @windows-dc.domain.dom some.linux.host.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt; The master server for the secondary zone is located across the WAN. However, netbackup server and all windows and linux servers are located in the same LAN/subnet.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt; But why are they working fine when the WAN is up?&lt;BR /&gt;&lt;BR /&gt;If the WAN is up, then you will be able to contact the primary DNS server for that domain. Do you have forwarders configured in your Windows DNS domain for company.net.edu.au ?? If so, then you should remove it, as you already hold a secondary zone.</description>
    <pubDate>Tue, 22 Apr 2008 01:27:56 GMT</pubDate>
    <dc:creator>Ivan Ferreira</dc:creator>
    <dc:date>2008-04-22T01:27:56Z</dc:date>
    <item>
      <title>Linux client and Windows DNS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-client-and-windows-dns/m-p/4184225#M83514</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;We have a W2K3 DNS in our network.  We also have a number of RHEL linux servers installed and points to the W2K3 DNS as its primary DNS/name server.&lt;BR /&gt;&lt;BR /&gt;The W2K3 DNS is a DC and has the directory-integrated windows domain zone.  In addition, the DNS server also has a secondary zone configured for 'company.net.edu.au'.  All our linux servers are entered into this zone as Host entries.&lt;BR /&gt;&lt;BR /&gt;We have a windows netbackup server backing up windows and linux servers.  The problem is, when our WAN goes down, backup fails for all the linux servers.  Backup of Windows servers are fine.  Logs show that netbackup server and linux servers couldn't resolve each (ex. linuxserver.company.net.edu.au)&lt;BR /&gt;&lt;BR /&gt;The master server for the secondary zone is located across the WAN.  However, netbackup server and all windows and linux servers are located in the same LAN/subnet.&lt;BR /&gt;&lt;BR /&gt;I have a feeling that the Linux servers are unable to resolve using the secondary zone configured in the W2K3 DNS server.  But why are they working fine when the WAN is up?&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Cris</description>
      <pubDate>Tue, 22 Apr 2008 00:14:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-client-and-windows-dns/m-p/4184225#M83514</guid>
      <dc:creator>OTEN Helpdesk</dc:creator>
      <dc:date>2008-04-22T00:14:55Z</dc:date>
    </item>
    <item>
      <title>Re: Linux client and Windows DNS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-client-and-windows-dns/m-p/4184226#M83515</link>
      <description>&lt;!--!*#--&gt;What are the Linux systems using as DNS&lt;BR /&gt;servers?&lt;BR /&gt;&lt;BR /&gt;    grep nameserver /etc/resolv.conf&lt;BR /&gt;&lt;BR /&gt;And where are they?&lt;BR /&gt;&lt;BR /&gt;Same for the netbackup server?&lt;BR /&gt;&lt;BR /&gt;&amp;gt; Logs show [...]&lt;BR /&gt;&lt;BR /&gt;They might show you, but I can't see a thing.&lt;BR /&gt;Who can't resolve whom (by name or by&lt;BR /&gt;address)?&lt;BR /&gt;&lt;BR /&gt;&amp;gt; However, netbackup server and all windows&lt;BR /&gt;&amp;gt; and linux servers are located in the same&lt;BR /&gt;&amp;gt; LAN/subnet.&lt;BR /&gt;&lt;BR /&gt;It's nice that they're close, but if they&lt;BR /&gt;can't get each other's addresses, they won't&lt;BR /&gt;know how close they are.</description>
      <pubDate>Tue, 22 Apr 2008 01:27:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-client-and-windows-dns/m-p/4184226#M83515</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2008-04-22T01:27:29Z</dc:date>
    </item>
    <item>
      <title>Re: Linux client and Windows DNS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-client-and-windows-dns/m-p/4184227#M83516</link>
      <description>&amp;gt;&amp;gt;&amp;gt; Logs show that netbackup server and linux servers couldn't resolve each (ex. linuxserver.company.net.edu.au)&lt;BR /&gt;&lt;BR /&gt;So, the netbackup server can't resolve a Linux host. Are you sure that your Windows DNS server is answering queries for the secondary zone? Have you tested with:&lt;BR /&gt;&lt;BR /&gt;dig @windows-dc.domain.dom some.linux.host.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt; The master server for the secondary zone is located across the WAN. However, netbackup server and all windows and linux servers are located in the same LAN/subnet.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;&amp;gt; But why are they working fine when the WAN is up?&lt;BR /&gt;&lt;BR /&gt;If the WAN is up, then you will be able to contact the primary DNS server for that domain. Do you have forwarders configured in your Windows DNS domain for company.net.edu.au ?? If so, then you should remove it, as you already hold a secondary zone.</description>
      <pubDate>Tue, 22 Apr 2008 01:27:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-client-and-windows-dns/m-p/4184227#M83516</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2008-04-22T01:27:56Z</dc:date>
    </item>
  </channel>
</rss>

