really whacky issues

Mark (Help Desk Specialist) mark at downtownhelpdesk.com
Sat Jan 17 18:08:44 UTC 2004


*This message was transferred with a trial version of CommuniGate(tm) Pro*
I'm having some interesting problems; I've searched the list and didn't 
seem to find any answers.

I'm running BIND 8.3.3-REL on FreeBSD 5.0-STABLE.

All of my name queries are appending my domain name to the query.  So, 
if I do an nslookup on "perl.org", it indicates that it is looking up 
"perl.org.mydomain.name".  Of course, because perl.org.mydomain.name 
doesn't exist in my zone records, it will fail the lookup.  Ping and 
whois also all fail to find correct information.


Some sample outputs: (I have changed my actual domain name here to 
"mydomain.name")

ping: cannot resolve marknernberg.com: No address associated with name

nslookup's output:
$ nslookup perl.org
Server:  ns1.866gethost.com
Address:  66.70.83.244

Name:    perl.org.mydomain.name
Served by:
- B.ROOT-SERVERS.NET

[and continues to list some of the other root servers]

whois:


$ whois perl.org
whois: org.whois-servers.net: No address associated with hostname
[i'm presuming because the lookup for "org.whois-servers.net" is 
failing]

DIG, on the other hand, seems to work:
$ dig perl.org
; <<>> DiG 8.3 <<>> perl.org
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2
;; QUERY SECTION:
;;      perl.org, type = A, class = IN

;; AUTHORITY SECTION:
org.                    1d23h26m19s IN NS  TLD1.ULTRADNS.NET.
org.                    1d23h26m19s IN NS  TLD2.ULTRADNS.NET.

;; ADDITIONAL SECTION:
TLD1.ULTRADNS.NET.      1h52m54s IN A   204.74.112.1
TLD2.ULTRADNS.NET.      1h52m54s IN A   204.74.113.1

;; Total query time: 25 msec
;; FROM: router.mydomain.name to SERVER: default -- 66.70.83.244
;; WHEN: Sat Jan 17 13:06:24 2004
;; MSG SIZE  sent: 26  rcvd: 108

[or does it?]  this doesn't seem to be the right info, either.

Any ideas?  I can ping by IP address with no problems, and other 
servers can access my machine using some of the domain names associated 
with it [although not the ones for which I control the DNS].

Mark Nernberg



More information about the bind-users mailing list