Unnormal results when using nslookup

[xujun]

Hi !
I have some questions about DNS.
My /etc/hosts file is originally described as following.

127.0.0.1 localhost loopback
192.168.200.1 dserver.eda.com dserver
192.168.200.2 hp_music.eda.com hp_music
192.168.200.3 WS02.eda.com WS02
192.168.200.4 WS03.eda.com WS03
192.168.200.5 WS04.eda.com WS04

Then under /etc/named.data ,I create a file param, using hosts_to_named -f param command to create data files and booting files, modifing /etc/rc.config.d/namesvrs, changing NAMED variant to 1,
configuring /etc/resolv.conf file and /etc/nsswitch.conf file,
then restart.

The following is the process of hosts resolving on DNS server.

nslookup

Default Name dserver: dserver.eda.com
Address: 192.168.200.1

> hp_music
Name dserver: dserver.eda.com
Address: 192.168.200.1

Trying DNS
*** dserver.eda.com can't find hp_music: dserver failed
> ws03
Name dserver: dserver.eda.com
Address: 192.168.200.1

Trying DNS
Non-authoritative answer:
Name: ws03.eda.com
Address: 192.168.200.4

> 192.168.200.4
Name dserver: dserver.eda.com
Address: 192.168.200.1

Trying DNS
Name: ws03.eda.com
Address: 192.168.200.4

> 192.168.200.2
Name dserver: dserver.eda.com
Address: 192.168.200.1

Trying DNS
*** dserver.eda.com can't find 192.168.200.2: dserver failed


Questions:
1. There is always "Non-authoritative answer" warning when resolving hostname to ip address.
2. All hostnames include underline cann't be resolved correctly.

How can I solve it? My HP-UX version is 10.20 . Thanks a lot.

[Paula J Frazer-Campbell]

Hi
This might help

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xdc77abe92dabd5118ff10090279cd0f9,00.html


Paula

[Chris Vail]

Do not worry about "non-authoritative answer". This merely means that the DNS cache for this entry hasn't been updated since the last inquiry.

The underscore character is not valid for hostnames. Microsoft uses it, but this violates the RFC's for hostnames.


Chris

[Sridhar Bhaskarla]

Answers.

1. There are a couple of reasons why you get non-authorative answers.
- You don't have a full copy of the zone file.
- SOA record missing to specify itself as the authority server.

2. _ is not valid in forming DNS names.

-Sri

[Stew McLeod]

Non-authoritative answer is not a error message. It simply means the answer is coming from a Name Server's cache.

To be able to use underscore in host name, edit /etc/named.conf and add

options {
check-names master ignore;
check-names slave ignore;
check-names response ignore;
};

in the options section, if you are running bind 8.x

good luck.

[xujun]

The original reason of errors and warnings is that
hp_music was DNS server and dserver was DNS client initially.
Could you offer me any more valuable answers?

[Nashford Ramdeen]

Underscores are not legal characters in hostnames. If you want to continue to use the underscores then you need to add the following entries to your named.boot file:

check-names primary ignore
check-names secondary ignore
check-names response ignore

[Craig Rants]

RFC 922 states that _ is not a valid character for DNS resolution. Now Microsoft does not adhere to this RFC, but Unix definately does. You may want to change your hostname.

C