Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DNS not resolving the IP

Status
Not open for further replies.

techincaladmin

Technical User
Jul 5, 2009
26
QA
Hi there,

I am stuck with problem on my dns server, prevoiusly it was working fine.. all the sudden it comes up with under giving messages

Oct 19 11:40:15 ns3 snmpXdmid: [ID 887556 daemon.error] Error receiving PDU The message has a wrong header type (0x79).
Oct 19 11:40:15 ns3 snmpXdmid: [ID 352064 daemon.error] Error receiving packet from agent; rc = -1.
Oct 19 11:40:15 ns3 snmpXdmid: [ID 669004 daemon.error] Will attempt to re-establish connection.


tail query.log
.qa IN A -
19-Oct-2009 12:00:46.356 info: client 69.63.179.20#34321: query: mta2.xx.xxx.xx IN A -
19-Oct-2009 12:00:46.357 info: client 69.63.179.20#34321: query: xx.xxx.xx IN MX -
19-Oct-2009 12:00:46.373 info: client 164.124.101.49#36556: query: xx.xxx.xx IN MX -E
19-Oct-2009 12:00:46.673 info: client 216.9.253.45#31641: query: mail.xx.xxx.xx IN A -
19-Oct-2009 12:00:46.772 info: client 86.36.67.11#53803: query: helplesscoat.com IN MX +
19-Oct-2009 12:00:46.988 info: client 41.211.226.10#32774: query: IN A -E
19-Oct-2009 12:00:47.574 info: client 212.77.192.41#24812: query: F7T61L200766211.xx.xxx.xx IN SOA -


general: error: zone xx.xxx.xx/IN: loading master file qu.edu.qa.zone: bad owner name (check-names)


[root@ns3]#tail named.log
19-Oct-2009 12:23:22.102 lame-servers: info: lame server resolving 'ns.vener.net' (in 'vener.NET'?): 206.145.80.226#53
19-Oct-2009 12:23:22.103 lame-servers: info: lame server resolving 'ns2.vener.net' (in 'vener.NET'?): 206.145.80.226#53
19-Oct-2009 12:23:22.852 lame-servers: info: lame server resolving 'ns.vener.net' (in 'vener.NET'?): 206.145.85.18#53
19-Oct-2009 12:23:22.852 lame-servers: info: lame server resolving 'ns2.vener.net' (in 'vener.NET'?): 206.145.85.18#53
19-Oct-2009 12:38:15.630 lame-servers: info: lame server resolving 'ezash.com' (in 'ezash.com'?): 162.97.140.211#53
19-Oct-2009 12:38:16.347 lame-servers: info: lame server resolving 'ezash.com' (in 'ezash.com'?): 67.43.55.170#53
19-Oct-2009 12:46:48.624 lame-servers: info: unexpected RCODE (SERVFAIL) resolving 'ronclappison.com/MX/IN': 216.194.67.73#53
19-Oct-2009 13:01:00.933 lame-servers: info: unexpected RCODE (SERVFAIL) resolving 'ns1.fastdns.net/AAAA/IN': 64.33.24.11#53
19-Oct-2009 13:05:53.906 lame-servers: info: unexpected RCODE (SERVFAIL) resolving '123.com.gt/MX/IN': 200.13.161.3#53
19-Oct-2009 13:05:55.142 lame-servers: info: unexpected RCODE (SERVFAIL) resolving '123.com.gt/MX/IN': 200.13.161.2#53
[root@ns3]#tail query.log
19-Oct-2009 13:12:37.198 info: client 212.77.192.40#21819: query: mybb.qu.edu.qa IN A -
19-Oct-2009 13:12:37.314 info: client 66.228.118.12#52223: query: qu.edu.qa IN MX -E
19-Oct-2009 13:12:37.348 info: client 86.36.67.11#58220: query: danceinstitutedenver.com IN MX +
19-Oct-2009 13:12:37.567 info: client 78.101.215.24#60125: query: xx.xxx.xx IN SOA +
19-Oct-2009 13:12:37.637 info: client 69.63.178.247#44795: query: mta2.xx.xxx.xx IN A -
19-Oct-2009 13:12:37.640 info: client 69.63.178.248#23856: query: mta1.xx.xxx.xx IN A -
19-Oct-2009 13:12:37.650 info: client 69.63.178.247#2711: query: xx.xxx.xx IN MX -
19-Oct-2009 13:12:37.717 info: client 8.0.23.83#37829: query: mta2.xx.xxx.xx IN A -E
19-Oct-2009 13:12:37.947 info: client 195.146.128.60#19164: query: ns3.xx.xxx.xx IN AAAA -
19-Oct-2009 13:12:37.950 info: client 195.146.128.60#39402: query: mta1.xx.xxx.xxIN AAAA -
[root@ns3]#

[root@ns3]#nslookup mylibrary
Server: 86.36.67.11
Address: 86.36.67.11#53

** server can't find mylibrary: NXDOMAIN

not able to resolve any name.

Kind Regards,
 
I assume the error is in qu.edu.qa, and it is a syntax error. Assume you are running bind.

run "named-checkzone qu.edu.qa PATH_TO_ZONE_FILES/qu.edu.qa.zone"

Most likely you have a '_' or some other illegal character and the load is truncated for that zone.

You could turn off name-checking for that zone...but a better solution is to find/fix the problem.
 

[root@ns3]#named-checkzone XX.XXX.XX /var/named/XX.XXX.XX.zone
/var/named/XX.XXX.XX.zone:58: *mylibrary.XX.XXX.XX: bad owner name (check-names)
zone XX.XXX.XX/IN: loaded serial 2009102002
OK
[root@ns3]#

Here i am confused as we got two dns servers, only this one is make problem after editing the new values for mylibrary whereas second dns server responding perfectly. :(

Even we got same entries on both side. :(((
 
Is that really a '*' on line 58 of the zone file?
Paste what is on line 58...
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top