Dear All
i have problem in DNS Server Which is in HPUX 10
i found the error report when i check dnsstuff.com

http://www.dnsreport.com/tools/dnsre...n=glide.net.in

this shows that

Lame nameservers ERROR: You have one or more lame nameservers. These are nameservers that do NOT answer authoritatively for your domain. This is bad; for example, these nameservers may never get updated. The following nameservers are lame:
202.131.124.4

what this error means pls explain as
my mail servers are working ok , websites opening worldwide

Well, is ns.glide.net.in. [202.131.124.4] [TTL=86000] a master or slave nameserver to ns1.glide.net.in. [202.131.124.5] [TTL=86000]? How does it get it's updates?

ns.glide.net.in [202.131.124.4] is primary name server for
ns1.glide.net.in [202.131.124.5]
About its update ? pls clear it

He is asking how the nameservers arranged (which is the master, which is the slave) and how the transfer is made. IE are both nameservers on the same LAN, to they connect through private IP addresses without a firewall in between, or do they connect through their public addresses?

What is odd is that ns1.glide.net.in reports that it is authoritative, but ns.glide.net.in says it isn't. You say ns is the master and ns1 is the slave? That seems odd. I don't think you can have the master not report as authoritative, but the slave report the opposite. Here are some results:

See how AUTHORITY is 2 under 202.131.124.5 but AUTHORITY is 0 under 202.131.124.4? Something is off there. It would help if you could post both the named.conf and the zone file for glide.net.in from 202.131.124.4.

Peace,
JimBass

db.glide in 202.131.124.4 is as

-------------------------------------------------------------------
[/]cat /etc/named.data/db.glide |more
@ IN SOA glide.net.in. root.glide.net.in. (
2003010401 ; Serial
7200 ; Refresh every 3 hours
3600 ; Retry every hour
1209600 ; Expire after a week
86000 ) ; Minimum ttl of 1 day
IN NS ns.glide.net.in.
IN NS ns1.glide.net.in.
glide.net.in. IN A 202.131.124.4
glide.net.in. IN MX 10 ss.glide.net.in.
localhost IN A 127.0.0.1
pop IN CNAME ns5
ss IN A 202.131.114.7
ns IN A 202.131.124.4
ns5 IN A 202.131.124.3
ns1 IN A 202.131.124.5
------------------------------------------------------------------

named.boot file is
[/]cat /etc/named.boot |more

; type domain source file
;


directory /etc/named.data ;running dir for named


primary 0.0.127.IN-ADDR.ARPA db.127.0.0
primary 116.131.202.IN-ADDR.ARPA db.202.131.116
primary 122.131.202.IN-ADDR.ARPA db.202.131.122
primary 126.131.202.IN-ADDR.ARPA db.202.131.126
primary windowsupdate.com db.windowsupdate
primary glide.net.in db.glide

--------------------------------------------------------------------

pls check now what is the problem in this

The problem lies in the configs of ns.glide.net.in. it still isn't responding as authoritative.

It looks like the version of BIND you are running on 202.131.124.4 is only recursive, that is it doesn't respond authoritatively for anything. It needs to be changed so it answers positively for glide.net.in.

You would normally copy the named.conf file from 202.131.124.5, and place it on 202.131.124.4, but have one set as master for glide.net.in, and the other set to slave from the master. It looks like you have some rpm distro that changes the names of important files. Looks like what should be called named.conf on your machine is called named.boot. Great. Yet another reason to detest Redhat.

If you could post both the named.conf (or named.boot as it might be on your machine) from both 202.131.124.4 and 202.131.124.5, we'll spot the difference and correct it.

Peace,
JimBass

Now these are working

i created the master file again . and slave file created
working ok now