Its likely. We saw that once when some Windows domain controllers started responding with IPv6 addresses first. They would have to timeout before the v4 ones.
-----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Michael Weiner Sent: Thursday, October 29, 2015 9:31 AM To: [email protected] Subject: Re: [LINUX-390] DNS Question thank you. Is that why I am getting delays when I try to connect to the server? On Thu, Oct 29, 2015 at 12:06 PM, Marcy Cortes < [email protected]> wrote: > You can turn off IPv6 on a particular interface with > net.ipv6.conf.eth0.disable_ipv6 = 1 > > Or totally by putting > install ipv6 /bin/true > > in /etc/modprobe.d/50-ipv6.conf > > > You may have to do that if parts of your network aren't ready for it yet. > > > > -----Original Message----- > From: Linux on 390 Port [mailto:[email protected]] On Behalf Of > Michael Weiner > Sent: Thursday, October 29, 2015 8:06 AM > To: [email protected] > Subject: [LINUX-390] DNS Question > > Hi all, > > I am working on a DNS on SLES 11 SP3 using BIND. > > I got the DNS working where I can ping my entries etc. But I am > getting the following errors which looks like IPv6. > > 172.16.1.182 is my local laptop DHCP address. Any suggestions? > > Oct 29 06:28:58 dnsserver named[22031]: network unreachable resolving > '182.1.16.172.in-addr.arpa/PTR/IN': 2001:503:c27::2:30#53 Oct 29 > 06:28:58 dsnserver named[22031]: network unreachable resolving > '182.1.16.172.in-addr.arpa/PTR/IN': 2001:500:2d::d#53 Oct 29 06:28:58 > dsnserver named[22031]: network unreachable resolving > '182.1.16.172.in-addr.arpa/PTR/IN': 2001:503:ba3e::2:30#53 Oct 29 > 06:28:58 dsnserver named[22031]: network unreachable resolving > './NS/IN': 2001:503:c27::2:30#53 > Oct 29 06:29:01 dsnserver named[22031]: network unreachable resolving > './NS/IN': 2001:500:2d::d#53 > Oct 29 06:29:04 dsnserver named[22031]: network unreachable resolving > './NS/IN': 2001:dc3::35#53 > Oct 29 06:29:04 dsnserver named[22031]: network unreachable resolving > './NS/IN': 2001:503:ba3e::2:30#53 > Oct 29 06:29:04 dsnserver named[22031]: network unreachable resolving > './NS/IN': 2001:500:3::42#53 > Oct 29 06:29:04 dsnserver named[22031]: network unreachable resolving > './NS/IN': 2001:500:2f::f#53 > Oct 29 06:29:04 dsnserver named[22031]: network unreachable resolving > './NS/IN': 2001:7fe::53#53 > Oct 29 06:29:04 dsnserver named[22031]: network unreachable resolving > '182.1.16.172.in-addr.arpa/PTR/IN': 2001:dc3::35#53 Oct 29 06:29:09 > dsnserver named[22031]: client 10.100.0.191#38658: query: > 182.1.16.172.in-addr.arpa IN PTR + > Oct 29 06:29:22 dsnserver named[22031]: network unreachable resolving > './NS/IN': 2001:7fd::1#53 > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- Michael Weiner Systems Admin Infinity Systems Software, Inc. One Penn Plaza Suite 2010 New York, NY 10119 o: (646) 405-9300 c: (845) 641-0517 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
