Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > Linux Forums > Server Operation

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #1  
Old 4th July 2006, 11:18
IPMolester IPMolester is offline
Junior Member
 
Join Date: Jul 2006
Posts: 2
Thanks: 0
Thanked 0 Times in 0 Posts
Default The weirdest DNS problem I have come upon

I'm totally lost with this:

I have set up a Linux (Mandriva 2006) server on my home ADSL line and everything works just splendid.

Well, everything except for a tiny little problem. Bind sometimes has a problem with resolving A records, always for the same domains and hosts. But what I don't understand is that when I turn on more debugging in "dig" it shows me that it received the information, but a error claims it didn't

Example:
Quote:
[MySelf@MyHost]$ dig www.break.com +trace +additional

; <<>> DiG 9.3.2 <<>> www.break.com +trace +additional
;; global options: printcmd
. 185534 IN NS i.root-servers.net.
. 185534 IN NS j.root-servers.net.
. 185534 IN NS k.root-servers.net.
. 185534 IN NS l.root-servers.net.
. 185534 IN NS m.root-servers.net.
. 185534 IN NS a.root-servers.net.
. 185534 IN NS b.root-servers.net.
. 185534 IN NS c.root-servers.net.
. 185534 IN NS d.root-servers.net.
. 185534 IN NS e.root-servers.net.
. 185534 IN NS f.root-servers.net.
. 185534 IN NS g.root-servers.net.
. 185534 IN NS h.root-servers.net.
a.root-servers.net. 533570 IN A 198.41.0.4
b.root-servers.net. 300260 IN A 192.228.79.201
c.root-servers.net. 271934 IN A 192.33.4.12
d.root-servers.net. 300260 IN A 128.8.10.90
e.root-servers.net. 300260 IN A 192.203.230.10
f.root-servers.net. 534166 IN A 192.5.5.241
g.root-servers.net. 300260 IN A 192.112.36.4
h.root-servers.net. 271934 IN A 128.63.2.53
i.root-servers.net. 271934 IN A 192.36.148.17
j.root-servers.net. 533797 IN A 192.58.128.30
k.root-servers.net. 533757 IN A 193.0.14.129
l.root-servers.net. 300260 IN A 198.32.64.12
m.root-servers.net. 300260 IN A 202.12.27.33
;; Received 436 bytes from 127.0.0.1#53(127.0.0.1) in 3 ms

com. 172800 IN NS M.GTLD-SERVERS.NET.
com. 172800 IN NS A.GTLD-SERVERS.NET.
com. 172800 IN NS B.GTLD-SERVERS.NET.
com. 172800 IN NS C.GTLD-SERVERS.NET.
com. 172800 IN NS D.GTLD-SERVERS.NET.
com. 172800 IN NS E.GTLD-SERVERS.NET.
com. 172800 IN NS F.GTLD-SERVERS.NET.
com. 172800 IN NS G.GTLD-SERVERS.NET.
com. 172800 IN NS H.GTLD-SERVERS.NET.
com. 172800 IN NS I.GTLD-SERVERS.NET.
com. 172800 IN NS J.GTLD-SERVERS.NET.
com. 172800 IN NS K.GTLD-SERVERS.NET.
com. 172800 IN NS L.GTLD-SERVERS.NET.
A.GTLD-SERVERS.NET. 172800 IN A 192.5.6.30
A.GTLD-SERVERS.NET. 172800 IN AAAA 2001:503:a83e::2:30
B.GTLD-SERVERS.NET. 172800 IN A 192.33.14.30
B.GTLD-SERVERS.NET. 172800 IN AAAA 2001:503:231d::2:30
C.GTLD-SERVERS.NET. 172800 IN A 192.26.92.30
D.GTLD-SERVERS.NET. 172800 IN A 192.31.80.30
E.GTLD-SERVERS.NET. 172800 IN A 192.12.94.30
F.GTLD-SERVERS.NET. 172800 IN A 192.35.51.30
G.GTLD-SERVERS.NET. 172800 IN A 192.42.93.30
H.GTLD-SERVERS.NET. 172800 IN A 192.54.112.30
I.GTLD-SERVERS.NET. 172800 IN A 192.43.172.30
J.GTLD-SERVERS.NET. 172800 IN A 192.48.79.30
K.GTLD-SERVERS.NET. 172800 IN A 192.52.178.30
L.GTLD-SERVERS.NET. 172800 IN A 192.41.162.30
;; Received 503 bytes from 192.36.148.17#53(i.root-servers.net) in 99 ms

break.com. 172800 IN NS ns1.theplanet.com.
break.com. 172800 IN NS ns2.theplanet.com.
ns1.theplanet.com. 172800 IN A 70.86.61.133
ns1.theplanet.com. 172800 IN A 70.86.61.134
ns1.theplanet.com. 172800 IN A 70.87.7.70
ns1.theplanet.com. 172800 IN A 70.87.7.71

ns2.theplanet.com. 172800 IN A 70.86.61.135
ns2.theplanet.com. 172800 IN A 70.86.61.136
ns2.theplanet.com. 172800 IN A 70.87.7.72
ns2.theplanet.com. 172800 IN A 70.87.7.73
;; Received 205 bytes from 192.55.83.30#53(M.GTLD-SERVERS.NET) in 375 ms

dig: couldn't get address for 'ns1.theplanet.com': failure
As you can see, dig did indeed receive the IP for ns1.theplanet.com, and then claimed it didn't.

The problem doesn't seem to be a network problem, since I can ping the server.

Quote:
[MySelf@MyHost]$ ping 70.86.61.133
PING 70.86.61.133 (70.86.61.133) 56(84) bytes of data.
64 bytes from 70.86.61.133: icmp_seq=1 ttl=53 time=147 ms
64 bytes from 70.86.61.133: icmp_seq=2 ttl=53 time=164 ms
64 bytes from 70.86.61.133: icmp_seq=3 ttl=53 time=149 ms

--- 70.86.61.133 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 147.009/153.632/164.135/7.510 ms
My question is this: Why is 'dig' claiming that it can't get the address for ns1.theplanet.com when it's obvious from the trace that it already did ?

Last edited by IPMolester; 4th July 2006 at 11:35.
Reply With Quote
Sponsored Links
 

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
postfix problems with smtp linkdeb Server Operation 13 15th March 2014 17:58
Strange email problem for one of my domains... any help appreciated paulrobert_a Installation/Configuration 5 9th August 2010 14:15
sending e-mail using mail() function linuxuser1 HOWTO-Related Questions 38 21st April 2009 12:20
Postfix+MySQL Problem jasutton Installation/Configuration 1 15th June 2006 16:06
SMTP TLS Problem with Mail Client dschmid Installation/Configuration 1 9th December 2005 01:56


All times are GMT +2. The time now is 04:50.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.