I think I've found a bug--but I don't know how obscure it might be.

I'm trying to resolve Ames Community Bank using NW 6.0 sp5 (plus patches). named.nlm version 5.12.06 dated May 11,2004.

amesbank.com uses directnic.com for DNS services (ns0 and ns1 .directnic.com). Ames Community Bank has a cname (alias) entry pointing to acb.eogdenbancshares.com.

eogdenbancshares.com uses dns servers ns1 and ns2 .eogdenbancshares.com.

Now directnic.com replies to all queries that it is not authoritative for with its own advertising website (instead of denying the request or performing the recursive lookup). Looks like this:

C:\Documents and Settings\user>nslookup

> server ns0.directnic.com
Default Server: ns0.directnic.com
Address: 69.46.233.245

> www.novell.com
Server: ns0.directnic.com
Address: 69.46.233.245

Name: www.novell.com
Address: 204.251.15.176


Where 204.251.15.176 is an advertising website. (www.novell.com is actually 130.57.5.25)

Now if I try Ames Community Bank from directnic.com I get this:

> Ames Community Bank
Server: ns0.directnic.com
Address: 69.46.233.245

Name: acb.eogdenbancshares.com
Address: 204.251.15.176
Aliases: Ames Community Bank


which shows the alias and acb.eogdenbancshares.com, but directnic also sends along the advertising website's IP address. This is the incorrect IP address that my DNS server returns to client requests:


> server 192.168.1.254

> Ames Community Bank
Server: [192.168.1.254]
Address: 192.168.1.254

Non-authoritative answer:
Name: acb.eogdenbancshares.com
Address: 204.251.15.176
Aliases: Ames Community Bank

> acb.eogdenbancshares.com
Server: [192.168.1.254]
Address: 192.168.1.254

Non-authoritative answer:
Name: acb.eogdenbancshares.com
Address: 204.251.15.176


If you connect to eogdenbancshares' dns servers you get:

> server ns1.eogdenbancshares.com
Default Server: ns1.eogdenbancshares.com
Address: 71.39.82.180

> Ames Community Bank
Server: ns1.eogdenbancshares.com
Address: 71.39.82.180

Name: Ames Community Bank
Address: 71.39.82.180

> acb.eogdenbancshares.com
Server: ns1.eogdenbancshares.com
Address: 71.39.82.180

Name: acb.eogdenbancshares.com
Address: 71.39.82.180


Which, of course, is the correct IP by definition since that's the authoritative DNS server.


It's easy to say that it's a problem with directnic (which I don't entirely disagree with), BUT I can't find any other DNS servers with this problem (Netware 6.5 servers, microsoft, *nix, you name it). Yes, I've done reboots of the server and cleared the cache etc. If I unload/reload named and I manually do a lookup on acb.eogdenbancshares.com BEFORE Ames Community Bank, then the dns server gets the correct IP (because that doesn't have anything to do with directnic.com) for acb.eogdenbancshares, caches it, and then will correctly resolve Ames Community Bank (at least until the TTL expires).


This feels like a bug since I can't find any other dns servers that have the problem (admittedly, I do not have any other NW 6.0 servers to test with--and I don't want to take the time to create one). But rather obscure--it's only a problem with a hostname that's "controlled" by directnic which uses an alias to a hostname that's NOT "controlled" by directnic.

Ted Kumsher