Re: Bordermanager DNS resolution problem

[Craig Johnson]

In article <daystar...@no-mx.forums.novell.com>, Daystar wrote:
> I do not think that I changed anything on my end, so was guessing that
> my website host (who also hosts the DNS records for mydomain.com) has
> different records somehow than my last DNS host, and my server is having
> a lookup problem and forcing every request to tigertech.net.
>
I saw just that with a client last week.

Try using a different first DNS server as a test - try 4.2.2.2 for
instance. Wait about 60 seconds, and BM will start using the new server.

Craig Johnson
Novell Knowledge Partner
*** For a current patch list, tips, handy files and books on
BorderManager, go to http://www.craigjconsulting.com ***

[Craig Johnson]

That explains it. In my case, redirecting to other DNS servers 'fixed'
(hid) the issue then, because DNS started working again.

[Massimo Rosen]

Hi,

Craig Johnson wrote:
> >
> I saw just that with a client last week.
>
> Try using a different first DNS server as a test - try 4.2.2.2 for
> instance. Wait about 60 seconds, and BM will start using the new server.

It's a long known winsock bug in NW6.5 (since SP7) that Novell refuses
to fix so far. The problem being that DNS requests from NW always first
try with the local domain appended, and only if that fails it attempts
without local domain. E.G, when NW tries to resolve www.google.com, the
first request will be www.google.com.yourdomain.com. Many DNS servers
are configured with wildcard resolution, and will answer anything
unknown.domain.com with always the same address. Additionally, NW also
only falls back to the proper request, whe the DNS server returns an
error on the first request. If (and that's legal), the DNS server simply
answers with an empty record, NW never even attempts the proper name.

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