Anonymous_User Absent Member.
Absent Member.
1081 views

DNS issues

Have the following Network:
NW6.5 SP4, 3-Nic’s all 255.255.0.0 Subnet Mask, all plugged into the same
Switch, no VLAN yet.
NIC 1 – 10.1.0.11 + 10.2.0.11 Teamed NIC 2 + NIC 3 – 10.0.0.12 + 10.1.0.12
+ 10.3.0.12

One subnet for each floor, One NIC does Main Office floor, Teamed NICs do
other Three Floors

Here’s the problem, setup DNS Server, School.org but have a problem setting
up the reverse lookup. Tried the following, with A and PTR Records. Added A
Records and it put in PTR Records:

10.1.IN-ADDR.ARPA – NSLOOKUP error, Server not found
10.2.IN-ADDR.ARPA – NSLOOKUP error, Server not found
10.1.0.0.IN-ADDR.ARPA - NSLOOKUP error, Server not found
10.2.0.0.IN-ADDR.ARPA - NSLOOKUP error, Server not found
10.1.0.11.IN-ADDR.ARPA – NSLOOKUP responds with domain info but still
Server not found
10.2.0.11.IN-ADDR.ARPA – NSLOOKUP error - not sure which one needs to recheck

Routing has the following, can not add 10.1.0.0 to 10.1.0.11 route:
0.0.0.0 10.1.0.1 (Firewall)
10.0.0.0 10.0.0.12
10.1.0.0 10.1.0.12
10.2.0.0 10.2.0.11
10.3.0.0 10.3.0.12

10.2.0.0 subnet can not access the Internet, through 10.1.0.1. When I stop
the DNS Server, through DHCP/DNS Console, Server ABENDS. DHCP Server screen
keeps giving 10.1.0.12 port 53 errors? I may have some of the errors wrong,
I will check tomorrow. If you see any issues or can offer any help it would
be much appreciated

Labels (2)
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: DNS issues

Hi,

Computerware@att.net wrote:
>
> Have the following Network:
> NW6.5 SP4, 3-Nic’s all 255.255.0.0 Subnet Mask, all plugged into the same
> Switch, no VLAN yet.
> NIC 1 – 10.1.0.11 + 10.2.0.11 Teamed NIC 2 + NIC 3 – 10.0.0.12 + 10.1.0.12


Problem #1. You're using the same subnet 10.1.X.X twice on two different
nics.

>
> 10.1.IN-ADDR.ARPA – NSLOOKUP error, Server not found
> 10.2.IN-ADDR.ARPA – NSLOOKUP error, Server not found
> 10.1.0.0.IN-ADDR.ARPA - NSLOOKUP error, Server not found
> 10.2.0.0.IN-ADDR.ARPA - NSLOOKUP error, Server not found
> 10.1.0.11.IN-ADDR.ARPA – NSLOOKUP responds with domain info but still
> Server not found
> 10.2.0.11.IN-ADDR.ARPA – NSLOOKUP error - not sure which one needs to recheck


Hmm. Ain't these in the wrong order? A correct PTR zone has the net
octets reversed, e.g 1.10.IN-ADDR.ARPA for the 10.1.x.x network.

> Routing has the following, can not add 10.1.0.0 to 10.1.0.11 route:


Not surprisingly, see problem #1.


> 10.2.0.0 subnet can not access the Internet, through 10.1.0.1.


Still a issue caused by #1.

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de
0 Likes
Anonymous_User Absent Member.
Absent Member.

DNS issues correction

Have the following Network:
NW6.5 SP4, 3-Nic’s all 255.255.0.0 Subnet Mask, all plugged into same
Switch, no VLAN yet.
NIC 1 – 10.1.0.11 + 10.2.0.11, Teamed NIC 2 + NIC 3 – 10.0.0.12 + 10.1.0.12
+ 10.3.0.12

One subnet for each floor, One NIC does Main Office floor, Teamed NICs do
other Three Floors

Here’s the problem, setup DNS Server, School.org but have a problem setting
up the reverse lookup. Tried the following, with A and PTR Records. Added A
Records and it put in PTR Records:

1.10.IN-ADDR.ARPA – NSLOOKUP error, Server not found - removed
2.10.IN-ADDR.ARPA – NSLOOKUP error, Server not found - removed
0.0.1.10.IN-ADDR.ARPA - NSLOOKUP error, Server not found - removed
0.0.2.10.IN-ADDR.ARPA - NSLOOKUP error, Server not found - removed
11.0.1.10.IN-ADDR.ARPA – NSLOOKUP responds with domain info but still
Server not found
11.0.2.10.IN-ADDR.ARPA – NSLOOKUP error - not sure which one needs to recheck

Routing has the following, can not add 10.1.0.0 to 10.1.0.11 route:
0.0.0.0 10.1.0.1 (Firewall)
10.0.0.0 10.0.0.12
10.1.0.0 10.1.0.12
10.2.0.0 10.2.0.11
10.3.0.0 10.3.0.12

10.2.0.0 subnet can not access the Internet, through 10.1.0.1. When I stop
the DNS Server, through DHCP/DNS Console, Server ABENDS. DHCP Server screen
keeps giving 10.1.0.12 port 53 errors? I may have some of the errors wrong,
I will check tomorrow. If you see any issues or can offer any help it would
be much appreciated

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: DNS issues

Thanks for the update. As far as the Two NIc's on the 10.1.X.X subnet, just
wanted to be able to access them both from the same network, DNS and DHCP
are on 10.1.0.11 and the floors, 0+1+3, are other NIC, 10.1.0.12. I guess I
am a little confused, why can't Two NIC's on the Server be on the same
subnet? You would think it would know which IP has what services on it.

> Hi,
>
> Computerware@att.net wrote:
> >
> > Have the following Network:
> > NW6.5 SP4, 3-Nic’s all 255.255.0.0 Subnet Mask, all plugged into the same
> > Switch, no VLAN yet.
> > NIC 1 – 10.1.0.11 + 10.2.0.11 Teamed NIC 2 + NIC 3 – 10.0.0.12 + 10.1.0.12

>
> Problem #1. You're using the same subnet 10.1.X.X twice on two different
> nics.
>
> >
> > 10.1.IN-ADDR.ARPA – NSLOOKUP error, Server not found
> > 10.2.IN-ADDR.ARPA – NSLOOKUP error, Server not found
> > 10.1.0.0.IN-ADDR.ARPA - NSLOOKUP error, Server not found
> > 10.2.0.0.IN-ADDR.ARPA - NSLOOKUP error, Server not found
> > 10.1.0.11.IN-ADDR.ARPA – NSLOOKUP responds with domain info but still
> > Server not found
> > 10.2.0.11.IN-ADDR.ARPA – NSLOOKUP error - not sure which one needs to

recheck
>
> Hmm. Ain't these in the wrong order? A correct PTR zone has the net
> octets reversed, e.g 1.10.IN-ADDR.ARPA for the 10.1.x.x network.
>
> > Routing has the following, can not add 10.1.0.0 to 10.1.0.11 route:

>
> Not surprisingly, see problem #1.
>
>
> > 10.2.0.0 subnet can not access the Internet, through 10.1.0.1.

>
> Still a issue caused by #1.
>
> CU,
> --
> Massimo Rosen
> Novell Product Support Forum Sysop
> No emails please!
> http://www.cfc-it.de


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.